Re: Reminder:: 3.3.0 pre-release cut: December 17th
Warren Togami wrote on Wed, 16 Dec 2009 18:12:05 -0500: All bugs targeted for 3.3.0. When reviewing this list and playing around I found that there are 22 bugs for milestone 3.2.6. Shouldn't these get reviewed and promoted to 3.3.0 if still valid? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
Re: Reminder:: 3.3.0 pre-release cut: December 17th
On Thursday December 17 2009 12:49:25 Kai Schaetzl wrote: When reviewing this list and playing around I found that there are 22 bugs for milestone 3.2.6. Shouldn't these get reviewed and promoted to 3.3.0 if still valid? What usually happens is that a bug was fixed in trunk (3.3), but then (if it seemed important and not too difficult to mend) targeted for 3.2.6 just in case this release ever happens. If one can find any bugs targeted for 3.2.6 but not yet fixed in 3.3, please promote or copy them to a 3.3 target. Mark
Re: Reminder:: 3.3.0 pre-release cut: December 17th
Suggesting to postpone the wrapup date till tomorrow (December 18) to give us one more day to digest the latest changes and see where we stand. Mark
Re: Reminder:: 3.3.0 pre-release cut: December 17th
On 12/17/2009 04:24 PM, Mark Martinec wrote: Suggesting to postpone the wrapup date till tomorrow (December 18) to give us one more day to digest the latest changes and see where we stand. Mark Seconded. I guess I'm spinning the rc1 unless jm wants to do it. I'm reluctantly going to call the first cut rc1.proposed1 after the previous discussion. After the 3 day period has passed with no objections then it will be renamed to rc1 and released. Warren Togami wtog...@redhat.com
Re: Reminder:: 3.3.0 pre-release cut: December 17th
It was a good catch that RNBL replaced SSBL but I don't see this as a 3.3.0 P1 issue. Same thing with HABEAS/BSP. Can't these be handled in normal course with GA and then sa-update? I worry we are hurrying these too much. This is a reminder of the goal to cut another pre-release December 17th either named beta2 or rc1 depending on the above conditions. It is not a big deal if we need to delay the cut to the proposed deadline of December 23rd. I think a beta2 would be more appropriate. I think rc1 would be after we have all the known P1 bugs closed off. regards, KAM
Re: Reminder:: 3.3.0 pre-release cut: December 17th
On Wed, Dec 16, 2009 at 13:59, Kevin A. McGrail kmcgr...@pccc.com wrote: It was a good catch that RNBL replaced SSBL but I don't see this as a 3.3.0 P1 issue. Same thing with HABEAS/BSP. Can't these be handled in normal course with GA and then sa-update? I worry we are hurrying these too much. This is a reminder of the goal to cut another pre-release December 17th either named beta2 or rc1 depending on the above conditions. It is not a big deal if we need to delay the cut to the proposed deadline of December 23rd. I think a beta2 would be more appropriate. I think rc1 would be after we have all the known P1 bugs closed off. +1. sa-learn --backup being broken is a big deal. -- --j.
Re: Reminder:: 3.3.0 pre-release cut: December 17th
On 12/16/2009 08:59 AM, Kevin A. McGrail wrote: It was a good catch that RNBL replaced SSBL but I don't see this as a 3.3.0 P1 issue. Same thing with HABEAS/BSP. Can't these be handled in normal course with GA and then sa-update? I worry we are hurrying these too much. I rather use this opportunity to make a clean break to get rid of legacy. The change seems to be clear enough, and I am testing the heck out of this to be sure. This is a reminder of the goal to cut another pre-release December 17th either named beta2 or rc1 depending on the above conditions. It is not a big deal if we need to delay the cut to the proposed deadline of December 23rd. I think a beta2 would be more appropriate. I think rc1 would be after we have all the known P1 bugs closed off. If someone can figure out Bug #6228 then all P1's will be closed by Dec 17th. Even without that bug fixed however, I agree with Mark Marintec that this next release should be called rc1. This is PRETTY CLOSE to what people will be using, and some wont try it if it is called beta. Numbers are cheap. We use this as a 'wake up and test it, this is your last chance!' get the flurry of bugs and polish it up for January or February release. Warren Togami wtog...@redhat.com
Re: Reminder:: 3.3.0 pre-release cut: December 17th
http://tinyurl.com/yd8n96m All bugs targeted for 3.3.0. https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6228 Last bug currently P1 priority and considered a blocker. Warren Togami wtog...@redhat.com
