On 6/21/2013 11:59 AM, Mark Martinec wrote:
Ok, let me put it this way: I'd publish the RC2 as it is and let people
play with it for few days, hoping for some feedback.
Likely my poor wording in the request for a vote coupled with the length
of time since a previous release but rc2 *is* published.  You aren't
voting to publish rc2.  You're voting to make rc2 the release 3.4.0 or not.
"I'd publish the RC2 as it..." ->
   -> "Let's announce on the ML that RC2 is available for testing,
       feedback is welcome. Unless something major pops up, the
       final release will follow shortly."


I had viewed that released candidates going to dev mailing list was the announcement for testing and feedback but it seems a good idea to get the general users list involved as well. Getting it onto the website is a bit of a catch-22 I'd like to ignore for now (see Other Items below).

Could you please announce it on the users list? For rc3's vote, I will be more clear that I am asking for that rc3 to be cleared to then create the 3.4.0 release for a final official vote. I don't think there is really any Apache guidance and the process that the SA project followed should be flexible to get this long-standing release out the door as long as we have 3 PMC +1's.

*Switching to R-T-C on Monday*
- I think we are planning on rc3 so please get any patches submitted in place for Monday when we will switch to R-T-C in prep for 3.4.0.

*Bugzilla*
I've cleaned up bugzilla. If you see any bugs you'd like to tag for 3.4.0, please edit the bugs ASAP to get discussion started.

*Possible Release Blockers *
Right now, there are five: https://issues.apache.org/SpamAssassin/buglist.cgi?cmdtype=runnamed&namedcmd=3.4.&list_id=8446

6945 - Has a patch to submit
Bug 6422 & 6639 - Will be tested with rc3 on CPAN
5503 - I need to work on this and I'm doing so now.

*Important Questions:*
Should some of the info in the announcement also go into the general README file?

*Other Items*
Bug 6885 to switch the website's publishing method will be needed to update the website to announce the release.

I'll also be working through the rest of the build/README file and expect lots of issues / problems that will need to be overcome to switch to 3.4.X.

Regards,
KAM

Reply via email to