> the todo dir seems a bit dated.
also remember that there is the STATUS file.
> can you summarize (in a new thread) the > most pressing issues you see, then I can maybe jump on some of those.
besides small things that are better handled as they are reported to be a problem, the two massive open issues are:
* sync apr_ and ap_ for APIs we support. Quite a few functions were renamed and some have changed they arguments. So in the simple case all that needs to be changes is the map file and the corresponding table .pm file. In the complex case (args changed) the XS wrapper might needs to be updated.
the hard part is to handle the temporary backcompat in the C level where the arguments have changed. it's temprorary since at some point (probably when we release the first real modperl-2.0) we will require httpd-2.0.$min where $min will be bigger than 36 and then we can cut off the temp workarounds.
this issue is urgent since not many people haven't started to rely on the 2.0 apis, it'll be much harder to change them.
* manpages. Gerald has a pretty good prototype for importing C docs from .h files, which once created need to be adjusted to match the perl API which will be a bit different.
this issue is urgent as it prevents people from starting using the new APIs, that didn't exist in 1.0, since they need docs. However it depends on the previous one, since we first need to correct the apis.
probably there are other issues, but nothing comes to my mind as very important right now.
__________________________________________________________________ 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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
