Watch the April 4 Bugzilla Project Meeting

by Dave Miller (justdave)

Below are the minutes from today’s Bugzilla meeting along with a link to the video recording of the meeting.

video of this meeting

1. Updates from Dylan
   1. CyberShadow is a big help getting Harmony in shape to be run by itself
   2. If you’re making a large change, make lots of small pull requests if possible (they can be on the same bug) as it makes it easier to review. That’s been working very well with CyberShadow’s changes.
   3. Bugzilla (Harmony) now working with Mojolicious which is a big deal (mostly for OAuth2 compatibility)
   4. “Rake me over the coals if there’s no 5.0.{next} release by the next meeting”
2. Updates from Dave
   1. Still waiting on hosting info for our bots and email from Mozilla, hopefully soon
   2. History section on the website has been moved to the About page. It’s been updated with the help of Asa Dotzler correcting some inaccuracies and expanding it based on old Mozilla press releases and commit records. https://www.bugzilla.org/about/
3. Next meeting is on Wednesday, May 2, at 9pm BST (UTC+1), 4pm EDT (UTC-4), 1pm PDT (UTC-7)

Watch the March 7 Bugzilla Project Meeting

by Dave Miller (justdave)

There was a lot of good information in today’s project meeting.  Below are the minutes from the meeting as well as a link to the video recording of the meeting.  Be sure to check out and comment on the new project roadmaps!

video recording of this meeting

• Appoint note taker and get them editing the Etherpad
  • justdave
• We now have a new set of roadmaps
  • Dylan gave a walkthrough of the new roadmaps - https://github.com/bugzilla/harmony/wiki
  • watch the meeting video recording for commentary (it’s good stuff!)
• Infrastructure updates
  • www.bugzilla.org was switched over to GitHub Pages finally - this gets it out of Mozilla’s internal hosting infrastructure and into somewhere the Bugzilla project has some amount of control over.
    • typo fixes and other pull requests welcome at https://github.com/bugzilla/bugzilla.github.io
  • We have a couple leads on hosting for the remaining Bugzilla project infrastructure - will hopefully have movement on this in the next month or so. (we have until August to get out of Mozilla’s old datacenter)
• Any other business
  • none brought up.

The next meeting will be on Wednesday, April 4, at 20:00 UTC (9pm BST / 4pm EDT / 1pm PDT)

Release of Bugzilla 5.1.2, 5.0.4, and 4.4.13

by Bugzilla Team

Today we have several new releases.

All of today’s releases contain security fixes. We recommend that all Bugzilla administrators read the Security Advisory that was published along with these releases.

Bugzilla 5.0.4 is our latest stable release. It contains various useful bug fixes and security improvements:

• Download 5.0.4
• Release Notes for 5.0.4

Bugzilla 4.4.13 is a security update for the 4.4 branch:

• Download 4.4.13
• Release Notes for 4.4.13

Bugzilla 5.1.2 is an unstable development release. This release has not received QA testing from the Bugzilla Project, and should not be used in production environments. Development releases exist as previews of the features that the next major release of Bugzilla will contain. They also exist for testing purposes, to collect bug reports and feedback, so if you find a bug in this development release (or you don’t like how some feature works) please tell us.

• Download 5.1.2

Release of Bugzilla 4.4.12, 5.0.3, and 5.1.1

by Bugzilla Team

Today we have several new releases for you!

All of today’s releases contain security fixes. We recommend that all Bugzilla administrators read the Security Advisory that was published along with these releases.

Bugzilla 5.0.3 is our latest stable release. It contains various useful bug fixes and security improvements:

• Download 5.0.3
• Release Notes for 5.0.3

Bugzilla 4.4.12 is a security update for the 4.4 branch:

• Download 4.4.12
• Release Notes for 4.4.12

Bugzilla 5.1.1 is an unstable development release. This release has not received QA testing from the Bugzilla Project, and should not be used in production environments. Development releases exist as previews of the features that the next major release of Bugzilla will contain. They also exist for testing purposes, to collect bug reports and feedback, so if you find a bug in this development release (or you don’t like how some feature works) please tell us.

• Download 5.1.1

Note:Make sure ImageMagick is up-to-date if the BmpConvert extension is enabled. If no updated ImageMagick version is available for your OS, we recommend to disable the BmpConvert extension for now (bug 1269793).

Release of Bugzilla 5.0.2, 4.4.11, and 4.2.16

by Bugzilla Team

Today we have several new releases for you!

All of today’s releases contain two security fixes. We recommend that all Bugzilla administrators read the Security Advisory that was published along with these releases.

Bugzilla 5.0.2 is our latest stable release. It contains various useful bug fixes and security improvements:

• Download 5.0.2
• Release Notes for 5.0.2

Bugzilla 4.4.11 is a security update for the 4.4 branch:

• Download 4.4.11
• Release Notes for 4.4.11

Bugzilla 4.2.16 is a security update for the 4.2 branch:

• Download 4.2.16
• Release Notes for 4.2.16

EOL for 4.2.x

With this release, Bugzilla 4.2 is now end-of-lifed. This means no fixes of any kind will be issued for Bugzilla 4.2 from today onwards. All Bugzilla admins are encouraged to upgrade to the latest version of Bugzilla, especially those running 4.2 or earlier.

Release of Bugzilla 5.0.1, 4.4.10, and 4.2.15

by Bugzilla Team

Today we have several new releases for you!

All of today’s releases contain security fixes. We recommend that all Bugzilla administrators read the Security Advisory that was published along with these releases.

Bugzilla 5.0.1 is our latest stable release. It contains various useful bug fixes and security improvements:

• Download 5.0.1
• Release Notes for 5.0.1

Bugzilla 4.4.10 is a security and bug fix update for the 4.4 branch:

• Download 4.4.10
• Release Notes for 4.4.10

Bugzilla 4.2.15 is a security and bug fix update for the 4.2 branch:

• Download 4.2.15
• Release Notes for 4.2.15

Bugzilla 4.2 will be EOL on 2015/11/30

by Bugzilla Team

As discussed on the Bugzilla developers mailing list/newsgroup and confirmed by project leads, Bugzilla’s new release policy is to end-of-life the oldest supported major version four months after a new major release. Since this is the first time we’re enacting this policy, we’ve extended the date to be 4 months from today rather than from Bugzilla 5.0’s exact release date (July 7th).

Thus Bugzilla 4.2 will be end-of-lifed on 30 November 2015. This means no fixes of any kind will be issued for Bugzilla 4.2 from that date onwards. As usual, all Bugzilla admins are encouraged to upgrade to the latest version of Bugzilla as soon as possible, especially those running 4.2 or earlier.

To expand a bit further on our new EOL process, after a new major release, we will support three major releases (including the new one) for four months. After four months, we will drop support for the oldest one. We will continue to support the remaining two until four months after the next release.

For example, currently we support 4.2, 4.4, and 5.0. In four months’ time we will drop support for 4.2 and support only 4.4 and 5.0. When the next major version comes out, it may be 6.0 instead of 5.2 depending on the changes, we will support 4.4, 5.0, and 5.2. Four months later, we will drop support for 4.4 and support only 5.0 and 5.2.

Bugzilla 4.2 will be EOL on 2015/11/30

by Mark Côté (mcote)

As discussed on the Bugzilla developers mailing list/newsgroup and confirmed by project leads, Bugzilla’s new release policy is to end-of-life the oldest supported major version four months after a new major release. Since this is the first time we’re enacting this policy, we’ve extended the date to be 4 months from today rather than from Bugzilla 5.0’s exact release date (July 7th).

Thus Bugzilla 4.2 will be end-of-lifed on 30 November 2015. This means no fixes of any kind will be issued for Bugzilla 4.2 from that date onwards. As usual, all Bugzilla admins are encouraged to upgrade to the latest version of Bugzilla as soon as possible, especially those running 4.2 or earlier.

To expand a bit further on our new EOL process, after a new major release, we will support three major releases (including the new one) for four months.  After four months, we will drop support for the oldest one.  We will continue to support the remaining two until four months after the next release.

For example, currently we support 4.2, 4.4, and 5.0.  In four months’ time we will drop support for 4.2 and support only 4.4 and 5.0.  When the next major version comes out, perhaps 5.2¹, we will support 4.4, 5.0, and 5.2.  Four months later, we will drop support for 4.4 and support only 5.0 and 5.2.

Mark Côté
Assistant Project Lead, Bugzilla

Release of Bugzilla 5.0

by Bugzilla Team

Today the Bugzilla Project is extremely proud to announce the release of Bugzilla 5.0!

It has been slightly over two years since we released Bugzilla 4.4 on May 2013. This new major release comes with many new features and improvements to WebServices and performance.

We hope that you enjoy and appreciate the results of the past two years of hard work by our entirely-volunteer community.

• Download 5.0
• Release Notes for 5.0

EOL for 4.0.x

Please note that the release of Bugzilla 5.0 also marks End Of Life for the Bugzilla 4.0 series, meaning that there will be no further updates for the 4.0.x series, even if there are serious security issues found in that series. We recommend that all installations running the 4.0 series upgrade as soon as possible to 5.0.

VCS updates: bzr moving, cvs ending

by Mark Côté (mcote)

At the Bugzilla project meeting on 2015-03-25 the project lead and assistant leads agreed on two major changes to Bugzilla’s source-code hosting:

1. CVS support is officially dropped as of now. 4.0 is the last version that was released on CVS, and it will be EOLed when 5.0 comes out (very soon; rc3 was just released). In the event of a release on the 4.0 branch before it is EOLed, any Bugzilla installations that have not migrated to bzr or git will have to apply patches to upgrade, which will continue to be distributed as usual. Bugzilla site admins are strongly encouraged to migrate to pulling from git.mozilla.org as soon as possible.
2. Bazaar hosting has been officially switched from bzr.mozilla.org to bzr.bugzilla.org. bzr.bugzilla.org is already active and syncing changes from git.mozilla.org. bzr.mozilla.org is no longer syncing changes and will soon be shut down. Any sites upgrading from bzr.mozilla.org must do one of the following to apply any future upgrades, in order of preference:

• Switch to upgrading from git.mozilla.org.
• Switch to pulling from bzr.bugzilla.org. See instructions at https://bzr.bugzilla.org/.
• Apply the released patch.

bzr.bugzilla.org will continue to mirror changes from git.mozilla.org for the 4.0, 4.2, and 4.4 branches as long as they are supported. Note that, at the moment, master/trunk is being mirrored as well, but no other branches, including and subsequent to 5.0, will be mirrored to bzr.bugzilla.org, and trunk mirroring may cease at any time.

Note that bzr.bugzilla.org is waiting on a proper certificate; please use plain http until this is resolved.

The Bugzilla team apologizes for any inconvenience. Please see our support options if you have trouble migrating.

Mark Côté

Assistant Project Lead, Bugzilla