Okay, but I want my (quasi-production) environment to remain stable and I don't want to expose it to constant patches. This will be even more important once 2.0 becomes official. Maybe this doesn't really apply to MP, but I also wouldn't want to break any dependencies that other modules have (i.e. MP may require an update to httpd, which breaks something else). (Of course, I wouldn't have this concern if I had another system for pure development.)
A properly designed production system, has a thorough test suite and a staging machine(s), so any new upgrade goes through it. You can't just go, upgrade the software and hope that it'll work. Any new version may introduce new bugs, so you are never protected if you don't thoroughly test *your* system.
Hence there is no need
for an overhead of managing a bug tracking system. Those that aren't
fixed are listed in the STATUS file, and/or in the todo/ directory.
Bugzilla is a scary monster -- and its probably one of the lighter ones. Even posting a master spreadsheet or html table that includes historical bug details (not just summary) would be very useful.
The developer team is too small and we have no time to manage a bug tracking system, if we get more people give us hand we may consider opening up a bug tracking system. Meanwhile if you want to search for bug reports you can search the mailing list archive.
And we already have the RT system via CPAN, but nobody looks at it:
http://rt.cpan.org/NoAuth/Bugs.html?Dist=mod_perl
I had no idea someone has reported the bugs. RT needs to send those bugs to the modperl list. Last time I tried to make that happen, it didn't work due to some email blocking issues at apache.org :(
-- __________________________________________________________________ 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
