So Perl 5.10.1 is out, and my Apache is a couple of releases old, and
the
latest mod_apreq2 failed testing from source so I can try it from the
FreeBSD ports. Which is close to critical mass to rebuild my site
software.
Does anyone reading this know the state of the next mod_perl2?
Like when it might be released?
Thanks,
cmac
On Wed, Aug 26, 2009 at 10:44 AM,
> So Perl 5.10.1 is out, and my Apache is a couple of releases old, and the
> latest mod_apreq2 failed testing from source so I can try it from the
> FreeBSD ports. =A0Which is close to critical mass to rebuild my site soft=
ware.
>
> Does anyone reading this know the state of the next mod_perl2?
There's a few issues that need to be resolved with the external
modules such as Apache::Reload. A lot of discussion occurred on the
dev list regarding the best practice for bundling these modules with
mod_perl2 core vs. making them separately available. I need to look
through the archives to verify, but I think a consensus was reached to
ship Apache2?::* modules bundled with core, but also allow for
separate module releases as needed.
Other than those bundling issues, svn tip is in great shape. I've got
it running in production and it just works.
> Like when it might be released?
My guess would be when it is ready. The best way to make that happen
is to test with svn trunk, and report back success or failures to the
list. The issues that are in the front of the minds of the developers
are usually stability, scalability, and maintainability. Releasing a
numbered version of mod_perl takes a lot of work. There's prefork,
win32, mpm-worker variants that must be tested on variants of
perl/apache/libapreq/os.
How can you help make it happen? By posting this email you have
already taken the first step. Go ahead and download 5.10.1 and test
it out with your setup and mod_perl svn trunk, and report back with
success or failure. Success cases are usually boring, but failures
are interesting and present problems that need to be solved.