[Dev] commit policy during the Milestone build process

[Mike Taylor]

I need to remind everyone that in the period of time right before a 
Milestone build it is imperative that the following be done:

   * only commits that target a bug are allowed (ask the bug council to 
create a bug if it's urgent)
   * the commit must have a peer review or a review by the bug council
   * the commit log should contain a "bug ####" and also a "r=foo" line
   * the dev must be on IRC in case feedback is needed

Any commit not following the above will first get an email from me and 
then get backed out - the only exceptions are when I'm told by the bug 
council otherwise.

thanks,

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
http://www.osafoundation.org

bear at code-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20050714/0a247dc2/PGP.pgp