What about branching for 1.0 now copying fixes from trunk to branch but not introducing features which are not 100% stable?
Releases 0.90 to 0.98 could go as usual parallel to 1.0 branch. On 10.07.2011 15:29, Gabor Szabo wrote: > I think we should certainly have more stability in the project as we keep > breaking features all the time. It would be nice to read proposals how > to ensure more stability while we want to keep development? > > regards > Gabor > > On Sat, Jul 9, 2011 at 11:32 PM, Claudio Ramirez > <padre.clau...@apt-get.be> wrote: >> Indeed, now that Padre is kind of "feature-ful" it's good to >> concentrate in stability and "paper cuts". And push this version >> forward as the one to be picked up by distros and the like. >> >> C. >> >> On Sat, Jul 9, 2011 at 8:14 AM, Sebastian Willing >> <sebastian.will...@web.de> wrote: >>> Hi, >>> >>> we've been working hard on growing up Padre and decided somewhere in the >>> 0.50s not to jump to 1.0 but wait until we had enough releases. >>> >>> I think we should follow this and if 1.0 is the next release number, it >>> is, so special treatment. >>> >>> Maybe the branch-and-fix period should be (much) longer for 1.0 :-) >>> >>> Sebastian >>> >>> On 09.07.2011 04:16, Peter Lavender wrote: >>>> Hi Everyone, >>>> >>>> Given that the next release will be 0.88, we have effectively 6 more >>>> 'stable' release before we hit the magic 0.100 or 1.00. >>>> >>>> What are peoples thoughts on this. >>>> >>>> I know versioning can be a hot topic, and personally I'm not fussed one >>>> way or another, so there's my "non vote" on the issue. :) >>>> >>>> Peter. > _______________________________________________ > 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
