Archive for décembre 2009

Bugzilla 3.6 is now feature complete

I didn’t blog about new features in Bugzilla 3.5/3.6 for a long time (last time was more than 4 months ago) as most of my time devoted to Bugzilla these last few months was to review patches (I had 35 pending reviews in my queue at the beginning of the month, and I brought it down to only 7, none of which is critical for Bugzilla 3.6). But last week, we reached one important milestone in the development of Bugzilla 3.6 as we no longer accept new features for this branch. This means that the current 3.5.2+ code is feature complete and we will now focus on stability, polish and bug fixes only. Among others, this means fixing all blockers and writing new QA scripts. Bugzilla 3.5.3, which will be the first development snapshot to be feature complete, should be released pretty soon now, see bug 532515. Your feedback will be important as it will let us know what remains broken or badly implemented. When all blockers will be fixed, and when the QA team thinks the code is stable enough, we will release Bugzilla 3.6rc1 (somewhere in Q1 or Q2 2010). Note that the release of Bugzilla 3.6 means the end-of-life of Bugzilla 3.0, which should happen late in Q2 2010.

So, what’s new since my last post?

  • Bug 108243: As said in my previous post, bug flags can now be displayed in buglists.
  • Bug 140999: Users without editbugs privs can make comments on attachments.
  • Bug 162060: You can now use the UNCONFIRMED bug status independently of the number of votes to confirm bugs.
  • Bug 176002: Duplicates data is no longer stored in data/duplicates/ but is generated on the fly from the DB.
  • Bug 204106: enter_bug.cgi now highlights mandatory fields.
  • Bug 286625: –regenerate is much faster. This fix has also been backported to Bugzilla 3.4.2.
  • Bugs 302542 and 451716: Series in new charts can now be deleted, either individually or when deleting a product.
  • Bug 355283: After too many unsuccessful attempts to log in, your account is locked out (to prevent brute force).
  • Bug 366994: When a private comment is added to a bug, public changes are now sent to users not in the insidergroup (previously, no email was sent at all to those users).
  • Bug 381912: You can now add attachments to Bugzilla by email (using
  • Bug 421265: By default, the language used by a Bugzilla installation to display pages is based on the preferred language specified by your web browser, if available. Now you can manually change this language without having to alter your preferred language in your web browser.
  • Bugs 430010, 430014, 524229 and some others: major rewrite of the extension/plugin/hook system.
  • Bug 513593: Incoming parameters used in the WebService are now tainted, to improve security.
  • Bug 519584: A GNATS installation can now be imported into a Bugzilla installation.
  • Bug 524368: New user account passwords must now be at least 6 characters long (previous value was 3)

This is only a small list of all the hard work which has recently been done in this development cycle and doesn’t include all the bug fixes we worked on since Bugzilla 3.4. But major new features are listed here and Bugzilla 3.6 shouldn’t differ very much.

Catégories:Bugzilla, Mozilla

Recevez les nouvelles publications par mail.