Front page | perl.perl5.porters |
Postings from August 2009
Jesse,
regarding the recent changes to release_managers_guide.pod, I've spotted
some issues:
-------
8c35d285401fe5adc3a2123303047b3c9caf49e7
Linearized the release-manager's guide to make it less of a
choose-your-own-adve nture novel
I've not looked too closely yet, but this re-ordering seems to have
screwed up the logical ordering of some of the steps. For example,
there are now RC- and release-specific steps (such as setting
patchlevel.h, looking for typos in perldelta) that are described as being
done *after* the release tarball has been built!!!!
You also added the following two lines:
XXX - we should be able to use git to automate much of the role
previously filled by the mergelog.
This is wrong. I added mergelog specifically after we moved to git, to
cope with git's inability to handle the sort of cherry-picking bookkeeping
that I needed for maint.
-------
dc2f75c0f2e64ac8eee5e3138845de02223668f8
Porting/corelist.pl can now update Module::CoreList directly
You made the following change:
- $ cd ~/perl/root; make perl
- $ ./perl -Ilib Porting/corelist.pl ~/cpan-mirror/ > /tmp/corelist
+ $ perl -Ilib Porting/corelist.pl ~/my-cpan-mirror
but you can't run a general perl with -Ilib, which is why I explicitly
showed it as building and running perl in the target perl root. For
example:
$ perl -Ilib Porting/corelist.pl ~/cpan-mirror
Perl lib version (5.10.1) doesn't match executable version (v5.10.0) at lib/Config.pm line 50.
You also removed the following step, which stills needs to be done
manually:
-Then, add the current perl version to the C<CAVEATS> paragraph.
--
Britain, Britain, Britain! Discovered by Sir Henry Britain in
sixteen-oh-ten. Sold to Germany a year later for a pfennig and the promise
of a kiss. Destroyed in eighteen thirty-forty two, and rebuilt a week
later by a man. This we know. Hello. But what of the people of Britain?
Who they? What do? And why? -- "Little Britain"
Thread Next