Yes, it is a pre-release version. The point is that it is stable enough to use in an enterprise (fortune 500 company) application.
Is stable a reference to crashing or changes in the API ? I'm using a later version, 1.99_16, because the version that shipped with FC2, 1.99_12, was missing APIs (something to do with buckets) that are referred to on the modperl website and that i was trying to use.
wrt API stability, recent 1.99_XX releases are very close to the way the official 2.0 release will look. those things that will change (either pre- or post-2.0) are APIs that the vast majority of people won't ever need.
wrt "crashing"-type stability, mp2 is as stable as we can make it without people actually using it and finding things that only a real-world deployment can find. but we have had very few (any?) reports of random segfaults or crashes from those who have deployed it, so I guess we're doing something right :)
The current cvs (1.99_17-tobe) has a few API changes since 1.99_16, and with that it's about 99.5% API complete: http://cvs.apache.org/viewcvs.cgi/modperl-2.0/todo/api_status?view=markup
So 1.99_17 will probably be what 2.0.0 will be, API-wise.
We will ship a 2.0 release candidate really soon now. There are still a few complex problems that need to be resolved, which hold back the release. If you wish you can take a look at the todo list for the release and help if you can:
http://cvs.apache.org/viewcvs.cgi/modperl-2.0/todo/release?view=markup
We will have 1.99_17 released soonish.
-- __________________________________________________________________ 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
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
