Thank you Steve! I read at http://perldoc.perl.org/perlhist.html that you 
carried quite some major Perl releases on your shoulder since 2010. It must be 
said that such contribution is without a doubt something you made a lot of 
enthusiastic programmers happy with and it is something that cannot easily be 
ignored.

You've pointed out that the latest source is likely very close to what will 
become 2.0.9, from SVN: 
https://svn.apache.org/repos/asf/perl/modperl/trunk/

What is from your point of view necessary to release it?
Is it testing? Writing docs?
Are there some tasks that can be done by others as well?
Is it an option to release earlier by marking certain features as Experimental?

Adam


-----Original Message-----
From: Steve Hay [mailto:steve.m....@googlemail.com] 
Sent: Thursday, January 22, 2015 6:54 PM
To: The Aquatic Research Center
Cc: mod_perl Dev
Subject: Re: Releasing Apache 2.4 supported Mod-Perl

On 22 January 2015 at 16:52, The Aquatic Research Center
<plank...@theaquaticresearchcenter.com> wrote:
> Dear appreciated mod-perl developers,
>
>
>
> I have a mod-perl site that I want to continue using, but my distro doesn't
> distribute the mod-perl package anymore because there is none available that
> works with Apache 2.4.
>
>
>
> I read the archives and saw that nobody raised any objections against
> releasing.
>
>
>
> Does somebody know who is the brave Perl-monk that takes precious care of
> the mod-perl-pumpkin and is willing to release the Apache 2.4 supported
> mod-perl?
>
>
>

Thank you for your interest in mod_perl. I have been trying to
organize a new release for a little while now, and hope that it will
happen soon.

---------------------------------------------------------------------
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

Reply via email to