You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by "Kevin A. McGrail" <KM...@PCCC.com> on 2011/09/14 22:21:31 UTC
DRAFT TO-DO LIST PMC VOTE - September 30th 3.4.0 release candidate
On 9/14/2011 2:58 PM, Michael Parker wrote:
>> > So I guess I'm back to my last suggestion:
>> > September: Release from trunk, version 3.4.0, svn branched to 3.4.0 (not 3.4)
>> > January: Release from trunk, version 3.4.1, svn branched to 3.4.1
> I'm -1 for this branching/release strategy.
I'm -1 as well for that strategy. Darxus, you have a false assumption
that 3.4.1 is a different branch than 3.4.0. It is not. 3.4.0, 3.4.1,
3.4.2, etc. collectively are all the same branch.
A good reason we branch instead of using trunk is that branches require
RTC while trunk does not to give some leniency to pursue some avenues
others might not enjoy. Lately, those changes haven't been very
controversial or broken anything horribly.
But, while I test with trunk, it's really the least ideal for a
production system.
The problem is that branches and trunk get out of sync require up and
back porting but that's just programming as normal on a project that is
co-maintaining multiple versions.
Our chair is not comfortable releasing from trunk and I don't feel
strongly enough about the issue to argue it.
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 difficult)
- 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?
regards,
KAM
Re: DRAFT TO-DO LIST PMC VOTE - September 30th 3.4.0 release
candidate
Posted by Quanah Gibson-Mount <qu...@zimbra.com>.
--On Wednesday, September 14, 2011 4:21 PM -0400 "Kevin A. McGrail"
<KM...@PCCC.com> wrote:
> On 9/14/2011 2:58 PM, Michael Parker wrote:
>>> > So I guess I'm back to my last suggestion:
>>> > September: Release from trunk, version 3.4.0, svn branched to 3.4.0
>>> > (not 3.4) January: Release from trunk, version 3.4.1, svn branched
>>> > to 3.4.1
>> I'm -1 for this branching/release strategy.
> I'm -1 as well for that strategy. Darxus, you have a false assumption
> that 3.4.1 is a different branch than 3.4.0. It is not. 3.4.0, 3.4.1,
> 3.4.2, etc. collectively are all the same branch.
My summary would be that Darxus simply doesn't understand revision control
systems or release engineering. Probably something he should spend some
time researching before he provides any further commentary on this thread.
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
Re: DRAFT TO-DO LIST PMC VOTE - September 30th 3.4.0 release candidate
Posted by Mark Martinec <Ma...@ijs.si>.
Kevin wrote:
> - 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
+1
> - Add 3.4 SVN branch and 3.4.0 as a version for Bugzilla
> - Add 3.4.1 as a version for Target Milestone
done.
> - Trunk switches to R-T-C as of today, 9/14 in preparation for the release
In my opinion, delay that until we have most of the pending important
fixes in the trunk.
> - Create a 3.4 branch in SVN based on trunk ASAP (I think there are
> technical hurdles that make waiting until after the release difficult)
Delay creating the 3.4 branch until just shortly before a release,
let's get the remaining fixes first. I doubt anyone will do any 'future
developement' stuff in the near future, so branching now and
fixing issues on two tracks in parallel would be a nuisance.
> - Go through the 715 open bugs and identify the goals to finalize for
> 3.4.0 release
Right. Besides fixing tickets, this triage should be now the first goal.
> - 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.
Identify and prioritize these.
> - Open/edit bugs for 3.4.0 that have been discussed but not formalized
> such as the sa-update and ipv6 hurdles
Right, the blockers IMO. The ipv6 for sa-update is now ready (Bug 6654).
The sa-update state transitions to avoid frequent downloads from mirrors
on misconfigured sites should be a priority (Bug 6655).
> - 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?
It's not too bad if we miss the target date by a week or two, as long
as we get a ball rolling.
Mark
Re: DRAFT TO-DO LIST PMC VOTE - September 30th 3.4.0 release candidate
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
Individual votes aren't publicly discussed, sorry. But I can report this looks like the plan.
Regards,
KAM
darxus@chaosreigns.com wrote:
Did this get any votes either way, other than Kevin's?
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
> difficult)
> - 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 ;-)
--
"It's never too late to panic."
http://www.ChaosReigns.com
Re: DRAFT TO-DO LIST PMC VOTE - September 30th 3.4.0 release
candidate
Posted by da...@chaosreigns.com.
Did this get any votes either way, other than Kevin's?
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
> difficult)
> - 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 ;-)
--
"It's never too late to panic."
http://www.ChaosReigns.com
Re: DRAFT TO-DO LIST PMC VOTE - September 30th 3.4.0 release
candidate
Posted by da...@chaosreigns.com.
Open bugs with a target of 3.4.0: 41
Critical: 2
Major: 3
Normal: 25
Minor: 5
Enhancement: 6
Oh, look at that, 53 open bugs with a target of 3.3.2, which was released.
What should be done with this mess?
Which ones need to get done for a release candidate?
Critical, 3.4.0 target:
sa-update might DOS mirrors if TMPDIR unwritable
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6655
0.1 years old.
need way to cut emergency rule updates with new update-generation system
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6365
1.6 years old.
Major, 3.4.0 target:
Limit corpora network test age in score generation
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6386
1.5 years old.
tok_touch_all update forces full table scan, kills performance.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6444
1.3 years old.
Looks like this one can be closed?
need to have some limits on scanned data size
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6582
0.4 years old.
--
"You will need: a big heavy rock, something with a bit of a swing to it...
perhaps Mars" - How to destroy the Earth
http://www.ChaosReigns.com
Re: DRAFT TO-DO LIST PMC VOTE - September 30th 3.4.0 release
candidate
Posted by da...@chaosreigns.com.
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
> difficult)
> - 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?
>
> regards,
> KAM
>
--
"There never has been an answer. There never will be an answer.
That's the answer." - Gertrude Stein
http://www.ChaosReigns.com