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 multip
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
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
The key purpose for me with the 3.3.2 release is the perl 5.12 warnings so that
makes sense.
As for the keys, we have too few people clearly but I understand your concern!
Regards,
KAM
"Warren Togami Jr." wrote:
On 4/29/2011 3:28 AM, Kevin A. McGrail wrote: > >> I know the password for the
si
On 4/29/2011 3:28 AM, Kevin A. McGrail wrote:
I know the password for the signing keys. I've just been crazy busy. I
will have some time May 4th.
By the written policies, it appears that any committer is authorized
to unilaterally release an unofficial beta.
I therefore propose that folks sho
