|Main Archive Page > Month Archives > spamassassin-dev archives|
3.4.0 release candidate scheduled for today. How is that going? Kevin,
are you officially release manager? What needs to be done?
On 09/14, Kevin A. McGrail wrote:
> So I think we have consensus from PMC members but just to be clear,
> here's my first pass at a high-level to-do list which I vote +1.
> Please note, this is likely a PMC only vote so I'm cc'ing the PMC
> list as well.
> - 3.4.0 will be the next release
> - 3.3.x development is ceased barring a major bug and we won't
> backport changes currently in trunk to 3.3
> - Add 3.4 SVN branch and 3.4.0 as a version for Bugzilla
> - Add 3.4.1 as a version for Target Milestone
> - Trunk switches to R-T-C as of today, 9/14 in preparation for the release
> - Create a 3.4 branch in SVN based on trunk ASAP (I think there are
> technical hurdles that make waiting until after the release
> - Go through the 715 open bugs and identify the goals to finalize
> for 3.4.0 release
> - Move all open bugs tagged for 3.3.x to 3.4.0 or 3.4.1 later based on goals
> - Any patches to remove from 3.4.0? I know we have a bug or two
> with rules that are disabled/removed to resolve.
> - Open/edit bugs for 3.4.0 that have been discussed but not
> formalized such as the sa-update and ipv6 hurdles
> - Add a jenkins/hudson build for the 3.4.x branch
> - Add DNS entries and make sure rule updates are ready for 3.4.x branch
> - Goal is to prepare an rc1 for 3.4.0 on or about 9/30 through
> normal procedures, voting, etc. moving toward an eventual release
> shortly thereafter
> - Post-release, trunk and 3.4 branch will be kept in sync perfectly
> and all programmers will write code with zero bugs ;-)
> Anything I missed?
-- "There never has been an answer. There never will be an answer. That's the answer." - Gertrude Stein http://www.ChaosReigns.com