Firefox/Thunderbird 1.5rc1 and Gecko 1.8rc1 are quickly approaching
The Release Candidate should contain no known bugs that would prevent it from being released as the 1.5 final. This means we truly need to resolve all blocker bugs before the release candidate or defer those bugs into a release post 1.5 final.
Our schedule for rc1 was posted previously here:
http://developer.mozilla.org/devnews/index.php/2005/08/30/9-days-untill-15-beta/
The scheduled date for RC1 is Friday October 28, 2005. During the beta2 release cycle we learned that we need longer than 2 days to shake out final regressions in the builds, prepare auto-update, and the l10n builds. As a result we will need to move the code lockdown to 11:59pm PDT Sunday October 23, 2005. This means all blocker bugs must be checked in on the branch by then.
The process for getting your bug into the release is as follows:
• Land changes and get them verified on CVS trunk
• Include a comment in bug about the value, the risk, and any existing tests you have run
• Request drivers’ approval by setting the set the attachment flag to approval1.8rc1?
You can now use a handy set of links at the top of the tinderbox pages to track the blocker bugs (thanks Asa and Mike Beltzner!):
http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8
As always if you have any questions you can email drivers at mozilla dot org.