Andy Dougherty wrote: > Maintenance track: I would recommend bumping the patchlevel when the > pumpkin holder believes it is time to release snapshots for testing with > the world outside perl (e.g. other programs or modules that may have > patchlevel-specific code). Don't bump it too soon, because then it gets > out into the world and you may get bogus bug reports for some time to > come. But don't wait too long either, because there is likely some code > out there that has patchlevel-specific workarounds in it. Also, the perl > core itself has a few patchlevel-specific parts that need to be tested. > (Bonus trivia question: Who remembers what the first 5.000 release called > itself?) Ideally when rsync's repository of the maint track is updated, it could automatically update the patchlevel, using some script that talks peforce and can retrieve that info. In which case the pumpkin doesn't need to bother to remember to update this file. __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:stas@stason.org http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.comThread Previous | Thread Next