[Padre-dev] Once a month "major" release ?
lists.perl.padre-dev at csjewell.fastmail.us
Wed Aug 5 11:34:14 PDT 2009
A suggestion: What I do with my modules most of the time is "three digit
versioning", (1.251, forex).
A version where the third digit after the decimal point is a zero is a
"major version", and in Perl::Dist "long test" cases, has either been
used to do an actual build, or has had the long tests that do full
builds ran against them.
If I want dev versions, then I put an additional 3 digits in (1.252_001)
So, if we do weekly releases or so:
0.460 on August 28th
0.461 on September 4th
0.462 on September 11th
0.463 on September 18th
0.470 on September 25th
0.471 on October 2nd
On Wed, 05 Aug 2009 14:35 -0300, "breno" <breno at rio.pm.org> wrote:
> How will users know the difference between minor and major releases?
> We'll number them differently? If it's just a convention, like
> "third/last release of the month", "the release after rakudo", then I
> think users might get confused about it, no? Maybe switching to
> three-dotted versioning?
> On Wed, Aug 5, 2009 at 6:24 AM, Gabor Szabo<szabgab at gmail.com> wrote:
> > Hi,
> > on YAPC::EU I met I think 4 or 5 people who are already Padre developers.
> > It was great seeing them.
> > I talked a bit with each one of them. There were several ideas
> > bounced, one of them was to
> > make the translation effort less continuous. So while every translator
> > can decide for himself
> > if he wants to keep the translation always up to date or not, we will
> > not bug them so much.
> > I thought this can fit in a slightly new release process for the next
> > 6 months or so.
> > We keep the semi-regular weekly releases but once a month have a larger release.
> > What can be special about this "major" release?
> > 1) Longer time to spend on the release branch,
> > we could even have one of the smaller release and base the bigger
> > one right on the smaller release.
> > So for example we have 43, 44, 45 smaller releses
> > Then based on 45 we create a release branch for 46.
> > We give the translators a few days to catch up on this branch.
> > That time will also allow
> > people to give feedback on 45 so we can fix really critical issues
> > on the 46 branch.
> > 2) This release could be scheduled just a few days after Rakudo is released
> > 3) Once it is done and if Curtis agrees to do it we could have several
> > packages for windows:
> > 1) Almost Six that can be c:\strawberry for a while (msi. zip)
> > 2) Portable Strawberry + Padre + growing number of plugins (msi,
> > zip) (no Perl 6)
> > That would mean we have these bigger, more stable and better
> > translated releases by ~ 25th of every month.
> > Comment ?
> > Gabor
> > _______________________________________________
> > Padre-dev mailing list
> > Padre-dev at perlide.org
> > http://mail.perlide.org/mailman/listinfo/padre-dev
> Padre-dev mailing list
> Padre-dev at perlide.org
swordsman at csjewell.fastmail.us
%DCL-E-MEM-BAD, bad memory
-VMS-F-PDGERS, pudding between the ears
[I use PC-Alpine, which deliberately does not display colors and pictures in HTML mail]
More information about the Padre-dev