Re: 3.2.0 release schedule

2007-01-19 Thread Daryl C. W. O'Shea
Justin Mason wrote: Theo Van Dinter writes: On Wed, Jan 03, 2007 at 02:42:44PM +, Justin Mason wrote: First step, I think, is to define a schedule. How does this sound? (based approximately on what we did for 3.1.0: http://wiki.apache.org/spamassassin/Release310Schedule ) - T + 0

Re: 3.2.0 release schedule

2007-01-17 Thread Justin Mason
I'm going to take the silence as assent, in the ASF lazy consensus style ;) --j. Justin Mason writes: Theo Van Dinter writes: On Wed, Jan 03, 2007 at 02:42:44PM +, Justin Mason wrote: First step, I think, is to define a schedule. How does this sound? (based approximately on what

Re: 3.2.0 release schedule

2007-01-17 Thread Theo Van Dinter
On Mon, Jan 15, 2007 at 10:56:15PM +, Justin Mason wrote: ok. so something like this? - T + 0 days: issue prerelease. announce a heads-up mail. clean up our corpora, get ready for mass-checking, try out mass-check to spot any big memory leaks or whatnot, fix remaining bugs

Re: 3.2.0 release schedule

2007-01-17 Thread Justin Mason
Theo Van Dinter writes: On Mon, Jan 15, 2007 at 10:56:15PM +, Justin Mason wrote: ok. so something like this? - T + 0 days: issue prerelease. announce a heads-up mail. clean up our corpora, get ready for mass-checking, try out mass-check to spot any big memory leaks or

Re: 3.2.0 release schedule

2007-01-17 Thread Doc Schneider
Theo Van Dinter wrote: On Mon, Jan 15, 2007 at 10:56:15PM +, Justin Mason wrote: ok. so something like this? - T + 0 days: issue prerelease. announce a heads-up mail. clean up our corpora, get ready for mass-checking, try out mass-check to spot any big memory leaks or whatnot,

Re: 3.2.0 release schedule

2007-01-15 Thread Justin Mason
Duncan Findlay writes: On Wed, Jan 03, 2007 at 02:42:44PM +, Justin Mason wrote: - T + 0 days: announce a heads-up mail. clean up our corpora, get ready for mass-checking, try out mass-check to spot any big memory leaks or whatnot, fix remaining bugs that affect mass-checks

Re: 3.2.0 release schedule

2007-01-15 Thread Daryl C. W. O'Shea
sure, +1. Justin Mason wrote: could you guys vote? I reckon, since it's part of an official release plan, we need 3 committer +1's (mine plus two more). --j. Daryl C. W. O'Shea writes: Sounds like an alright schedule to me. It'd be nice to get away with a single RC, but I hope that we

Re: 3.2.0 release schedule

2007-01-15 Thread Theo Van Dinter
On Wed, Jan 03, 2007 at 02:42:44PM +, Justin Mason wrote: First step, I think, is to define a schedule. How does this sound? (based approximately on what we did for 3.1.0: http://wiki.apache.org/spamassassin/Release310Schedule ) - T + 0 days: announce a heads-up mail. clean up our

Re: 3.2.0 release schedule

2007-01-15 Thread Justin Mason
Theo Van Dinter writes: On Wed, Jan 03, 2007 at 02:42:44PM +, Justin Mason wrote: First step, I think, is to define a schedule. How does this sound? (based approximately on what we did for 3.1.0: http://wiki.apache.org/spamassassin/Release310Schedule ) - T + 0 days: announce a

Re: 3.2.0 release schedule

2007-01-14 Thread Justin Mason
could you guys vote? I reckon, since it's part of an official release plan, we need 3 committer +1's (mine plus two more). --j. Daryl C. W. O'Shea writes: Sounds like an alright schedule to me. It'd be nice to get away with a single RC, but I hope that we have enough people test it that we

Re: 3.2.0 release schedule

2007-01-14 Thread Duncan Findlay
On Wed, Jan 03, 2007 at 02:42:44PM +, Justin Mason wrote: - T + 0 days: announce a heads-up mail. clean up our corpora, get ready for mass-checking, try out mass-check to spot any big memory leaks or whatnot, fix remaining bugs that affect mass-checks (esp bug 5260!), get

Re: 3.2.0 release schedule

2007-01-14 Thread Doc Schneider
Justin Mason wrote: could you guys vote? I reckon, since it's part of an official release plan, we need 3 committer +1's (mine plus two more). --j. Daryl C. W. O'Shea writes: Sounds like an alright schedule to me. It'd be nice to get away with a single RC, but I hope that we have enough

Re: 3.2.0 release schedule

2007-01-13 Thread Daryl C. W. O'Shea
Sounds like an alright schedule to me. It'd be nice to get away with a single RC, but I hope that we have enough people test it that we end up doing a second one. :) Daryl Justin Mason wrote: ping -- anyone there? --j. Justin Mason writes: Happy new year! New year, time for a new major

Re: 3.2.0 release schedule

2007-01-12 Thread Kevin A. McGrail
: Friday, January 12, 2007 10:17 AM Subject: Re: 3.2.0 release schedule ping -- anyone there? --j. Justin Mason writes: Happy new year! New year, time for a new major release since we missed one in 2006 ;) I think the 3.2.0 bugs list has most of the major ones off the list, and the remaining

Re: 3.2.0 release schedule

2007-01-12 Thread Sidney Markowitz
Justin Mason wrote, On 13/1/07 4:17 AM: ping -- anyone there? Yup, looks good to me. I won't be set up for participating in mass checks but I will be able to clear some of those bugs after some major life and work deadlines complete a week from now. -- sidney

Re: 3.2.0 release schedule

2007-01-12 Thread Doc Schneider
Justin Mason wrote: ping -- anyone there? --j. Justin Mason writes: Happy new year! New year, time for a new major release since we missed one in 2006 ;) Bah... I thought I had replied to this. I'll sure help with mass-checking. Just let me know when it is going to launch. -- -Doc

3.2.0 release schedule

2007-01-03 Thread Justin Mason
Happy new year! New year, time for a new major release since we missed one in 2006 ;) I think the 3.2.0 bugs list has most of the major ones off the list, and the remaining either (a) don't need to be done for 3.2.0 necessarily or (b) will probably be doable in the month or whatever between now