Front page | perl.perl5.porters |
Postings from April 2001
On Thu, 26 Apr 2001 12:41:48 BST, Dave Mitchell wrote:
>shouldnt mainenance branch releases be far more frequent, say every
>couple of months or so?
I agree, but I can't promise to have the tuits available to bring it
off, unfortunately.
I have tried to pawn off the 5.6.x pumpkin on several occasions
for this reason, but can't find anyone among the most likely
suspects willing to take on the responsibility. :-(
In case someone will become interested in future, here are the job
requirements for keeping the maintenance pumpkin:
* familiarity with the perl internals (enough to judge patches
and reject them with a clear conscience :)
* at least a few years of p5p experience (enough not to repeat
past mistakes often)
* familiarity with source code control issues such as branching
and merging, perferably already knows perforce or a fast learner
of the same
* conservative attitude towards feature creep
* 16% sleep cycle, no job, family or social life (just kidding,
only need this to keep development pumpkin ;)
>I thought the rationale for the maintenance branch was that it was an
>accumulation of bug fixes, so that in effect each micro release
>becomes more and more stable?
I don't want maintenance releases to be more frequent than development
releases. Ideally, bug fixes in a maintenance release should have
survived at least a few development releases before they get into
a maintenance release.
So the ideal release pattern (to my mind) would be: a development
release every fortnight, and a maintenance release every two months.
>Or perhaps, like the swan madly paddling below the surface, there's more
>to making a minor release than meets the eye ?
There is this too.
Sarathy
gsar@ActiveState.com
Thread Previous