[Dev] Feature freeze, and winding down to 0.4

[Heikki Toivonen]

As is rather obvious, having just completed the feature freeze milestone 
we should not be checking in any new features or architectural changes 
at this point in game. However, if you think you have a change that you 
think should be an exception, the bug council will hear you.

Getting closer to release also means getting more conservative and 
careful with regular bug fixes. Think about the risk and potential 
failures. Get code reviews. Run unit tests before checkin.

Once a bug is marked fixed, the fix should be verified. It would be 
polite of the person who filed the bug to go and verify the bug is fixed 
after it is marked so, but anyone except the person who fixed the bug 
can mark it verified. When you verify, please state the build identifier 
(or date when you last updated source), OS, and whether you were using 
debug or release build. Check the radiobutton "Mark bug as VERIFIED" 
before you hit commit so the bug will be resolved accurately (from FIXED 
to VERIFIED FIXED).

In order to find out the bugs we really want to get fixed for 0.4, we'll 
start using the blocking 0.4 flag in Bugzilla. Anyone can nominate a bug 
to block this release - just set the blocking0.4 flag to '?' and the bug 
council will go through these nominations to distill the final list of 
blockers. Look under the CC field in bugs for the flag. For more details 
on the end game, please refer to 
http://wiki.osafoundation.org/bin/view/Chandler/ReleaseManagementWithBugzilla

The bug council will meet early next week, most likely Tuesday afternoon.

-- 
   Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20040923/3d4c4b94/signature.bin