Front page | perl.perl5.porters |
Postings from March 2013
The current suggested handling for maint branches in the release managers
guide for the updated perlhist.pod and the perlNNNdelta.pod files is:
1) update this maint branch's perlhist with the new version info for this
branch
2) make the new release
3) copy perlhist and the new perlNNNdelta to blead and *every other* maint
branch.
I suggest changing it to:
1) as an early step in the 'on the day' for a maint RC or maint FINAL
release, copy in the latest perlhist from blead; this will automatically
get us info on all new releases on all branches since the last maint
release on this branch; similarly, copy any perlNNNdelta files from blead
which aren't already in maint;
2) update this maint branch's perlhist with the new version info for this
branch
3) make the new release
4) copy perlhist and the new perlNNNdelta to blead *only*.
This means that a particular maint branch only gets its perlhist updated
when we're ready to make a release for that branch, rather than it getting
lots of small updates every time someone makes a release on another
branch.
And it saves someone making a release from having to checkout and update
every other branch.
--
Now is the discount of our winter tent
-- sign seen outside camping shop
Thread Next