One more comment - if this helps take some load off infrastructure@ and allows them to give us help with other needs, I see benefits there.
So my official vote is +1 for retiring after the 1.32 final release :) On Sat, Feb 19, 2011 at 1:02 PM, Philip M. Gollucci <pgollu...@p6m7g8.com> wrote: > On 2/19/2011 2:50 PM, Perrin Harkins wrote: >> I guess my question is how would this be any different from what we're >> doing now? Is anyone actively working on mod_perl 1 development, >> except when a security issue is raised? > Its 'official', good practice, and prudent :) > > The security practice is biggest thing. But the way we handle it > standard with other ASF projects and other 3rd Parties (i.e. FreeBSD). > > > > -- > ------------------------------------------------------------------------ > 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C > Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 > VP Apache Infrastructure; Member, Apache Software Foundation > Committer, FreeBSD Foundation > Consultant, P6M7G8 Inc. > Sr. System Admin, Ridecharge Inc. > > Work like you don't need the money, > love like you'll never get hurt, > and dance like nobody's watching. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org > For additional commands, e-mail: dev-h...@perl.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org For additional commands, e-mail: dev-h...@perl.apache.org
