[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:

  * 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



thanks,

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
[EMAIL PROTECTED]
http://www.osafoundation.org

[EMAIL PROTECTED]
http://code-bear.com

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

* only commits that target a bug are allowed (ask the bug council to create a bug if it's urgent) 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.

PGP.sig
Description: This is a digitally signed message part

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev