[Dev] Code Freeze in one week, Documentation Complete in three weeks

[Ted Leung]

Hi,

In today's Engineering Issues Meeting we discussed the progress of the 
0.4 release, and I was asked to send a reminder concerning our process.

Next Tuesday, October, 2 is our code freeze.  Between now and then, 
please observe the following rules:

1. Only check in changes which are a fix for a bug targeted for the 0.4 
release.
2. Include the bug number associated with your fix in your commit 
comments.
3. Give an English explanation of the bug being fixed.

After the code freeze, the following rules will be in effect:
1. Only fixes for bugs flagged as 0.4blocking will be accepted.
2. Bug numbers and descriptions should be included in commit comments.
3. Please have your code reviewed by at least one other person before 
checking it in.

Also, please note that Milestone 03.27 on October 19, is the 
Documentation Complete milestone, so you should be thinking about any 
documentation that will be needed, be that epydoc or a longer (HTML) 
document.   epydoc checkins will be permitted during code freeze, but 
should also be reviewed.

----
Ted Leung                 Open Source Applications Foundation (OSAF)
PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87 F5FC 4B42