We'll reach Chandler Milestone 0.5.07 today. This marks the transition point to even more conservative approach to accepting bugs for the 0.6 Release, and the Bug Council will be triaging the existing list to punt minor issues.
The Bug Council has started marking bugs with the blocking flag that we will hold the release for. All of these are changes that need to be checked in to the Chandler Subversion repository before we can create the release bits. Please work on these bugs first, if you have any. Anyone can nominate a bug to block a release: just set the blocking0.6? flag in the bug. The Bug Council will be meeting on most weekdays to go over these nominations and all incoming new bugs. You can still make changes in tests and documentation as well as fixes to issues that turn Tinderbox red/orange (build/test failures) without a bug number, but reviews are strongly recommended even for these changes. The Code Freeze milestone is about 3 weeks out, and we are aiming to have 0 bugs with blocking0.6+ flag by that date. We will only take in fixes that we would block the release for after that point - so no nice to haves even with reviewed patches. After Code Freeze we will be creating Release Candidates. If testing finds new blockers with a Release Candidate, we will fix the blockers and spin the next Release Candidate. When we are unable to find blockers in Release Candidate the latest Release Candidate will become the official 0.6 Release. We will be branching for the 0.6 release when we have 10-20 blocking bugs left. We estimate we can branch within the next 3 weeks. The release will happen from the branch while 0.7 development can start on the trunk. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
