=head3 Check more build configurations
-Check some more build configurations.
+Try running the full test suite against multiple Perl configurations. Here are
+some sets of Configure flags you can try:
- $ sh Configure -Dprefix=/tmp/perl-5.x.y -Uinstallusrbinperl \
- -Duseshrplib -Dusesitecustomize
- $ make
- $ make test
+=over 4
+
+=item *
-XXX think of other configurations that need testing.
+C<-Duseshrplib -Dusesitecustomize>
+
+=item *
+
+C<-Duserelocatableinc>
+
+=item *
+C<-Dusethreads>
+
+=back
+
+If you have multiple compilers on your machine, you might also consider
+compiling with C<-Dcc=$other_compiler>.
=head3 update perlport
C<$Module::CoreList::VERSION>. Make sure the two versions match before
proceeding.
+Edit the version number in the new
+C<< 'Module::CoreList::TieHashDelta' => 'X.YZ' >> entry, as that is likely to
+reflect the previous version number.
+
=head4 Bump version in Module::CoreList F<Changes>
Also edit Module::CoreList's new version number in its F<Changes>
sure that his or her name is listed in the section entitled
C<THE KEEPERS OF THE PUMPKIN>.
-I<If you're making a BLEAD-POINT release>, also update the "SELECTED
+I<If you're making a BLEAD-FINAL release>, also update the "SELECTED
RELEASE SIZES" section with the output of
F<Porting/perlhist_calculate.pl>.
$ git commit -m 'bump version to RCnnn' patchlevel.h
+=head3 run makemeta to update META files
+
+ $ perl Porting/makemeta
+
+Be sure to commit any changes (if applicable):
+
+ $ git commit -m 'Update META files' META.*
=head3 build, test and check a fresh perl
Push all your recent commits:
- $ git push origin ....
-
+ $ git push origin release-5.xx.yy
=head3 tag the release
I<You MUST SKIP this step for a RC release>
-In your C<perlorg> repository, link to the new release. For a new
+In your C<perlweb> repository, link to the new release. For a new
latest-maint release, edit F<docs/shared/tpl/stats.html>. Otherwise,
edit F<docs/dev/perl5/index.html>.