Thanks. One of the reasons I personally don't stress about releases formally is that as a project, I see the svn versions as production level.
On 9/2/2018 11:19 PM, Alex wrote: > Hi, > >> The key documentation changes I am referring to are the build/README >> process which I've been working to clarify so that now you can pretty >> much launch a CentOS box, install a few stock packages, upload the SA >> Signing Key, checkout the branch and roll a release in a few minutes. > That's awesome news. > >> The 3.4.2-pre5 is the same as running from SVN 3.4 branch as of when I >> ran the package. I think it was r1839733. So it's pretty safe to use >> in a production system and was in a passing state for all tests suitable >> for a release. If it builds and installs, the sha signatures work, >> etc., that's all great. > We've been running branch exclusively since what looks like 11/2016, > updating more than 20+ times since and it's almost always been stable. > There haven't been any real issues in months. This is also on some > pretty high-profile systems. > >> We have a project vote to go into Review then Commit mode in prep for a >> release so your feedback is helpful, thank you. I'm using the long >> weekend here in the US to bang through as much as I can to make 3.4.2 as >> close to the end of 3.4.x as possible. I'm thinking a 3.4.3 in a month >> and put it to bed forever to focus on 4.0. > That sounds terrific. Thanks for all you do. -- Kevin A. McGrail VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
