Re: Proposed: 3.3.2-beta1 on May 4th Re: New release Re: [Bug 6577] IPv6 encapsulated IPv4 sender not detected correctly

["Daryl C. W. O'Shea" <sp...@dostech.ca>]

On 30/04/2011 6:05 AM, Warren Togami Jr. wrote:
> BTW, I haven't seen any voting on 3.3 bugs for quite a while now.
> Meanwhile the written policies allows releasing betas at anytime. So we
> might be better off just cutting a beta right now instead of waiting.
> I'll try to do it this weekend if nobody objects.

Back when Theo and I were hammering out a release a month for about a 
year, we were giving one week notice that we were going to cut a tarball 
to vote on.

There's no need to call it beta if you don't want to.  Just cut the 
tarball, post it to your home directory on people.a.o and let the dev@ 
list know where it is.  We then let the vote run for the minimum time 
required -- at least (I prefer a 5 day minimum myself).

Let me know if you have any issues with the associated rule tarball.  I 
can help out with that if you like.  Copy me directly on any emails to 
the dev@ list about any required help.

Daryl

Re: Proposed: 3.3.2-beta1 on May 4th Re: New release Re: [Bug 6577] IPv6 encapsulated IPv4 sender not detected correctly

[Mark Martinec <Ma...@ijs.si>]

> +1 from me. And I'm paying attention again, so I expect to be voting when
> that's needed.

I'm here too, just returned from a two weeks vacation.

  Mark

Re: Proposed: 3.3.2-beta1 on May 4th Re: New release Re: [Bug 6577] IPv6 encapsulated IPv4 sender not detected correctly

["Warren Togami Jr." <wt...@gmail.com>]

On 5/4/2011 1:46 AM, Mark Martinec wrote:
>> Proposed: 3.3.2-beta1 on May 4th
>
> Please give us a day or two more to sort out some pending bugs,
> I came late for the show :)
>
>    Mark

OK fine, too many appointments today anyway. =)

Warren

Re: Proposed: 3.3.2-beta1 on May 4th Re: New release Re: [Bug 6577] IPv6 encapsulated IPv4 sender not detected correctly

[Mark Martinec <Ma...@ijs.si>]

> Proposed: 3.3.2-beta1 on May 4th

Please give us a day or two more to sort out some pending bugs,
I came late for the show :)

  Mark

Re: Proposed: 3.3.2-beta1 on May 4th Re: New release Re: [Bug 6577] IPv6 encapsulated IPv4 sender not detected correctly

[Steffen Schwigon <ss...@renormalist.net>]

"Kevin A. McGrail" <KM...@PCCC.com> writes:
> On 4/30/2011 10:40 PM, Warren Togami Jr. wrote:
>> On 4/30/2011 4:07 PM, Todd Rinaldo wrote:
>>>
>>> I know it's not the current procedure, but the CPAN way would be to
>>> release a dev version with _01 at the end of the version. This makes
>>> it readily available to everyone and allows the CPAN testers
>>> infrastructure to report on the test suite across multiple platforms
>>> and versions of perl. It does not get installed by any
>>> cpan(plus/minus) clients because of the underscore.
>>>
>>> I definitely don't want to slow down a release but this might be a
>>> good approach eventually.
>>>
>>
>> While I personally don't use CPAN, I do recognize this as a welcome
>> additional means to ease exposure to testing of spamassassin
>> prereleases.
>>
> +1 for sure.

+1, just to express the opinion from a lurker. :-)

Thanks.

Kind regards,
Steffen 
-- 
Steffen Schwigon <ss...@renormalist.net>

Re: Proposed: 3.3.2-beta1 on May 4th Re: New release Re: [Bug 6577] IPv6 encapsulated IPv4 sender not detected correctly

["Kevin A. McGrail" <KM...@PCCC.com>]

On 4/30/2011 10:40 PM, Warren Togami Jr. wrote:
> On 4/30/2011 4:07 PM, Todd Rinaldo wrote:
>>
>> I know it's not the current procedure, but the CPAN way would be to
>> release a dev version with _01 at the end of the version. This makes
>> it readily available to everyone and allows the CPAN testers
>> infrastructure to report on the test suite across multiple platforms
>> and versions of perl. It does not get installed by any
>> cpan(plus/minus) clients because of the underscore.
>>
>> I definitely don't want to slow down a release but this might be a
>> good approach eventually.
>>
>
> While I personally don't use CPAN, I do recognize this as a welcome 
> additional means to ease exposure to testing of spamassassin prereleases.
>
+1 for sure.

Re: Proposed: 3.3.2-beta1 on May 4th Re: New release Re: [Bug 6577] IPv6 encapsulated IPv4 sender not detected correctly

["Warren Togami Jr." <wt...@gmail.com>]

On 4/30/2011 4:07 PM, Todd Rinaldo wrote:
>
> I know it's not the current procedure, but the CPAN way would be to
> release a dev version with _01 at the end of the version. This makes
> it readily available to everyone and allows the CPAN testers
> infrastructure to report on the test suite across multiple platforms
> and versions of perl. It does not get installed by any
> cpan(plus/minus) clients because of the underscore.
>
> I definitely don't want to slow down a release but this might be a
> good approach eventually.
>

While I personally don't use CPAN, I do recognize this as a welcome 
additional means to ease exposure to testing of spamassassin prereleases.

Warren

Re: Proposed: 3.3.2-beta1 on May 4th Re: New release Re: [Bug 6577] IPv6 encapsulated IPv4 sender not detected correctly

[Todd Rinaldo <to...@cpanel.net>]

On Apr 30, 2011, at 5:50 PM, Daryl C. W. O'Shea wrote:

> On 30/04/2011 6:05 AM, Warren Togami Jr. wrote:
>> BTW, I haven't seen any voting on 3.3 bugs for quite a while now.
>> Meanwhile the written policies allows releasing betas at anytime. So we
>> might be better off just cutting a beta right now instead of waiting.
>> I'll try to do it this weekend if nobody objects.
> 
> Back when Theo and I were hammering out a release a month for about a year, we were giving one week notice that we were going to cut a tarball to vote on.
> 
> There's no need to call it beta if you don't want to.  Just cut the tarball, post it to your home directory on people.a.o and let the dev@ list know where it is.  We then let the vote run for the minimum time required -- at least (I prefer a 5 day minimum myself).
> 
> Let me know if you have any issues with the associated rule tarball.  I can help out with that if you like.  Copy me directly on any emails to the dev@ list about any required help.
> 
> Daryl

I know it's not the current procedure, but the CPAN way would be to release a dev version with _01 at the end of the version. This makes it readily available to everyone and allows the CPAN testers infrastructure to report on the test suite across multiple platforms and versions of perl. It does not get installed by any cpan(plus/minus) clients because of the underscore. 

I definitely don't want to slow down a release but this might be a good approach eventually. 

Re: How were monthly releases done? Re: Proposed: 3.3.2-beta1 on May 4th

[Daniel McDonald <da...@austinenergy.com>]

On 5/6/11 11:31 AM, "darxus@chaosreigns.com" <da...@chaosreigns.com> wrote:

> On 04/30, Daryl C. W. O'Shea wrote:
>> Back when Theo and I were hammering out a release a month for about
>> a year, we were giving one week notice that we were going to cut a
>> tarball to vote on.
> 
> How was that done?  No branching, just do a release a month, call it a
> beta, and if no problems were found in the next month call it a stable
> release?

As I recall, there were no "betas".  They just cut the tarball, it would be
hosted on Daryl or Justin's server, and the committers would download and
test the tarball.  Normally there would be votes cast pretty quickly (2 or 3
days tops), and it would be published in the official channels once there
were enough +1 votes (and no -1).



-- 
Daniel J McDonald, CCIE # 2495, CISSP # 78281

How were monthly releases done? Re: Proposed: 3.3.2-beta1 on May 4th

[da...@chaosreigns.com]

On 04/30, Daryl C. W. O'Shea wrote:
> Back when Theo and I were hammering out a release a month for about
> a year, we were giving one week notice that we were going to cut a
> tarball to vote on.

How was that done?  No branching, just do a release a month, call it a
beta, and if no problems were found in the next month call it a stable
release?

-- 
"Life is either a daring adventure or it is nothing at all."
- Helen Keller
http://www.ChaosReigns.com