Daryl C. W. O'Shea writes: > Don't forget to change the current trunk/3.2 updates into 3.3 updates > and create 3.2 updates similar to 3.1 updates *before* releasing 3.2.0.
do we have to do this beforehand? I was thinking we could get away with doing it afterwards. ;) by the way -- I'm not in favour of adopting the current 3.1.x updates model for 3.2.x, where they have to be manually backported from a dev branch by hand -- it's proven fragile (there's been breakages) and is pretty much entirely neglected now (there hasn't been an update in 2 1/2 months). I think the trunk-style auto-built model works a lot better. and what use are updates if they're too hard for us to update? I'd prefer to have the auto-promotion, updates generation, etc. to output rules directly to the 3.2.x updates. The discussion at http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4982 also seems relevant... --j.
