> Today we are releasing 4.4.1, 4.2.7, 4.0.11, and the unstable
> development snapshot 4.5.1.
> Initially, we released new tarballs and diffs for these releases
> to the download site but found a new bug shortly after. New tarballs
> and diffs have been uploaded to the site which we recommend everyone
> update to if you downloaded the first version. To make sure you
> have the fixed version, md5sum values are provided further down in
> the announcement.
> All of today's releases contain security fixes. We recommend
> all Bugzilla administrators to read the Security Advisory linked below.
> Bugzilla 4.4.1 is our latest stable release. It contains various
> useful bug fixes, performance improvements and security fixes for
> the 4.4 branch.
> Bugzilla 4.2.7 and 4.0.11 are security updates for the 4.2
> branch and the 4.0 branch, respectively.
> Note that 4.5.1 is an unstable development release and should not
> be used in production environments. We are not yet feature-frozen at
> this time so the features you see in 4.5.1 might not accurately
> represent the behavior that 5.0 will have.
> Note that when Bugzilla 5.0 is released, the Bugzilla 4.0.x series
> will reach end of life. If you are using that series, we encourage
> you to upgrade to 4.4.1 now.
> Bugzilla is available at:
> http://www.bugzilla.org/download/ >
> 53d0bffc3055f7d5af1c754f177de4ad bugzilla-4.5.1.tar.gz
> fd9d6dcc85bb359536be52e34ad20dfd bugzilla-4.4.1.tar.gz
> ebf0a75d1037f09994660d3958fc66fb bugzilla-4.2.7.tar.gz
> 48402a4a105de3f00962dca244cd7569 bugzilla-4.0.11.tar.gz
> Security Advisory
> There is a security advisory describing the security issues
> fixed in these releases, at:
> http://www.bugzilla.org/security/4.0.10/ >
> Release Notes & Changes
> Before installing or upgrading, you should read the Release Notes for
> the new version of Bugzilla:
> 4.4.1: http://www.bugzilla.org/releases/4.4.1/release-notes.html > 4.2.7: http://www.bugzilla.org/releases/4.2.7/release-notes.html > 4.0.11: http://www.bugzilla.org/releases/4.0.11/release-notes.html >
> It is VERY IMPORTANT to read the Release Notes if you are
> upgrading from one major version to another (like 3.6.x to 4.4.x).
> To see a list of all changes between your version of Bugzilla and
> the current version of Bugzilla, you can use the chart at:
> http://www.bugzilla.org/status/changes.html >
> The Bugzilla Update
> You can see the latest updates from the Bugzilla Project and
> the status of Bugzilla development on The Bugzilla Update:
> http://bugzillaupdate.wordpress.com/ >
> Also, you can follow the Bugzilla Project on Twitter for frequent
> updates on new features being developed in Bugzilla, our current
> release plans, and much more:
> http://twitter.com/#!/bugzilla >
> Report Bugs
> If you find a bug in Bugzilla, please report it! Instructions are
> at this URL:
> http://www.bugzilla.org/developers/reporting_bugs.html >
> You can ask questions for free on the mailing lists (or in IRC)
> about Bugzilla, or you can hire a paid consultant to help you out:
> Free Support: http://www.bugzilla.org/support/ > Paid Support: http://www.bugzilla.org/support/consulting.html >
> About Bugzilla
> Bugzilla is a "Defect Tracking System" or "Bug-Tracking System."
> Defect Tracking Systems allow individuals or groups of developers
> to keep track of outstanding bugs in their product effectively.
> Most commercial defect-tracking software vendors charge enormous
> licensing fees. Despite being "free", Bugzilla has many features
> its expensive counterparts lack. Consequently, Bugzilla has quickly
> become a favorite of thousands of organizations across the globe, and
> is widely regarded as one of the top defect-tracking systems available.
> See http://www.bugzilla.org/about/ for more details.
> - David Lawrence
> Release Manager, Bugzilla Project
> support-bugzilla mailing list
> [hidden email] > https://lists.mozilla.org/listinfo/support-bugzilla > PLEASE put [hidden email] in the To: field when you reply.