Date: 2004-05-15T06:56:14
Editor: MalteStretz <mss@apache.org>
Wiki: SpamAssassin Wiki
Page: NextRelease
URL: http://wiki.apache.org/spamassassin/NextRelease
Put the release schedule here so I don't have to grep through my mailbox again
Change Log:
------------------------------------------------------------------------------
@@ -16,3 +16,38 @@
How can you help? Simple. Fix bugs. Log into [http://bugzilla.spamassassin.org Bugzilla] and browse through the bugs that are holding up the release. Fix them and attach patches to the bugs. (You may need to also fill out and send in a [http://www.apache.org/licenses/#clas Contributor License Agreement] before we can use your patch.) Also, WeLoveVolunteers.
(DuncanFindlay)
+
+== Schedule for SpamAssassin 3.0 ==
+
+The following schedule was first posted by TheoVanDinter to the SpamAssassin development mailinglist on April 21st 2004. He wrote:
+ 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
Editor: MalteStretz <mss@apache.org>
Wiki: SpamAssassin Wiki
Page: NextRelease
URL: http://wiki.apache.org/spamassassin/NextRelease
Put the release schedule here so I don't have to grep through my mailbox again
Change Log:
------------------------------------------------------------------------------
@@ -16,3 +16,38 @@
How can you help? Simple. Fix bugs. Log into [http://bugzilla.spamassassin.org Bugzilla] and browse through the bugs that are holding up the release. Fix them and attach patches to the bugs. (You may need to also fill out and send in a [http://www.apache.org/licenses/#clas Contributor License Agreement] before we can use your patch.) Also, WeLoveVolunteers.
(DuncanFindlay)
+
+== Schedule for SpamAssassin 3.0 ==
+
+The following schedule was first posted by TheoVanDinter to the SpamAssassin development mailinglist on April 21st 2004. He wrote:
+ 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