On Fri, Jul 13, 2012 at 9:39 AM, Logan Bell <[email protected]> wrote: > I agree it's a small fix, but we must ask the obvious question what > justifies a bug release? Looking through our wiki I don't see any sort of > guidelines for this.
You need a Release Manager willing to do the work and a majority vote with a quorum of 3 PMC members voting +1. Power resides in the do-ocracy. It's up to the judgment of those individuals. Personally, I think a bugfix release would be justified if we try to make some progress on this class of problem in Charmonizer: http://cpantesters.org/cpan/report/ffcaade6-6cc9-1014-8d81-4edd8ede4cb4 We have had similar problems with earlier releases: http://www.cpantesters.org/cpan/report/69b25746-6cfa-1014-850b-e0170163837e http://www.cpantesters.org/cpan/report/db586700-63e1-11e1-b759-ec922b0aa2c1 http://www.cpantesters.org/cpan/report/14256dac-6893-11e1-ba5b-ffa051838b10 I think they are all due to failed file system operations, maybe unchecked remove() calls that are failing on busy Windows systems. It would be nice to go over our code and make sure we are printing useful error messages to stderr whenever system calls fail. Then at least we would have a better shot at figuring out what's going wrong from CPAN tester failure output, since I can't seem to duplicate these failures locally. > My instincts tell me that since we're a small project that quick bug > releases to satisfy users of the project is the best way to grow the > project's user/dev base. Kudos for keeping community growth in mind. Our 0.3.2 release was needed because LUCY-238 had no workaround. Marvin Humphrey
