Ok... The first milestone date has passed, and no one has even commented on this mail. So let's try it this way ... Unless I hear otherwise by 12am EST, 3/13/2004 ... This will be the release schedule for 3.0.0. It gets us a release in approx 8 weeks and is considered mildly agressive.
03/19: 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 50.
03/24: do bug squashing event for as many remaining open tickets as
possible. I assume there'll still be a few major ones open.
03/24: announce that the mass-check runs are coming soon, to help read
the docs/get an account/etc.
03/27: all tickets should be finished and closed.
03/29: announce mass-check run 1 (sets 0 and 1), run until 04/03.
04/04: generate scores, etc.
04/07: announce mass-check run 2 (sets 2 and 3), run until 04/16.
04/17: generate scores, etc.
04/19: release 3.0.0rc1 -- fix bugs that come up, do polishing, etc.
release other 3.0.0rc as appropriate.
05/05: release 3.0.0-final, have a fiesta
--
Randomly Generated Tagline:
"The cardinal rule at our school is simple. No shooting at teachers. If
you have to shoot a gun, shoot it at a student or an administrator."
- "Word Smart II", from Princeton Review Pub.
pgpUOtBka7yWT.pgp
Description: PGP signature
