develooper Front page | perl.perl5.porters | Postings from June 2009

Re: Perl 5.10.1

Thread Previous | Thread Next
From:
Aristotle Pagaltzis
Date:
June 24, 2009 06:54
Subject:
Re: Perl 5.10.1
Message ID:
20090624135430.GA628@klangraum.plasmasturm.org
* David Golden <xdaveg@gmail.com> [2009-06-24 15:30]:
> I believe it will be easier to be confident in stability if the
> development model changes along the lines that Aristotle
> describes in his response to this thread (and that others have
> before).
>
> Dev model (a): blead trunk usually unstable, pulled into a
> stable state for a release infrequently; maint trunk possibly
> unstable, pulled into a stable state for a release from time to
> time
>
> Dev model (b): both trunks stable, work happens on branches,
> onus is on branches to demonstrate stability before being
> merged to trunks

Right. I am not *certain* that the model I described has been
described before, but I think my suggestion included a new
element.

What I was saying is that I see the arguments in favour of model
(a) (or against model (b), depending on how you see it), so I was
suggesting to do both: to use model (b) during normal operations,
but to switch to model (a) temporarily as the release cutting
strategy – the key being by making a selection of branches before
the switch, the model (a) phase is strictly constrained in scope.

[Insert metaphor about taking out small loans of technical debt
to increase buying power then paying them off quickly.]

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/>

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About