Sorry for my late response, and bringing the topic back to the list (with some quotes omitted).
Warren Togami writes: > Might it be feasible to get 3.3.0 out sometime during the Fedora 12 dev > cycle? It seems there is maybe 2-3 months. A fresh spamassassin making > this release might possibly be particularly more important than other > releases for unnamed reasons... Justin writes: > It would be quite possible to do this, given a sufficiently-dedicated > release guy pushing it. It takes about 2 months to get through > mass-checks, generate good scores, etc. Unfortunately, I'm out for this > job, as child #2 is about to be born any day now ;) > > BTW in the short term, if ppl want to help 3.3.0 release plans, I suggest > trying out the SVN trunk code as "dogfood". I've been doing this for the > last couple of years with very good results; I can't recall the last time > I had to restart my spamd, for example, or spotted an FP... I've also been running a fresh 3.3 in production at our site for more than a year now, mostly because it provides bug fixes and some new features or workarounds that I need. For example with a Perl upgrade to 5.8.9 (and later to 5.10.0) on FreeBSD ports the old 3.2.5 just couldn't survive any longer without crashing due to exceeded stack size while compiling our set of rules (a perl bug). I can confirm that 3.3 fares at least as well as 3.2.5, and in many ways better. I do monitor for possible glitches, but there just aren't any (new ones that is, that would not also be in 3.2.5). I may also add that the more recent versions of amavisd-new are happier with 3.3 than with 3.2.5, as this enables some nice SA functionality (like SA timing breakdown reports, DKIM checking of long mail messages). The trouble with only a handful of sites running the new code is that not all features are exercised, and not all setups tested. Then there is a concern that some of the fixes for old bug reports would still be nice to get into a 3.3 before a release, and some nice features added/finished. Given the current progress trends this is unfortunately just stretching time to a release, rising a feeling that "it just isn't ripe yet". We might consider just setting our goal/expectations closer to ground, and come out with what we have. > I'm pretty sure this won't be achievable in that timeframe if I'm > driving the release process [...] while I'm busy running after babies ;) > guys, I can totally provide advice/guidance as to how to go about > this, if you feel up to it. > > basically this wiki page describes the basic idea of how to put > together a new x.y.0 release: > http://wiki.apache.org/spamassassin/ReleasePolicy > > the biggest task is working through this: > http://wiki.apache.org/spamassassin/RescoreMassCheck On my part I've spent less time lately on SpamAssassin then I would like. Getting the amavis release out, preparing for a conference, and then there will be a vacation time for me, so I won't be of much help until the end of July. I wonder if there's anything we could do without too much trouble to let more people start using the 3.3 code from CVS. I suppose there are still nightly tarball builds? (I haven't checked). Perhaps just giving an encouraging hint every now and then on a mailing list could be a good start. Mark
