3.0 is coming along quite well, and we should get around to planning a release schedule... From the last few releases:
2.40 09/02
2.41 09/22
2.42 10/04
2.43 10/15
2.44 01/31
2.50 02/20
2.51 03/20
2.52 03/24
2.53 03/31
2.54 05/12
2.55 05/20
2.60 09/22
2.61 12/09
2.62 01/17
2.63 01/20
... fits our "major every 6 months, minor monthly" plan pretty well.
According to this, we're due for a new major release sometime around
the end of this month. Personally, I think a "4/1" release date would
be good ... ;)
Random thoughts in my head:
- do another bug squashing event as a last push to get 3.0 released
- we need to trim down bugzilla more -- there are currently just over
300 tickets still open
- prioritize some of the bugzilla tickets so we can focus on the things
we want for 3.0
- pick a versioning structure -- cpan seems to want floating-point
numbers, we want the x.y.z scheme... I still vote for doing x.yyzz,
then handling that internally when we need to display the version
somewhere.
- we'll want at least 1 week for rc testing
- we'll need at least 2 weeks for the mass-check runs
- I assume the rc testing code will be released via ASF systems
- we'll want to again let the 3rd party devs know about the API changes
- "make test" still fails the "rules hitting themselves" test w/
<10 rules...
- if we're not going to do a release in the next month or so, we should
probably do a 2.64 release to fix some of the 2.6x issues... if we are
doing the 3.0 release, blow away the bugzilla tickets in the 2.64 queue.
So to get that in some form of order/milestones -- aggressive schedule:
03/10: 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/13: do bug squashing event for as many remaining open tickets as
possible. I assume there'll still be a few major ones open.
03/20: all tickets should be finished and closed.
03/21: announce mass-check run 1 (sets 0 and 1), run until 03/27.
03/28: generate scores, etc.
03/29: announce mass-check run 2 (sets 2 and 3), run until 04/05.
04/06: generate scores, etc.
04/07: release 3.0.0rc1 -- fix bugs that come up, do polishing, etc.
release other 3.0.0rc as appropriate.
04/15: release 3.0.0-final
Thoughts, comments?
--
Randomly Generated Tagline:
A "goto" in Perl falls into the category of hard things that should be
possible, not easy things that should be easy.
-- Larry Wall in <[EMAIL PROTECTED]>
pgpFg4Y3DAvmw.pgp
Description: PGP signature
