From: Andreas K. <aku...@sh...> - 2006-07-01 02:01:06
|
This mail has been cc'd to the conference organizers to get their input on the proposed schedules (see below) as well. Ok then, let us see how that is working out: * Have one month where the CVS is frozen except for bug work. * Have the RC (Release Candidate) ready one week before the GA (General Announcement). The CVS is fully frozen during that time except for absolute blockers. Any other work has to be either defered until after release, or put into a branch. * Make a GA the weekend before the conference begins. With the conference held from Oct 9-13 this works out to the following dates: * Frozen except for bugs from Friday Sep 1. * Release Candidate ready at Friday Sep 29. * General Announcement at Friday Oct 6. * Conference Mo-Fri Oct 9-13. (*) Which means that we have from now on 2 months for general work on bugs, patches, new features until the work is restricted to bugs only. However, I do not know how early the release has to be to get on the conference CD. If the Friday before the conference is too short I guess that we can move GA and RC one week back, for a full week between GA and conference. That would work out to the following dates: * Frozen except for bugs from Friday Sep 1. * Release Candidate ready at Friday Sep 22. * General Announcement at Friday Sep 29. * Conference Mo-Fri Oct 9-13. (*) (*) Oh, a Friday the 13th :) -- So long, Andreas Kupries <aku...@sh...> <http://www.purl.org/NET/akupries/> Developer @ <http://www.activestate.com/> ------------------------------------------------------------------------------- |