Hi, As I was the one to suggest it in the first place, I will tell you why I asked for it. Putting out releases and announcing them is really a tough job to do all the time and Peter is doing a wonderful job there. Thanks Peter (waxhead++) :)
More developer releases shows the rate of change that Padre is going through. Early access developer releases provide early access to features at certain *stable* instances in the lifetime of Padre trunk. One needs to blog and tweet about the shiny new feature he/she has just developed in Padre core. People might get interested and excited enough to try Padre's new shiny feature. They install it from CPAN and to their surprise they have an older by 20 to 50 changes release that does not contain that feature. Now, they might think Padre is not working as announced and may reply or not back. They might delay their adoption to Padre and might eventually forget about installing it. As an example, I blogged about Padre Solarized light theme support. A week later, style 2.0 broke it. I embrace change and style 2.0 is certainly awesome but I would also like a developer release to say to people, "hey... we had that feature at that time" :) Basically gauge what people think about Padre's feature set and to see if we are going in the right direction or not. And I continually release Wx::Scintilla developer versions to get *feedback* and stay interested in the project :) If i did not release feature X in developer release Y, it will stay in subversion repository and might eventually start to decay. Thanks for reading this far :) Ahmad M. Zawawi (azawawi) 2011/9/26 Chris Marshall <devel.chm...@gmail.com> > For PDL CPAN Developers releases, we have directions for using > cpan to install and warnings at the top of the release notes. Then > they appear on any CPAN searches and can be sent out on mailing > lists for announcements. > > --Chris > > > On Mon, Sep 26, 2011 at 11:06 AM, Gabor Szabo <szab...@gmail.com> wrote: > > On Mon, Sep 26, 2011 at 11:32 AM, Peter Lavender > > <pla...@internode.on.net> wrote: > >> 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? > >> > > > > The CPAN testes effect is there but unfortunately it is relatively > > small in case of Padre. > > The other is to have more people try Padre before it has a stable > release. > > > > 1) We have a few people following SVN. > > 3) We have more people installing from CPAN and expecting it to be > stable. > > 4) We have (or so we hope) a lot more people installing binary versions. > > (e.g. from linux distros or the Mac package of Tome or the Padre on > > Strawberry package) > > > > > > Having developer releases would IMHO be > > 2) People brave enough to install possibly broken version. > > Who know how to install and older version if this is really broken. > > but who don't want to follow the SVN. > > > > So I am ok having developer releases. If we have someone to do them and > > if we tell people how to install them and how to install an older > > version in case > > of trouble. We might need a way to announce them. At least on this > > mailing list but maybe also elsewhere. > > > > I think seeing more frequent releases might help get some more noise > > and more developers. > > > > regards > > Gabor > > _______________________________________________ > > Padre-dev mailing list > > Padre-dev@perlide.org > > http://mail.perlide.org/mailman/listinfo/padre-dev > > > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev >
_______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
