Hi Everyone, I caught mention of doing developer releases for Padre:
http://irclog.perlgeek.de/padre/2011-09-21#i_4458775 I know Ahmad uses this a lot, we saw it plenty with the Wx::Scintilla development process. What do people think of doing this with Padre itself? I'm happy to do this, but I do have a concern or two about the perception of Padre itself, the main one being, do we risk damaging its profile if a number of releases hit CPAN that aren't so stable, or cause people a lot of pain. Many of the big changes we wait on before a release generally come down to which API is being worked on and how long it takes to get it back to stable enough for a release. I can see why currently doing a developer release or two does make it simple enough for people to install from CPAN, but then for most developers it's not that hard to svn checkout and make the project, but of course anything that lowers the barriers for a wider audience is always a good thing to get early feedback. So basically I guess I can see both arguments here, so for my part, I don't care, I'll happily roll out a a few developer releases before a "major" stable release to see things like the diff work that Ahmad has added to Padre. The big thing though is picking a natural 'stable enough' point to branch and release while other parts are being worked on. Thoughts? Pete.
_______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
