On Tue, Apr 20, 2004 at 03:28:56PM -0400, Theo Van Dinter wrote: > I set the default milestone to 3.1.0. I'll post a proposal schedule > later today.
Here's what I came up with. These are meant to be guidelines, not hard dates. This schedule has a release in 10 weeks. I'd really like to beat that. Depending on schedules, we can probably move up the code related work. The release related stuff is pretty much the amount of time it usually takes though. CODE RELATED: 04/20: DONE - get bugzilla prioritized and either close/punt stuff we're not going to get to to 3.1. We will need to get agressive about some tickets -- for instance: we can't avoid all FPs, so if they don't happen often and if it's not easy to fix, accept it, close the ticket, and move on. Get open 3.0 tickets down to around 50. 04/22: feature freeze -- no more adding enhancements to 3.0 w/out vote 04/28: do bug squashing event for as many remaining open tickets as possible. I assume there'll still be a few major ones open. 05/12: all tickets should be finished and closed. all testing rules should be promoted or removed. do testing to make sure the mass-checks will be smooth. RELEASE RELATED: 05/07: warn people that mass-check runs will be starting shortly 05/17: announce mass-check run 1 (sets 0 and 1), run until 05/24. enter R-T-C mode. 05/26: generate scores, etc. 05/31: announce mass-check run 2 (sets 2 and 3), run until 06/11. 06/13: generate scores, etc. 06/15: release 3.0.0rc1 -- fix bugs that come up, do polishing, etc. release other 3.0.0rc as appropriate. 06/30: planned release of 3.0.0-final Thoughts, comments? -- Randomly Generated Tagline: "If we can't keep this sort of thing out of the kernel, we might as well pack it up and go run Solaris." - Larry McVoy
pgp6JiIS03AcH.pgp
Description: PGP signature
