diff options
author | Karen Etheridge <ether@cpan.org> | 2018-11-20 12:24:04 -0800 |
---|---|---|
committer | Karen Etheridge <ether@cpan.org> | 2018-11-20 12:53:15 -0800 |
commit | cada13e68ff7cc5b4d8fe23e848d33c8e93dffe0 (patch) | |
tree | 063586919837e0b20069ea3fa02101b0ccfd064e | |
parent | afdabb7bd38d27cb89362c03e89d714ba51db8be (diff) | |
download | perl-cada13e68ff7cc5b4d8fe23e848d33c8e93dffe0.tar.gz |
RMG tweaks
-rw-r--r-- | Porting/release_managers_guide.pod | 16 |
1 files changed, 13 insertions, 3 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 2ab11d013f..6c8a769377 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -206,7 +206,7 @@ You can also run an actual diff of the contents of the modules, comparing core to CPAN, to ensure that there were no erroneous/extraneous changes that need to be dealt with. You do this by not passing the C<-x> option: - $ ./perl -Ilib Porting/core-cpan-diff -a -o /tmp/corediffs + $ ./perl -Ilib Porting/core-cpan-diff -a -o ~/corediffs Passing C<-u cpan> will probably be helpful, since it limits the search to distributions with 'cpan' upstream source. (It's OK for blead upstream to @@ -238,6 +238,16 @@ necessary, fix things up. For example, you might think that both blead and maint are synchronised with a particular CPAN module, but one might have some extra changes. +In any case, any cpan-first distribution that is listed as having files +"Customized for blead" in the output of cpan-core-diff should have requests +submitted to the maintainer(s) to make a cpan release to catch up with blead. + +Additionally, all files listed as "modified" but not "customized for blead" +should have entries added under the C<CUSTOMIZED> key in +F<Porting/Maintainers.pl>, as well as checksums updated via: + + cd t; ./perl -I../lib porting/customized.t --regen + =head4 Sync CPAN modules with the corresponding cpanE<sol> distro In most cases, once a new version of a distribution shipped with core has been @@ -393,7 +403,7 @@ L<"update Module::CoreList">). =head3 Bump the version number Do not do this yet for a BLEAD-POINT release! You will do this at the end of -the release process. +the release process (after building the final tarball, tagging etc). Increase the version number (e.g. from 5.12.0 to 5.12.1). @@ -732,7 +742,7 @@ Also, you may want to generate and view an HTML version of it to check formatting, e.g. $ ./perl -Ilib ext/Pod-Html/bin/pod2html pod/perldelta.pod > \ - /tmp/perldelta.html + ~/perldelta.html If you make changes, be sure to commit them. |