On Sat, 2003-11-22 at 16:46, Stas Bekman wrote:
This week at ApacheCon in Las Vegas, Geoff, Philippe and I sat down and created a new TODO list:
http://cvs.apache.org/viewcvs.cgi/*checkout*/modperl-2.0/todo/release?rev=HEAD&content-type=text/plain
which contains issues we think must be resolved before we release mod_perl 2.0.
Sign me up for porting Apache::SizeLimit under prefork.
It's all yours now ;) I'll handle the GTopLimit, unless someone wants to handle it. May be we should merge the two and have an option to use GTopLimit if that's available and other approaches if it is not?
* Apache::Reload - needs to handle properly redefined subs warnings
What would you consider properly handling these warnings?
We need to undefine all symbols and we don't at the moment. We started discussing this issue and there were a few suggested patches on the dev list, but the issue wasn't finished. See:
http://marc.theaimsgroup.com/?t=105545915700001&r=1&w=2
http://marc.theaimsgroup.com/?t=105599929900002&r=1&w=2
Most of these are tasks that require C skills.
True. But it's not like nobody knows C, most of us learn it as we go, there is always a time to start.
Is there anything else for people who want to contribute Perl code or help with docs?
Docs, absolutely, we need to write the API docs, even though it requires you to look at the C code sometimes, a big chunk of the API hasn't changed from mp1, so it's really just going and copying the docs for the methods from mp1 and verifying that they do the same under mp2. The test suite should provide a lot of help in this task, since most of the methods are exercised and tested there.
While we have quite a few tutorial sections on how things work, we still need a lot more. E.g. there are quite a few things that need to be ported from the mod_perl 1.0 guide, as most of the things haven't changed. And as it was noted on this list several times, mp2 users end up referring to mp1 guide quite often.
I'm sure there are many other code issues that we don't know about. We get a few bug reports every week, and we solve them as they come in. People should start porting their applications now and not wait for 2.0 release. The earlier you start porting to 2.0 the sooner you will discover problems, if any, the sooner they will be fixed. The more people will start using mp2 the better mp 2.0 release is going to be. It's a chicken and egg problem, don't be afraid to be the chicken before the egg.
__________________________________________________________________ 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
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
