Vivek Khera wrote:
We still have to see that this promise will be kept ("we will make every effort..."). Don't forget that we also rely on the apr project, whose API is not frozen yet. But otherwise it can be finished sooner if we get more people trying to shake out bugs and send patches for features that are still missing.The announcement of Apache 2.0.44 includes this:The 2.0.44 release marks a change in the Apache release process and a new level of stability in the 2.0 series. Beginning with this release, we will make every effort to retain forward compatibility in the configuration and module API, so that upgrading along the 2.0 series should be much easier. This compatibility extends backwards to 2.0.42, so users of that version or later should be able to upgrade without changing configurations or updating DSO modules. (Users of earlier releases will need to recompile all modules in order to upgrade to 2.0.44.) Does this mean that mod_perl 2.0 can finally be finished? I recall this being dougm's main objection to finishing it all up...
Also helping us to have a more covering test suite would be very helpful. Currently, I believe, we have most of the functionality tested at the very basic level. Covering the odd cases and the whole API is what we need. So read on how to write tests and send in new tests or extend the existing ones.
Currently I'm trying to finish the filtering API, which keeps on getting delayed to solve the bug reports. Then I'll go back to work on the other missing things. Philippe has promised to finish the <Perl> sections, so I think the configuration functionality will be completed soon. If you have a burning need for some missing functionality, speak up.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
