The code-freeze is now happening to allow us to test the release candidates. It lasts until Sunday [3].
Code-freeze means *no* non-essential commits to the trunk or to the new release branch. Other branches are free to continue. There should be no code enhancements or new functionality, because that could introduce new bugs. The main aim is to find and fix important bugs. Any minor issues are delayed until after release (add to Jira). Documentation corrections can happen because they will not break anything. As long as we do test the documentation building just prior to making the final release candidate. However, if there are important code changes that are required you can make a proposal to allow that commit. The PMC will make a quick decision. Next important milestones are: * Create release candidate #2 if there have been changes on Friday 2005-06-17 at 22:00 UTC [2] [2] http://www.timeanddate.com/worldclock/meetingtime.html?day=18&month=06&year=2005&p1=48&p2=176&p3=240&p4=224&p5=213 * Actual release date is Sunday 2005-06-19 at 14:00 UTC [3] [3] http://www.timeanddate.com/worldclock/meetingtime.html?day=20&month=06&year=2005&p1=48&p2=176&p3=240&p4=224&p5=213 Now we will go and build the releases which might take some time. The next message will tell you where to get the release candidates and describe how to test. -David
