Blog

Want to always keep up-to-date with Bugzilla news? Subscribe to announce@bugzilla.org, a read-only mailing list where we'll post announcements about new versions of Bugzilla and security advisories.

Browse Archives »

You can also see what's going on in the project by looking at the notes of, or watching the video of, our monthly developer meetings.

Loading the upcoming event

26. February 2007

Status Update

by Max Kanat-Alexander (mkanat)

Introduction and Updates

Today we’ve released the first Release Candidate for Bugzilla 3.0! This has been fairly well-tested, since the code is running on bugzilla.mozilla.org and it’s also been fully tested by our QA Team.

Localizers: Now is a good time to start translating templates for Bugzilla 3.0! We’re going to freeze the templates as much as possible between now and the final release of 3.0, so if you translate the templates for rc1, you’ll easily have a 3.0 translation.

About Bugzilla 3.0rc1

The best place to find out about the release is the release notes, which are now in HTML and linked from the front page of every installation by default.

Provided all goes well with RC1, we expect to release the final version of Bugzilla 3.0 within a few weeks. If you find any important bugs that you think should prevent release of Bugzilla 3.0, please file them and put a “?” in the blocking3.0 flag.

Plugins!

One thing we’d really like to see for Bugzilla 3.0 is some plugins! Bugzilla 3.0 has a lot of ways to write plugins, and if it doesn’t support what you want to do with your plugin, we’d be happy to add hooks for you. Right now we don’t have a standard place to store plugins, but if you make one, link it from the Bugzilla Addons page, and then tell us on the developers mailing list.

Also, if you know of any Bugzilla addons (or any other product that interacts with Bugzilla) that aren’t listed on that page, please add them!

What’s Going on with the Bugzilla Project?

This is the little section where we tell you about the development team and new news about the actual development process.

We’re just about to start work on our roadmap for Bugzilla 3.2, which will control our development for the next 6-9 months. We have a draft roadmap up now.

Max Kanat-Alexander (mkanat) and Frédéric Buclin (LpSolit) now have the power to approve bugs for checkin, meaning that there are now four “approvers” (including justdave and myk).

We have some plans to make it even easier to contribute to Bugzilla! Stay tuned to www.bugzilla.org for details.

Upcoming EOL for Bugzilla 2.18

Users of Bugzilla 2.18 should be aware that it will reach End-Of-Life with the final release of Bugzilla 3.0. Once Bugzilla 3.0 is released, no new patches will be released for Bugzilla 2.18, even for security issues.

We recommend that all Bugzilla 2.18 users upgrade to 2.22.2 (or 3.0, when it comes out) at their earliest convenience.

Stay Updated About Bugzilla

As usual, we’d like to remind all Bugzilla administrators that to assist them in keeping up-to-date with release announcements and security advisories, we provide an ultra-low-volume administrator mailing list ([email protected]). We advise all Bugzilla administrators to subscribe so they can keep up with important Bugzilla announcements.

Those looking to get involved with Bugzilla development may want to consider joining the developers list ([email protected]). This list offers discussion on new features and issues. Developers are invited to subscribe to the list. You may also want to read our Contributor’s Guide.

Bugzilla Meetings

Come to our meetings every other week! Anybody is welcome to attend who is interested in helping out with the Bugzilla Project, or just anybody who wants to put in their two cents on how development should go.

You can learn more about the meetings at the wiki page about Bugzilla Meetings.

26. February 2007

Release of Bugzilla 3.0rc1

by Bugzilla Team

We’ve released our first Release Candidate of Bugzilla 3.0, Bugzilla 3.0rc1! This is a major step towards our final release, and with your help we should be able to release Bugzilla 3.0 by April.

What help do we need? Report bugs! The whole purpose of Release Candidates is to really shake out any remaining bugs that we haven’t found, so if you find one, make sure that you file it!

We also have a new Status Update for you, so you can find out what’s going on with the Bugzilla Project!

02. February 2007

Release of Bugzilla 2.22.2, 2.20.4, and 2.23.4

by Bugzilla Team

Bugzilla 2.22.2 is a bug-fix and security release:

We also released Bugzilla 2.20.4, a security-fix release for the 2.20 series.

Finally, you can use Bugzilla 2.23.4 in your testing environments. 2.23.4 is fairly stable, since it’s currently running on bugzilla.mozilla.org, but it still hasn’t gone through QA yet, so it may have unfound critical issues.

There is a Security Advisory for all three releases. Please read it, particularly if you were using 2.23.3.

15. October 2006

Status Update

by Max Kanat-Alexander (mkanat)

Introduction and Updates

Well, we have a whole bunch of releases out today, all the way from 2.18.6 to 2.23.3.

  • 2.18.6 and 2.20.3 are primarily security fix releases.
  • 2.22.1 is our first bug-fix release for the 2.22 series, containing many useful fixes. We recommend everybody upgrade to 2.22.1 as soon as possible.
  • 2.23.3 is one of our most important development releases ever, containing the two “holy grails” of Bugzilla development, custom fields and mod_perl support. (Of course, the release is only a development snapshot, so don’t use it in production! It hasn’t received the same level of QA as the other releases!)

Bugzilla development has been extremely active lately, and we’re happy that we’re receiving so many contributions. As usual, though, we need more reviewers! To become a reviewer, you first have to be a consistent contributor, and then we have to trust your judgement. You can see more details at the List of Reviewers.

Stay Updated About Bugzilla

As usual, we’d like to remind all Bugzilla administrators that to assist them in keeping up-to-date with release announcements and security advisories, we provide an ultra-low-volume administrator mailing list ([email protected]). We advise all Bugzilla administrators to subscribe so they can keep up with important Bugzilla announcements.

Those looking to get involved with Bugzilla development may want to consider joining the developers list ([email protected]). This list offers discussion on new features and issues. Developers are invited to subscribe to the list. You may also want to read our Contributor’s Guide.

About Our Latest Development Release (2.23.3)

This tops 2.23.2 as one of our most feature-packed development releases ever. However, it is not strongly QA-tested, so use it at your own risk! We don’t recommend using it in a production environment. We know there are bugs in it.

Here’s a listing of some of the major improvements and changes since 2.23.2:

  • Custom Resolutions: You can now customize the list of resolutions for bugs.
  • Shared Queries: You can share saved queries with a group of users.
  • Custom Fields: Administrators can add plain-text and drop-down custom fields to Bugzilla. Note that you can search these fields using the Boolean Charts at the bottom of the search page.
  • mod_perl: Bugzilla can now run under mod_perl. See lower in this Status Update for more details.
  • XML-RPC: This version of Bugzilla has the beginnings of an XML-RPC interface. Note that the XML-RPC API is not yet stable, and may change before the release of Bugzilla 3.0. However, any documented function is likely to stay the same in the actual release as it is now.
  • Skins: Bugzilla is now skinnable. See the documentation for details.
  • You can now specify a Default CC for a component.
  • You can now disable Bugzilla’s sending of email to a particular user, in the administrative interface.
  • There’s a parameter for administrators to put an announcement at the top of all Bugzilla pages.
  • You can make a bug ASSIGNED when you file it, now.
  • If you aren’t allowed to change a field on a bug, it will look like plain text instead of a form element.
  • All of Bugzilla’s emails are now in templates.
  • Some of the messages printed out during installation can now be localized.
  • If you are using Firefox 2 or Internet Explorer 7, you can install a Search Plugin that will let you search Bugzilla bugs.

Also, the following changes may interest developers or customizers of Bugzilla:

  • When you build the documentation, the Bugzilla POD documentation will be available as docs/html/api/ in your installation. The POD describes all of the internal functions of Bugzilla. It’s very useful for customizers and developers of Bugzilla. It also explains how a few scripts work, like checksetup.pl, and that information is useful to all administrators of Bugzilla.
  • checksetup.pl has been completely reorganized into modules in the Bugzilla::Install namespace. It also has POD now, so you can do perldoc checksetup.pl to see all kinds of useful information about it.
  • Bugzilla::Object now has many more abilities, including the ability to create and update objects in the database.
  • You may notice a huge cleanup in post_bug.cgi and the creation of Bugzilla::Bug->create.
  • localconfig variables are now accessed through Bugzilla->localconfig.
  • UserInGroup has been removed. You should use Bugzilla->user->in_group instead.

mod_perl Support

Bugzilla now can be run under mod_perl. This allows for pages to load much faster (up to six times faster) than they did previously. However, it uses up much more memory than Bugzilla did previously. So if you’re going to use it, make sure that you have enough memory available, around 1.5GB.

We’d really like some testing of Bugzilla under mod_perl! We know that some things don’t work under mod_perl yet. You can see that at the tracking bug and its dependency list.

For more details, see the documentation.

The Road to Bugzilla 3.0

Bugzilla development freezes two weeks after today, meaning that no new enhancements will be accepted–we’ll focus on fixing bugs. We then hope to have Bugzilla 3.0rc1 out by the end of the year, and the final Bugzilla 3.0 by early 2007.

To see our current plans, you can watch the Bugzilla Calendar. It reflects only our current plans–it may change at any time.

Upcoming EOL for Bugzilla 2.18

Users of Bugzilla 2.18 should be aware that it will reach End-Of-Life with the final release of Bugzilla 3.0. Once Bugzilla 3.0 is released, no new patches will be released for Bugzilla 2.18, even for security issues.

We recommend that all Bugzilla 2.18 users upgrade to 2.22.1 (or 3.0, when it comes out) at their earliest convenience.

Bugzilla Meetings

Come to our meetings every other week! Anybody is welcome to attend who is interested in helping out with the Bugzilla Project, or just anybody who wants to put in their two cents on how development should go.

You can learn more about the meetings at the wiki page about Bugzilla Meetings.

15. October 2006

Release of Bugzilla 2.18.6, 2.20.3, 2.22.1, and 2.23.3

by Bugzilla Team

We have many releases for you, today:

  • Bugzilla 2.18.6 and Bugzilla 2.20.3 are security-fix releases for our older branches. (Bugzilla 2.20.3 also contains some non-security bug fixes.)
  • Bugzilla 2.22.1 is our first bug-fix release in the 2.22 series, and contains many useful fixes that improve the experience of using Bugzilla.
  • Finally, we are releasing an unstable development snapshot, Bugzilla 2.23.3. This snapshot has both custom fields and mod_perl support, but has not been tested as thoroughly as our other releases. The 2.23 series will eventually culminate in Bugzilla 3.0.

Also, read our latest Status Update to find out what’s going on with the Bugzilla Project, and learn about all the new features in our latest development snapshot!

Users of the 2.18.x series should note that 2.18.x will reach End Of Life when Bugzilla 3.0 is released. There are more details in the Status Update.

09. July 2006

Status Update

by Max Kanat-Alexander (mkanat)

Introduction and Updates

Today we released a development snapshot only. We’ve done a lot of coding on the trunk, and we wanted to get out a new version to be tested. Most of the branches (2.18, 2.20, and 2.22) are pretty stable, so they don’t urgently need a release at this time. We may be coming out with some bug fix releases for those in the coming months, though.

As usual, we’d like to remind all Bugzilla administrators that to assist them in keeping up-to-date with release announcements and security advisories, we provide an ultra-low-volume administrator mailing list ([email protected]). We advise all Bugzilla administrators to subscribe so they can keep up with important Bugzilla announcements.

Those looking to get involved with Bugzilla development may want to consider joining the developers list ([email protected]). This list offers discussion on new features and issues. Developers are invited to subscribe to the list. You may also want to read our Contributor’s Guide.

New Releases

2.23.2

In my totally biased opinion, this is a really exciting release. We’ve made some major changes to certain parts of the Bugzilla code, and we’re getting close to some major overall improvements.

However, it is totally untested, so use it at your own risk! We don’t recommend using it in a production environment.

Here’s a listing of some of the major improvements and changes since 2.23.1:

  • A new user preference to automatically put you on the CC list of any bug that you change.
  • The Summary field is now limited to 255 characters. Summaries longer than that will be truncated, with the original preserved in a comment, when you upgrade.
  • The “whinemail” parameter is now instead contained in a template.
  • Automatic Update Notification: Bugzilla can notify you (the administrator) automatically, on the front page, when there is a new release of Bugzilla. See the upgrade_notification parameter.
  • There is now navigation at the top of each page in addition to the bottom.
  • The UI at the top of each page has been generally improved.
  • You can now add an attachment to a bug when you are filing it!
  • checksetup.pl now displays the version of Bugzilla and the version of perl you are using.

In addition, there are a lot of changes that developers, customizers, or packagers of Bugzilla would be interested in:

  • The data formerly stored as the :locations section of Bugzilla::Config is now inside of Bugzilla::Constants. This is particularly important for packagers of Bugzilla.
  • CheckCanChangeField() has been moved from process_bug.cgi into Bugzilla/Bug.pm, and is now called check_can_change_field.
  • The entire Bugzilla::Auth structure has been entirely re-written. It should be easier to write authentication plugins for Bugzilla now. If you’re interested in writing one, just read the documentation on it by typing perldoc Bugzilla::Auth from inside your Bugzilla directory.
  • SendSQL() and all of its companion functions (including SqlQuote()) have been entirely eliminated from Bugzilla. The correct way to access the database now is to use DBI.
  • globals.pl is gone. All functions have been moved into modules in the Bugzilla/ directory.
  • Bugzilla no longer uses the data/versioncache file. If you notice any performance problems because of this, please let us know.
  • The Param() function now only exists in templates. Normal CGIs and scripts now use Bugzilla->params to access Bugzilla’s parameters. This also means most scripts don’t need to use Bugzilla::Config anymore.
  • There is a new Bugzilla::Object class that makes writing new objects even easier. See Bugzilla/Keyword.pm for an example.
  • The code for actually sending an email (MessageToMTA()) has moved into Bugzilla::Mailer.
  • There is now a Bugzilla->request_cache for storing variables that should live throughout an entire request. (For example, what used to be $Bugzilla::_cgi is now Bugzilla->request_cache->{cgi}.)

The Road to mod_perl

For many, many years, we have been working toward having Bugzilla support mod_perl, which would be a huge performance improvement.

Well, after a multi-year effort by almost every developer on the Project, we are almost there!

We should soon have a version of Bugzilla in CVS that supports mod_perl. If you’re interested, watch the mod_perl bug and its blockers. If you have any questions about mod_perl support, feel free to come into IRC and ask mkanat, if he’s around. Some other developers may be able to help you, also.

Bugzilla Meetings

Come to our meetings every other week! Anybody is welcome to attend who is interested in helping out with the Bugzilla Project, or just anybody who wants to put in their two cents on how development should go.

You can learn more about the meetings at the wiki page about Bugzilla Meetings.

09. July 2006

Release of Bugzilla 2.23.2

by Bugzilla Team

Today we have a new development snapshot for you, Bugzilla 2.23.2. It has a lot of improvements and changes since 2.23.1, so we wanted to get it out and get it tested!

However, remember that this is a development release, and so it has not been thoroughly tested. You should only use it in a testing environment!

22. April 2006

Status Update

by Dave Miller (justdave)

Introduction and Updates

This Status Update brings with it three new versions of Bugzilla. We have the final release of 2.22, a major feature update to Bugzilla (details below). We are also releasing version 2.20.2, which contains bugfixes and security updates to the 2.20 version series. And last, but not least, Bugzilla 2.23.1, a developer preview release of the codebase that will eventually become either 2.24 or 3.0. There’s a lot of other news about the Bugzilla Project included here, so keep reading!

As usual, we’d like to remind all Bugzilla administrators that to assist them in keeping up-to-date with release announcements and security advisories, we provide an ultra-low-volume administrator mailing list ([email protected]). We advise all Bugzilla administrators to subscribe so they can keep up with important Bugzilla announcements.

Those looking to get involved with Bugzilla development may want to consider joining the developers list ([email protected]). This list offers discussion on new features and issues. Developers are invited to subscribe to the list. You may also want to read our Contributor’s Guide.

The End Has Come! (of 2.16.x)

This Status Update represents a major milestone in the life of the Bugzilla Project! We are now dropping all support for the 2.16 version series. Why is this a major milestone? Because it is the longest-lived branch in the entire history of Bugzilla, and frankly, we’re tired of supporting it. :) Bugzilla 2.16 was released just shy of 4 years ago, and that’s a long time in the life of computer software. The only reason it’s lasted so long is because for a couple years we didn’t have anything to replace it with. Bugzilla 2.18 (the version to replace 2.16) has now been out for just over a year, giving most folks plenty of opportunity to upgrade.

Bugzilla has made tremendous progress since 2.16, both in terms of customizability and maintainability. Probably a good 50% of the code has been completely rewritten since then, so although it may look similar to an end user from the web (except for the obvious new features), the back end code looks completely different. The problem with all of this change, of course, is that the current version of Bugzilla is absolutely nothing like version 2.16, which makes it very difficult for us to support 2.16 because anything we backport to it has to be completely rewritten, it won’t just work with minor changes.

So if you are using Bugzilla 2.16.x, this is your last warning. You really need to upgrade if you plan to continue to get security support. We highly recommend version 2.22. Upgrading is easy if you haven’t made a lot of customizations (our upgrade script will upgrade your database schema for you). Not to mention that Bugzilla 2.22 is much more flexible and usable than 2.16. More details on that below.

Integrating with Bugzilla

I recently read a news article that talked about the CEO of Zimbra demonstrating a Zimlet that pulled data about bugs from Bugzilla when you hovered a bug number in their webmail application (among many other things he demonstrated). My first reaction was “hey, way cool!” My second reaction was “How come we didn’t know about that?” I think it’d be really useful for people who are shopping for a bug tracker to be able to see a list of all the things out there that integrate with it. You never know, someone might have already written scripts or extensions to make Bugzilla integrate with other applications they already have, and it might be a key selling point.

We set up a wiki page on the topic a while back, at https://wiki.mozilla.org/Bugzilla:Addons, but we haven’t advertised it very well. Have a look at it, and see what’s out there. And if you know of anything that’s not listed, please add it!

New Releases

2.22

Bugzilla 2.22 is a major new feature release of Bugzilla. You can see the list of major new features for details.

In addition to the user-visible features, the code for Bugzilla 2.22 is much cleaner, making it even easier to customize than before. A major new code improvement is that Products, Components, Milestones, Versions, and various other things now have real objects to represent them.

2.20.2

2.20.2 is a bug-fix release for the 2.20 series. Most importantly, users can now log in properly to a brand-new Bugzilla installation, which was broken in Bugzilla 2.20.1. 2.20.2 also includes corrections to the sidebar for admins, a fix for a problem when creating accounts using the “Env” authentication method, a new test for runtests, as well as many smaller fixes and improvements.

This is the last 2.20 release where non-critical bugs will be fixed. 2.20.3 and further will contain only security and dataloss fixes.

2.23.1

This is our completely untested development release. There are a few people using this code successfully in production, but that doesn’t mean it won’t break and destroy everything you have. If you install 2.23.1, you should do so only in a test environment.

Here’s a list of the new features or major changes in this release that are not in 2.22:

  • We require at least perl 5.8.0.
  • PostgreSQL users must use at least PostgreSQL 8.0.0.
  • Custom Fields: 2.23.1 has an extremely basic Custom Fields functionality. They only show up on show_bug.cgi. You create them with the customfield.pl script.
  • We’ve re-worked the “Format For Printing” page.
  • Emails can now have a header called X-Bugzilla-Who which specifies the Bugzilla account that made the changes. If you want this header, and you are upgrading, you have to reset your newchangedmail parameter to the default.
  • Emails also have an X-Bugzilla-Watch-Reason header, now. This contains the email address of the person you were watching and why they got the email. If you’re getting the email only because you were watching somebody, the old X-Bugzilla-Reason header will say “None.” If you got an email directly (not through anybody you’re watching), X-Bugzilla-Watch-Reason will say “None.”
  • Many other email headers were added which give information about the bug. See Bug 70710 for details.
  • “Quoted” text in comments is now displayed in a different color from normal comment text.
  • You can search for users in many different ways using editusers.cgi, now.
  • Comment fields (textareas) now zoom large when you click inside them. If you don’t like this, you can turn it off in your Preferences.
  • The “Dependency Tree” view has been redesigned.
  • You can now see what changes have been made over time to a user account. (That is, we’ve finally exposed the “profiles_activity” table in the UI.)
  • Users who wish to customize or extend Bugzilla can now take advantage of “hooks” at certain areas in the code. (See Bug 298341 for details.)
  • Bugzilla supports LDAPS connections in addition to normal LDAP connections.
  • You can now change the resolution of a bug without reopening it.
  • Administrators can delete attachments.
  • The “passwordmail” parameter is now a template instead of a parameter.
  • It’s now easy for templates to link to the documentation. (See Bug 316217 for details.)
  • We’re in the middle of removing all the global variables from the code. This means eliminating the “versioncache” file. If you notice significant performance differences between 2.22 and 2.23.1 in certain places, please let us know.
  • We’re also making a lot of progress on removing functions from globals.pl. Some functions you used in your customizations may have been moved somewhere else.

Bugzilla Meetings

The Bugzilla Project now has meetings every other week! Anybody is welcome to attend who is interested in helping out with the Bugzilla Project, or just anybody who wants to put in their two cents on how development should go.

You can learn more about the meetings at the wiki page about Bugzilla Meetings.

22. April 2006

Release of Bugzilla 2.22 (also 2.20.2 and 2.23.1)

by Bugzilla Team

The Bugzilla Project is proud to announce the official release of Bugzilla 2.22. Bugzilla 2.22 is a major new feature release for Bugzilla, containing a large number of bug fixes and enhancements, including complete PostgreSQL support, UTF-8 support, user-impersonation capabilities, and more.

We are also releasing Bugzilla 2.20.2, a bug-fix release for the 2.20 branch, recommended for all 2.20 branch users.

We also have a development snapshot, Bugzilla 2.23.1, the branch which will someday be released as 2.24 or 3.0. This snapshot is not tested, and should only be installed in a test environment. It’s entirely possible that it contains a bug which will delete your entire bug database. Or, it could be perfectly safe. Since it hasn’t been tested, nobody knows for sure. You Have Been Warned.

20. February 2006

Status Update

by Max Kanat-Alexander (mkanat)

Introduction and Updates

It’s been quite a few interesting months since our last Status Update, and there have been many interesting things happening in the Bugzilla Project! Thanks to the effort of the Bugzilla team, we’re releasing our first Release Candidate for 2.22, which has been tested by QA and we think is pretty stable! We also have a huge number of bug-fixes in 2.20.1, making the very-stable 2.20 even better. Finally, we have some security fixes the 2.18 and 2.16 branches.

The future of the Bugzilla Project looks good. We have some good plans for Bugzilla development that you can read all about below.

Oh, and if you’re using 2.16, remember that there won’t be any more security fixes for that branch after we release the final version of 2.22, which will happen very soon. That means that 2.16 will be completely “dead,” so upgrade as soon as possible!

As usual, we’d like to remind all Bugzilla administrators that to assist them in keeping up-to-date with release announcements and security advisories, we provide an ultra-low-volume administrator mailing list ([email protected]). We advise all Bugzilla administrators to subscribe so they can keep up with important Bugzilla announcements.

Those looking to get involved with Bugzilla development may want to consider joining the developers list ([email protected]gzilla.org). This list offers discussion on new features and issues. Developers are invited to subscribe to the list. You may also want to read our Contributor’s Guide.

New Releases

2.22rc1

This is our first Release Candidate of 2.22. It’s gone through QA Testing with our new Bugzilla QA Team, so we think it’s fairly stable. However, it hasn’t received a lot of wide-scale testing yet, so it should still only be used in testing environments.

However, we do encourage you to heavily test this release! We really think our next release will be 2.22 final, and it’s your feedback that will determine if that’s the case.

Since this is a Release Candidate, we also now have release notes for the 2.22 series. You can read them to see what new features and bug fixes we have in the 2.22 series.

2.20.1

Bugzilla 2.20 was one of our most stable releases ever, thanks to our QA Team. However, we still managed to fix many, many bugs for the 2.20.1 release. This is probably the most bugs we’ve ever fixed for a point release. Basically, the 2.20 series is now even more polished than it was when we first released it.

We’re aware of very few significant issues remaining on the 2.20 branch, which is good since it will likely go into “lockdown” mode with the release of 2.22. That is, only security and dataloss bugs will be fixed on the 2.20 branch after we release 2.22.

If you want to know some of the major things we fixed for 2.20.1, you can read the release notes. If you want to see everything we fixed, you can use the status changes page to see all the patches we’ve checked in on the 2.20 branch since the release of 2.20.

2.18.5 and 2.16.11

These are both just security fix releases. You can read the Security Advisory to see what we fixed.

Note that this is very likely to be the last 2.16 release, unless we do any further security fixes for the 2.16 branch along with the final 2.22 release.

Trunk Re-opens

With the release of 2.22rc1, we have branched 2.22 development, and the trunk is now open! We plan to have the trunk open for a while this time, you can read about that in the “roadmap” section below.

Anyhow, this means go ahead and start hacking away! We have many great things lined up to check in right now, such as the beginnings of custom fields. Our next release should be great.

Bugzilla Meetings

The Bugzilla Project now has meetings every other week! Anybody is welcome to attend who is interested in helping out with the Bugzilla Project, or just anybody who wants to put in their two cents on how development should go.

You can learn more about the meetings at the wiki page about Bugzilla Meetings.

Bugzilla 3.0: The Roadmap

So, we would very much like our next release of Bugzilla to be called 3.0. In our very first Bugzilla Meeting, we decided that the three critical features we would have to have for that would be:

  • mod_perl support
  • Custom Fields
  • Better Skins

As such, those are our three primary goals right now. However, some other interesting things should be getting into 3.0 as well.

We have not yet decided to break any backwards-compatibility for 2.x users. 2.x users will definitely be able to upgrade to 3.0, no matter what we decide. However, if anybody would like to propose any backward-incompatible changes, now is the time!

To help plan our development, LpSolit (Frederic Buclin) drafted a Bugzilla Roadmap and we revised it during our first Bugzilla Meeting. Check it out, it shows where we’re going and what our plans are, and it’s very up-to-date.

If you want to add something to the roadmap, attend one of our Bugzilla Meetings and make your suggestion.

Anything added to the roadmap needs somebody who can work on it. Although we’d certainly love every feature in the world to make it into 3.0, we only have a certain number of developers, and they only have a certain amount of time! That means that if you don’t have the time to code an enhancement, don’t suggest adding it to the roadmap (unless you can convince somebody else to work on it).

As you can see from the roadmap, we’re expecting our next release to be in September. Yes, that’s a long ways from now, but we’d like to call it 3.0, so we’re giving it a bit of extra time. When July rolls around we may consider doing a 2.24, but we’ll have to see how things are, at that time.

Making It Easier to Start Working on Bugzilla

We’ve been engaged in making it easier to start working on Bugzilla, if you’re a new contributor. We have a lot of ideas on how to do this, but we haven’t had time to implement all of them. If you’d like to help make life easier for new developers, come into IRC and ask what you can do to help.

Right now, you can search for bugs that have the string “[Good Intro Bug]” in the Status Whiteboard. These are bugs that Bugzilla Developers think would be good for newcomers to the Bugzilla Project. They’re usually somewhat-simple fixes that will give you an understanding of how Bugzilla works without requiring a lot of in-depth knowledge about Bugzilla.