THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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.
| Wiki Markup |
|---|
Open bugs blocking 3.0.0 are tracked via the meta-bug \[http://bugzilla.spamassassin.org/show_bug.cgi?id=3208 3208\]. |
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.
...