From mcote at mozilla.com Fri Jan 3 22:56:02 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Fri, 03 Jan 2014 17:56:02 -0500 Subject: Update on moving Bugzilla to git In-Reply-To: References: Message-ID: <87edndGHt9ad3VrPnZ2dnUVZ_ridnZ2d@mozilla.org> Another update: I've finished the two scripts. The first is for the initial migration, which translates bzr's fast-export output into git-friendly fast-import input, specifically adding the "bug" commit property to the git commit message, if it exists and if the referenced bug is not already mentioned in the commit message. This is a C# script, which I know is a bit odd, but I found it on a blog post, and it was easier to make a few changes than rewrite it in Perl or Python or Bash or another language that makes more sense on *NIX platforms. It runs fine under mono on Linux. The second script keeps the Bazaar branches in check with the git branches. It's Perl, based off of the current bzr-to-cvs.pl script, as mentioned in my previous post. I've created a repo in GitHub with these scripts and a README explaining how we intend to do the migration: https://github.com/markrcote/bugzilla-git-migration. I invite anyone interested to take a look and even try it out; there are instructions on testing in the README. I've done conversions of Bugzilla trunk and 4.2 using the latest version of the migration script and pushed them to a GitHub repo as examples (the plan is still to have the official repos hosted on git.mozilla.org with one-way mirrors to GitHub): https://github.com/markrcote/bugzilla I'm not sure of the exact timing of the migration. I'm thinking February/March, when we can both get some feedback on these scripts (in case I've made any glaring errors) and schedule some IT time. Mark On 12/10/2013, 4:16 PM, Mark C?t? wrote: > Just wanted to give a brief update on the plan to transition to git to > assure all that it is still progressing. > > I've fleshed out the wiki page[1], including a step-by-step plan. I've > got a one-time migration script working based on [2] that preserves the > bug ID commit metadata, although I need to tweak it slightly to only > annotate commits that don't reference the bug mentioned in the metadata > (the original script does this, but I need to change it to Bugzilla's > standard). An example of the resulting migration for bmo/4.2 is at [3]. > > Finally, I have a git-to-bzr.pl script working based on the previous > migration script, bzr-to-cvs.pl[4]. I will be posting it for review > very soon. > > Mark > > > [1]: https://wiki.mozilla.org/Bugzilla:Migrating_to_git > [2]: http://www.fusonic.net/en/blog/2013/03/26/migrating-from-bazaar-to-git/ > [3]: https://github.com/markrcote/bmo > [4]: http://bzr.mozilla.org/bzr-plugins/bzr-to-cvs/view/head:/bzr-to-cvs.pl > _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From damien.nozay at gmail.com Sat Jan 11 00:01:19 2014 From: damien.nozay at gmail.com (Damien) Date: Fri, 10 Jan 2014 16:01:19 -0800 Subject: Update on moving Bugzilla to git In-Reply-To: <87edndGHt9ad3VrPnZ2dnUVZ_ridnZ2d@mozilla.org> References: <87edndGHt9ad3VrPnZ2dnUVZ_ridnZ2d@mozilla.org> Message-ID: Hey Mark, from https://github.com/markrcote/bugzilla-git-migration: However, since git doesn't have the concept of commit properties, piping > this data into git fast-importresults in errors. We can, however, translate > the fast-export output by storing commit properties in the git commit > messages. Even better, we can check if the bug number is already present in > the commit message and only add the bug info if it isn't. You could use git notes for the additional metadata / bzr commit properties. http://git-scm.com/blog/2010/08/25/notes.html e.g. ref/notes/reviews for the r/a flags. and ref/notes/bugs for the bug links. e.g. sample workflow: 1) get patch / commit from other remote 2) review it, use git-notes to add a note (r/a flags) 3) if there is a relevant bug, add a note. If you think about it, if the patch you get from the user is okay, you don't need to modify the message (!= SHA1) to add notes (same SHA1). this allows consistent objects between your repo / somebody else's repo, etc. $0.02 Damien. On Fri, Jan 3, 2014 at 2:56 PM, Mark C?t? wrote: > Another update: I've finished the two scripts. The first is for the > initial migration, which translates bzr's fast-export output into > git-friendly fast-import input, specifically adding the "bug" commit > property to the git commit message, if it exists and if the referenced > bug is not already mentioned in the commit message. This is a C# > script, which I know is a bit odd, but I found it on a blog post, and it > was easier to make a few changes than rewrite it in Perl or Python or > Bash or another language that makes more sense on *NIX platforms. It > runs fine under mono on Linux. > > The second script keeps the Bazaar branches in check with the git > branches. It's Perl, based off of the current bzr-to-cvs.pl script, as > mentioned in my previous post. > > I've created a repo in GitHub with these scripts and a README explaining > how we intend to do the migration: > https://github.com/markrcote/bugzilla-git-migration. I invite anyone > interested to take a look and even try it out; there are instructions on > testing in the README. > > I've done conversions of Bugzilla trunk and 4.2 using the latest version > of the migration script and pushed them to a GitHub repo as examples > (the plan is still to have the official repos hosted on git.mozilla.org > with one-way mirrors to GitHub): https://github.com/markrcote/bugzilla > > I'm not sure of the exact timing of the migration. I'm thinking > February/March, when we can both get some feedback on these scripts (in > case I've made any glaring errors) and schedule some IT time. > > Mark > > > On 12/10/2013, 4:16 PM, Mark C?t? wrote: > > Just wanted to give a brief update on the plan to transition to git to > > assure all that it is still progressing. > > > > I've fleshed out the wiki page[1], including a step-by-step plan. I've > > got a one-time migration script working based on [2] that preserves the > > bug ID commit metadata, although I need to tweak it slightly to only > > annotate commits that don't reference the bug mentioned in the metadata > > (the original script does this, but I need to change it to Bugzilla's > > standard). An example of the resulting migration for bmo/4.2 is at [3]. > > > > Finally, I have a git-to-bzr.pl script working based on the previous > > migration script, bzr-to-cvs.pl[4]. I will be posting it for review > > very soon. > > > > Mark > > > > > > [1]: https://wiki.mozilla.org/Bugzilla:Migrating_to_git > > [2]: > http://www.fusonic.net/en/blog/2013/03/26/migrating-from-bazaar-to-git/ > > [3]: https://github.com/markrcote/bmo > > [4]: > http://bzr.mozilla.org/bzr-plugins/bzr-to-cvs/view/head:/bzr-to-cvs.pl > > > > _______________________________________________ > dev-apps-bugzilla mailing list > dev-apps-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-apps-bugzilla > - > To view or change your list settings, click here: > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerv at mozilla.org Fri Jan 17 10:52:43 2014 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 17 Jan 2014 10:52:43 +0000 Subject: Docs now converted to RST and up on ReadTheDocs Message-ID: I've just checked in the fix for bug 912064: https://bugzilla.mozilla.org/show_bug.cgi?id=912064 and so Bugzilla's documentation format is now RST (ReStructured Text) rather than XML DocBook. We hope that this will make the docs much easier to edit and contribute to (although building the PDF version still requires 1GB of TeX...). It also means we can put them up on ReadTheDocs, and I have now done so: http://bugzilla.readthedocs.org/en/latest/ Pretty! :-) There are many things still to do, but this is a good base for moving forwards. I will be filing more bugs about enhancements, and encourage others to do the same. Soon, we will perhaps want to reorganize the docs, import a load of stuff which has up to now lived in the wiki (because changing the docs was too hard) and so on. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From cedric.corazza at gmail.com Fri Jan 17 11:03:34 2014 From: cedric.corazza at gmail.com (=?UTF-8?B?Q8OpZHJpYyBDb3Jhenph?=) Date: Fri, 17 Jan 2014 12:03:34 +0100 Subject: Docs now converted to RST and up on ReadTheDocs In-Reply-To: References: Message-ID: Le 17/01/2014 11:52, Gervase Markham a ?crit : > I've just checked in the fix for bug 912064: > https://bugzilla.mozilla.org/show_bug.cgi?id=912064 > and so Bugzilla's documentation format is now RST (ReStructured Text) > rather than XML DocBook. > > We hope that this will make the docs much easier to edit and contribute > to (although building the PDF version still requires 1GB of TeX...). > > It also means we can put them up on ReadTheDocs, and I have now done so: > > http://bugzilla.readthedocs.org/en/latest/ > > Pretty! :-) > > There are many things still to do, but this is a good base for moving > forwards. I will be filing more bugs about enhancements, and encourage > others to do the same. Soon, we will perhaps want to reorganize the > docs, import a load of stuff which has up to now lived in the wiki > (because changing the docs was too hard) and so on. > > Gerv > Hi, I'm the French localizer of Bugzilla (http://frenchmozilla.cvs.sourceforge.net/viewvc/frenchmozilla/bugzilla/?pathrev=HEAD) Reading bug 912064, I can't see how to convert the current French files to the new system and link them to https://bugzilla.readthedocs.org/. Is there an how-to file somewhere to explain this? This might interest as well the other localizers (http://www.bugzilla.org/download/#localizations). Thanks. C?dric _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Fri Jan 17 12:00:29 2014 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 17 Jan 2014 12:00:29 +0000 Subject: Docs now converted to RST and up on ReadTheDocs In-Reply-To: References: Message-ID: <52D91B5D.9060307@mozilla.org> On 17/01/14 11:03, C?dric Corazza wrote: > I'm the French localizer of Bugzilla > (http://frenchmozilla.cvs.sourceforge.net/viewvc/frenchmozilla/bugzilla/?pathrev=HEAD) > > Reading bug 912064, I can't see how to convert the current French files > to the new system and link them to https://bugzilla.readthedocs.org/. > Is there an how-to file somewhere to explain this? > This might interest as well the other localizers > (http://www.bugzilla.org/download/#localizations). That's a very good question. Converting them to the new system: one option is to use the db2rst.py and makebzdocs tools here, which I used to do the initial conversion: https://github.com/gerv/bzdocs There's then quite a bit of fixup to do, which I did manually. I'm afraid I didn't keep records of exactly what I did :-( The other option is to take the new English docs and copy-paste each para of French into the structure, but that might be more work. As for putting them on ReadTheDocs, there's a FAQ answer: https://docs.readthedocs.org/en/latest/faq.html#how-do-i-support-multiple-languages-of-documentation They want to have full language support, but it's not there yet. (Patches welcome? :-) In the mean time, the FAQ suggests creating a project for each language of documentation. So we would have: bugzilla-fr.readthedocs.org bugzilla-de.readthedocs.org etc. and point each of them at the place where you keep your translation of the docs. Although RTD doesn't support CVS - only Git, SVN, BZR and Hg - so you'd need to move the Bugzilla docs somewhere else, or use Subversion SVN. I note that we only have very old non-English versions of docs linked from http://www.bugzilla.org/docs/ . You should file a bug in Bugzilla::bugzilla.org to get that fixed. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From cedric.corazza at gmail.com Sat Jan 18 20:39:36 2014 From: cedric.corazza at gmail.com (=?UTF-8?B?Q8OpZHJpYyBDb3Jhenph?=) Date: Sat, 18 Jan 2014 21:39:36 +0100 Subject: Docs now converted to RST and up on ReadTheDocs In-Reply-To: <52D91B5D.9060307@mozilla.org> References: <52D91B5D.9060307@mozilla.org> Message-ID: Le 17/01/2014 13:00, Gervase Markham a ?crit : > Converting them to the new system: one option is to use the db2rst.py > and makebzdocs tools here, which I used to do the initial conversion: > https://github.com/gerv/bzdocs > > There's then quite a bit of fixup to do, which I did manually. I'm > afraid I didn't keep records of exactly what I did :-( The other option > is to take the new English docs and copy-paste each para of French into > the structure, but that might be more work. I succeeded to convert the French documentation files almost flawlessly in an afternoon with the script on your repository. I just have now to get used to the RST syntax and fix some little remaining syntax errors. Will blog about this tomorrow with the link to the fr Documentation. > As for putting them on ReadTheDocs, there's a FAQ answer: > > https://docs.readthedocs.org/en/latest/faq.html#how-do-i-support-multiple-languages-of-documentation > > They want to have full language support, but it's not there yet. > (Patches welcome? :-) In the mean time, the FAQ suggests creating a > project for each language of documentation. So we would have: > > bugzilla-fr.readthedocs.org > bugzilla-de.readthedocs.org > > etc. and point each of them at the place where you keep your translation > of the docs. Although RTD doesn't support CVS - only Git, SVN, BZR and > Hg - so you'd need to move the Bugzilla docs somewhere else, or use > Subversion SVN. I migrated my CVS repository to Mercurial and will look at the FAQ on RTD. > I note that we only have very old non-English versions of docs linked > from http://www.bugzilla.org/docs/ . You should file a bug in > Bugzilla::bugzilla.org to get that fixed. I didn't notice that page. I will file a bug after hosting the up-to-date localized doc on my site. Probably tomorrow. C?dric _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Sun Jan 19 22:06:01 2014 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Sun, 19 Jan 2014 23:06:01 +0100 Subject: Docs now converted to RST and up on ReadTheDocs In-Reply-To: References: Message-ID: <52DC4C49.9050203@gmail.com> Le 17. 01. 14 11:52, Gervase Markham a ?crit : > We hope that this will make the docs much easier to edit and contribute > to (although building the PDF version still requires 1GB of TeX...). Bug 961398 lets you build the PDF doc using rst2pdf instead of pdflatex. So instead of 1.1Gb, you only need a few Mb. LpSolit From justdave at bugzilla.org Tue Jan 21 05:09:16 2014 From: justdave at bugzilla.org (Dave Miller) Date: Tue, 21 Jan 2014 00:09:16 -0500 Subject: Bugzilla explanatory presentation In-Reply-To: <519F928C.7040104@mozilla.org> References: <519F928C.7040104@mozilla.org> Message-ID: <52DE00FC.1020607@bugzilla.org> So I just re-found this in my old mail... did this ever happen? The topic came up recently in an internal discussion at Mozilla about trying to explain to people how to use Bugzilla, and johnath's video came up as an out-of-date-but-useful example. Gervase Markham wrote: > I'm writing the script for an explanatory Popcorn presentation about > Bugzilla (focussing on BMO). I've done a draft, and I'd really > appreciate review comments: > > https://wiki.mozilla.org/Capture_Mozilla/Bugzilla -- Dave Miller http://www.justdave.net/ IT Infrastructure Engineer, Mozilla http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From gerv at mozilla.org Tue Jan 21 10:49:27 2014 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 21 Jan 2014 10:49:27 +0000 Subject: Bugzilla explanatory presentation In-Reply-To: References: <519F928C.7040104@mozilla.org> Message-ID: <25GdncpPVccqzUPPnZ2dnUVZ_rSdnZ2d@mozilla.org> On 21/01/14 05:09, Dave Miller wrote: > So I just re-found this in my old mail... did this ever happen? The > topic came up recently in an internal discussion at Mozilla about trying > to explain to people how to use Bugzilla, and johnath's video came up as > an out-of-date-but-useful example. There's a script, and even a recording of the script - it "just" requires someone to go through and set it to screenshots etc. in Popcorn. It's was on my ToDo list for a while, then someone offered to do it, so I passed it off to them, but they didn't have time, so I have it back now. If anyone is interested in doing this, it would be great :-) Otherwise, I'll try and get to it soon. But it needs a chunk of time and a decent net connection. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From justdave at bugzilla.org Sun Jan 26 07:08:14 2014 From: justdave at bugzilla.org (Dave Miller) Date: Sun, 26 Jan 2014 02:08:14 -0500 Subject: Simon has left the building Message-ID: <52E4B45E.2000302@bugzilla.org> Just to let everyone know, Simon Green stepped down from his approver/reviewer role in the Bugzilla project this last week. So anything you would have sent him previously should go to myself or Byron (glob) now. -- Dave Miller http://www.justdave.net/ IT Infrastructure Engineer, Mozilla http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From gerv at mozilla.org Tue Jan 28 17:54:54 2014 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 28 Jan 2014 17:54:54 +0000 Subject: SecureMail on BMO Message-ID: dveditz writes in a bug: "I believe the bugzilla-security folks have actively rejected encrypted mail." Can someone remind me when we did that, and why? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Tue Jan 28 20:43:36 2014 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Tue, 28 Jan 2014 21:43:36 +0100 Subject: SecureMail on BMO In-Reply-To: References: Message-ID: <52E81678.40105@gmail.com> Le 28. 01. 14 18:54, Gervase Markham a ?crit : > dveditz writes in a bug: "I believe the bugzilla-security folks have > actively rejected encrypted mail." > > Can someone remind me when we did that, and why? We chatted about this briefly on IRC in April 2011. But this discussion doesn't need to take place here, only with members of the security group. LpSolit From hilel14 at gmail.com Fri Jan 31 06:57:33 2014 From: hilel14 at gmail.com (hilel14 .) Date: Fri, 31 Jan 2014 08:57:33 +0200 Subject: Bi-directional text support Message-ID: Hello all This is my first post to this list. I created a special localization package, to provides Bi-directional text support for some default (English) templates. Here is the link to the project: https://sourceforge.net/projects/bugzilla-bidi/ How can I get this project added to the list of localization packages? Regards, Hilel Yits?aki _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Fri Jan 31 10:03:21 2014 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 31 Jan 2014 10:03:21 +0000 Subject: Bi-directional text support In-Reply-To: References: Message-ID: <52EB74E9.3090802@mozilla.org> On 31/01/14 06:57, hilel14 . wrote: > How can I get this project added to the list of localization packages? Which list? If it's on the wiki, then just add it yourself :-) Gerv From lhenry at mozilla.com Fri Jan 31 17:49:13 2014 From: lhenry at mozilla.com (Liz Henry) Date: Fri, 31 Jan 2014 09:49:13 -0800 Subject: Bi-directional text support In-Reply-To: References: Message-ID: <52EBE219.5060509@mozilla.com> Hi Hilel, welcome! I'm not sure, but this may be the page to add to, https://wiki.mozilla.org/Bugzilla:L10N Though it is perhaps not supporting any particular language, it could go somewhere on these pages, maybe on the list of various localization teams (https://wiki.mozilla.org/Bugzilla:L10n:Localization_Teams) or the Localization Guide. Best, LIz On 1/30/14 10:57 PM, hilel14 . wrote: > Hello all > > This is my first post to this list. > I created a special localization package, to provides Bi-directional text > support for some default (English) templates. > Here is the link to the project: > https://sourceforge.net/projects/bugzilla-bidi/ > > How can I get this project added to the list of localization packages? > > > > Regards, > > Hilel Yits?aki > _______________________________________________ > dev-apps-bugzilla mailing list > dev-apps-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-apps-bugzilla > -- Liz Henry lhenry at mozilla.com _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Fri Jan 31 17:46:40 2014 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 31 Jan 2014 18:46:40 +0100 Subject: How to document our minimum module versions Message-ID: Our documentation currently attempts to tell people the minimum version of the required and optional Perl modules they will need. However, there is a problem. The .rst file which contains this info is built by makedocs.pl - and makedocs.pl is not run when the docs are compiled by ReadTheDocs. So the substitution values are not available. The result looks like this: http://bugzilla.readthedocs.org/en/latest/modules.html (Note that this is not the mainline install docs; it's designed for manual install of Perl modules.) This problem is: https://bugzilla.mozilla.org/show_bug.cgi?id=964849 The version data is stored in Bugzilla/Install/Requirements.pm. The initial solution which suggests itself is to write a parser for the Requirements.pm data structures in Python. However, these are not straight data structures. The minimum version of some modules depends on whether you are on Windows, and for others it depends on your Perl version. (This leads to bug 428793, which notes that the docs can lie to you about the required minimum version if they were compiled on a computer with a different OS or Perl version to your own.) So, it seems to me that, if we want to continue to have this info in the docs, the best fix is to remove that data and place it in a JSON file, which can be parsed by either Perl or Python. That file could have a specific section for the differing requirements of Windows. If the varying minimums depending on Perl version are still required, it could also have a way of indicating when the minimum version depended on your Perl version, and what the options were. The docs would then attempt to explain all this to the user. However, this would be a reasonable amount of work. Another possibility is to remove this information from the documentation entirely, and require that people run checksetup.pl --check-modules on their target system in order to get it. (Running with --check-modules has no side effects and does not take any installation steps.) This would be the simplest fix, and is preferable if it's acceptable to people. Given that running checksetup is a required step for installation anyway, it's not a hardship. If people wanted a printed list, we could even link them to the relevant code in our BZR repo, as the data structure is not hard to read for a human. I'd prefer to do the latter, but welcome your comments. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From spamsux at forgetit.org Fri Jan 31 18:51:15 2014 From: spamsux at forgetit.org (Steve Wendt) Date: Fri, 31 Jan 2014 10:51:15 -0800 Subject: How to document our minimum module versions In-Reply-To: References: Message-ID: On 1/31/2014 9:46 AM, Gervase Markham wrote: > Our documentation currently attempts to tell people the minimum version > of the required and optional Perl modules they will need. > Another possibility is to remove this information from the documentation > entirely, and require that people run checksetup.pl --check-modules Perhaps a tangential issue, but I find it very helpful when the upgrade notes indicate new/changed module requirements. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Fri Jan 31 18:58:03 2014 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Fri, 31 Jan 2014 19:58:03 +0100 Subject: How to document our minimum module versions In-Reply-To: References: Message-ID: <52EBF23B.4070906@gmail.com> Le 31. 01. 14 18:46, Gervase Markham a ?crit : > list, we could even link them to the relevant code in our BZR repo, as > the data structure is not hard to read for a human. No need. Requirements are already listed in the release notes: http://www.bugzilla.org/releases/4.4.2/release-notes.html#v44_req_perl