This is a live mirror of the Perl 5 development currently hosted at https://github.com/perl/perl5
Fix corelist generation section of the release manager documentation.
[perl5.git] / Porting / release_managers_guide.pod
CommitLineData
7277a900
GS
1=head1 NAME
2
3release_managers_guide - Releasing a new version of perl 5.x
4
636a1918
DM
5XXX as of Jul 2009, this file is still a work-in-progress. I think it
6contains all the actions needed to build a release, but things may have
7got skipped, and some things could do with polishing. Note that things
8change each release, there may be new things not covered here, or
9tools may need updating. DAPM
f6af4394 10
7277a900
GS
11=head1 SYNOPSIS
12
f6af4394
DM
13This document describes the series of tasks required - some automatic, some
14manual - to produce a perl release of some description, be that a snaphot,
8c35d285 15release candidate, or final, numbered release of maint or blead.
f6af4394 16
8c35d285
JV
17The release process has traditionally been executed by the current
18pumpking.
7277a900 19
8c35d285
JV
20This document both helps as a check-list for the release engineer
21and is a base for ideas on how the various tasks could be automated
22or distributed.
7277a900 23
636a1918 24The outline of a typical release cycle is as follows:
f6af4394 25
636a1918 26 (5.10.1 is released, and post-release actions have been done)
f6af4394
DM
27
28 ...time passes...
29
30 an occasional snapshot is released, that still identifies itself as
31 5.10.1
32
33 ...time passes...
34
35 a few weeks before the release, a number of steps are performed,
36 including bumping the version to 5.10.2
636a1918
DM
37
38 ...a few weeks passes...
46743ef7 39
f6af4394
DM
40 perl-5.10.2-RC1 is released
41
42 perl-5.10.2 is released
43
44 post-release actions are performed, including creating new
45 perl5103delta.pod
46
47 ... the cycle continues ...
7277a900
GS
48
49=head1 DETAILS
50
8c35d285
JV
51Some of the tasks described below apply to all four types of
52release of Perl. (snapshot, RC, final release of maint, final
53release of blead). Some of these tasks apply only to a subset
54of these release types. If a step does not apply to a given
55type of release, you will see a notation to that effect at
56the beginning of the step.
57
58=head2 Release types
59
60=over 4
61
62=item Snapshot
63
64A snapshot is intended to encourage in-depth testing from time-to-time,
65for example after a key point in the stabilisation of a branch. It
66requires fewer steps than a full release, and the version number of perl in
67the tarball will usually be the same as that of the previous release.
68
69=item Release Candidate (RC)
70
71XXX Describe me
72
73=item Stable/Maint release
74
75At this point you should have a working release candidate with few or no
76changes since.
77
78It's essentially the same procedure as for making a release candidate, but
79with a whole bunch of extra post-release steps.
80
81=item Blead release
82
83It's essentially the same procedure as for making a release candidate, but
84with a whole bunch of extra post-release steps.
85
86=back
7277a900 87
fd838dcf
JV
88=head2 Prerequisites
89
90Before you can make an official release of perl, there are a few
91hoops you need to jump through:
92
93=over 4
94
8c35d285
JV
95=item PAUSE account
96
97I<SKIP this step for SNAPSHOT>
fd838dcf
JV
98
99Make sure you have a PAUSE account suitable for uploading a perl release.
100If you don't have a PAUSE account, then request one:
101
102 https://pause.perl.org/pause/query?ACTION=request_id
103
104Check that your account is allowed to upload perl distros: goto
105https://pause.perl.org/, login, then select 'upload file to CPAN'; there
106should be a "For pumpkings only: Send a CC" tickbox. If not, ask Andreas
107K├Ânig to add your ID to the list of people allowed to upload something
108called perl. You can find Andreas' email address at:
4d2c8158 109
fd838dcf
JV
110 https://pause.perl.org/pause/query?ACTION=pause_04imprint
111
8c35d285
JV
112=item CPAN mirror
113
114Some release engineering steps require a full mirror of the CPAN.
115Work to fall back to using a remote mirror via HTTP is incomplete
116but ongoing. (No, a minicpan mirror is not sufficient)
117
118=item git checkout and commit bit
fd838dcf
JV
119
120You will need a working C<git> installation, checkout of the perl
121git repository and perl commit bit. For information about working
122with perl and git, see F<pod/perlrepository.pod>.
123
124If you are not yet a perl committer, you won't be able to make a
125release. Have a chat with whichever evil perl porter tried to talk
126you into the idea in the first place to figure out the best way to
127resolve the issue.
128
f6af4394 129
8c35d285 130=item Quotation for release announcement epigraph
f6af4394 131
8c35d285 132I<SKIP this step for SNAPSHOT and RC>
f6af4394 133
8c35d285
JV
134For a numbered blead or maint release of perl, you will need a quotation
135to use as an epigraph to your release announcement. (There's no harm
136in having one for a snapshot, but it's not required).
46743ef7 137
f6af4394
DM
138
139=back
140
f6af4394 141
8c35d285
JV
142=head2 Building a release
143
144The work of building a release candidate for a numbered release of
145perl generally starts several weeks before the first release candidate.
146Some of these should be done regularly, but all I<must> be done in the
147runup to a release.
7277a900
GS
148
149=over 4
150
f6af4394
DM
151=item *
152
8c35d285
JV
153I<You MAY SKIP this step for SNAPSHOT>
154
f6af4394
DM
155Ensure that dual-life CPAN modules are synchronised with CPAN. Basically,
156run the following:
157
db3f805e 158 $ ./perl -Ilib Porting/core-cpan-diff -a -o /tmp/corediffs
7277a900 159
f6af4394
DM
160to see any inconsistencies between the core and CPAN versions of distros,
161then fix the core, or cajole CPAN authors as appropriate. See also the
162C<-d> and C<-v> options for more detail. You'll probably want to use the
163C<-c cachedir> option to avoid repeated CPAN downloads.
7277a900 164
f6af4394 165To see which core distro versions differ from the current CPAN versions:
7277a900 166
db3f805e 167 $ ./perl -Ilib Porting/core-cpan-diff -x -a
7277a900 168
636a1918
DM
169if you are making a maint release, run C<core-cpan-diff> on both blead and
170maint, then diff the two outputs. Compare this with what you expect, and if
171necessary, fix things up. For example, you might think that both blead
172and maint are synchronised with a particular CPAN module, but one might
173have some extra changes.
174
f6af4394 175=item *
7277a900 176
8c35d285
JV
177I<You MAY SKIP this step for SNAPSHOT>
178
f6af4394 179Ensure dual-life CPAN modules are stable, which comes down to:
7277a900
GS
180
181 for each module that fails its regression tests on $current
f6af4394
DM
182 did it fail identically on $previous?
183 if yes, "SEP" (Somebody Else's Problem)
184 else work out why it failed (a bisect is useful for this)
7277a900
GS
185
186 attempt to group failure causes
187
188 for each failure cause
f6af4394
DM
189 is that a regression?
190 if yes, figure out how to fix it
191 (more code? revert the code that broke it)
192 else
193 (presumably) it's relying on something un-or-under-documented
194 should the existing behaviour stay?
195 yes - goto "regression"
196 no - note it in perldelta as a significant bugfix
197 (also, try to inform the module's author)
1aff5354 198
f6af4394 199=item *
7277a900 200
8c35d285
JV
201I<You MAY SKIP this step for SNAPSHOT>
202
f6af4394 203Similarly, monitor the smoking of core tests, and try to fix.
7277a900 204
f6af4394 205=item *
7277a900 206
8c35d285
JV
207I<You MAY SKIP this step for SNAPSHOT>
208
636a1918
DM
209Similarly, monitor the smoking of perl for compiler warnings, and try to
210fix.
211
212=item *
213
8c35d285
JV
214I<You MAY SKIP this step for SNAPSHOT>
215
f6af4394
DM
216Run F<Porting/cmpVERSION.pl> to compare the current source tree with the
217previous version to check for for modules that have identical version
218numbers but different contents, e.g.:
7277a900 219
f6af4394
DM
220 $ cd ~/some-perl-root
221 $ ./perl -Ilib Porting/cmpVERSION.pl -xd ~/my_perl-tarballs/perl-5.10.0 .
222
223then bump the version numbers of any non-dual-life modules that have
224changed since the previous release, but which still have the old version
225number. If there is more than one maintenance branch (e.g. 5.8.x, 5.10.x),
226then compare against both.
227
228Note that some of the files listed may be generated (e.g. copied from ext/
229to lib/, or a script like lib/lib_pm.PL is run to produce lib/lib.pm);
230make sure you edit the correct file!
231
232Once all version numbers have been bumped, re-run the checks.
233
234Then run again without the -x option, to check that dual-life modules are
235also sensible.
236
55878aed
JV
237=item *
238
239Check that files managed by F<regen.pl> and friends are up to date. From
240within your working directory:
241
242
ee56566f 243 $ git status
55878aed
JV
244 $ make regen
245 $ make regen_perly
ee56566f 246 $ git status
55878aed
JV
247
248If any of the files managed by regen.pl have changed, then you should commit
249the updated versions:
250
251 $ git commit -m 'Updated files generated by regen tools for perl 5.x.y' <list of files>
252
f6af4394
DM
253
254=item *
255
8c35d285
JV
256I<You MAY SKIP this step for SNAPSHOT>
257
f6af4394 258Get perldelta in a mostly finished state.
db3f805e 259
636a1918
DM
260Peruse F<Porting/how_to_write_a_perldelta.pod>, and try to make sure that
261every section it lists is, if necessary, populated and complete. Copy
262edit the whole document.
f6af4394
DM
263
264=item *
265
8c35d285
JV
266I<You MUST SKIP this step for SNAPSHOT>
267
f6af4394
DM
268Bump the perl version number (e.g. from 5.10.0 to 5.10.1).
269
270There is a tool to semi-automate this process. It works in two stages.
271First, it generates a list of suggested changes, which you review and
272edit; then you feed this list back and it applies the edits. So, first
273scan the source dir looking for likely candidates:
274
275 $ Porting/bump-perl-version -s 5.10.0 5.10.1 > /tmp/scan
276
277This produces a file containing a list of suggested edits, eg:
278
279 NetWare/Makefile
280
281 89: -MODULE_DESC = "Perl 5.10.0 for NetWare"
282 +MODULE_DESC = "Perl 5.10.1 for NetWare"
283
284i.e. in the file F<NetWare/Makefile>, line 89 would be changed as shown.
285Review the file carefully, and delete any -/+ line pairs that you don't
286want changing. Remember that this tool is largely just grepping for '5.10.0'
287or whatever, so it will generate false positives. Be careful not change
288text like "this was fixed in 5.10.0"! Then run:
289
290 $ Porting/bump-perl-version -u < /tmp/scan
291
292which will update all the files shown; then commit the changes.
293
294Be particularly careful with F<INSTALL>, which contains a mixture of
295C<5.10.0>-type strings, some of which need bumping on every release, and
296some of which need to be left. Also note that this tool currently only
297performs a single change per line, so in particular, this line in
298README.vms needs special handling:
299
300 rename perl-5^.10^.1.dir perl-5_10_1.dir
7277a900 301
dc0a62a1
DM
302
303=item *
304
8c35d285
JV
305I<You MUST SKIP this step for SNAPSHOT>
306
dc0a62a1
DM
307Review and update INSTALL to account for the change in version number;
308in particular, the "Coexistence with earlier versions of perl 5" section.
309
f6af4394 310=item *
7277a900 311
8c35d285
JV
312I<You MUST SKIP this step for SNAPSHOT>
313
f6af4394
DM
314Update the F<Changes> file to contain the git log command which would show
315all the changes in this release. You will need assume the existence of a
316not-yet created tag for the forthcoming release; e.g.
7277a900 317
f6af4394 318 git log ... perl-5.10.0..perl5.12.0
7277a900 319
f6af4394
DM
320Due to warts in the perforce-to-git migration, some branches require extra
321exclusions to avoid other branches being pulled in. Make sure you have the
322correct incantation: replace the not-yet-created tag with C<HEAD> and see
323if git log produces roughly the right number of commits across roughly the
324right time period.
7277a900 325
dc0a62a1 326
f6af4394 327=item *
7277a900 328
f6af4394 329Check some more build configurations, e.g.
7277a900 330
f6af4394
DM
331 -Duseshrplib -Dd_dosuid
332 make suidperl
7277a900 333
f6af4394
DM
334Check that setuid installs works (for < 5.11.0 only).
335XXX any other configs?
7277a900 336
7277a900 337
f6af4394 338=item *
7277a900 339
8c35d285
JV
340I<You MAY SKIP this step for SNAPSHOT>
341
f6af4394 342Update F<AUTHORS>, using the C<Porting/checkAUTHORS.pl> script, and if
ce80ee91
JV
343necessary, update the script to include new alias mappings for porters
344already in F<AUTHORS>
f6af4394 345
ce80ee91 346 $ git log | perl Porting/checkAUTHORS.pl --acknowledged AUTHORS -
f6af4394 347
8c35d285 348=item *
f6af4394 349
8c35d285 350I<You MAY SKIP this step for SNAPSHOT>
f6af4394 351
8c35d285
JV
352As there are no regular smokes [ XXX yet - please fix?] find out about the
353state of the current branch on VMS. If the branch you're releasing on
354is failing tests on VMS, you may not want to do a release.
355
356=item *
357
358Configure and build perl so that you have a Makefile and porting tools:
359
360 $ ./Configure -Dusedevel -des
361 $ make
362
363=item *
364
365Rebuild META.yml:
366
367 $ rm META.yml
368 $ make META.yml
369
370Commit META.yml if it has changed:
371
372 $ git commit -m 'Updating META.yml in preparation for release of 5.x.y' META.yml
373
374=item *
375
376Check that the manifest is sorted and correct:
377
378 $ make manisort
379 $ make distclean
380 $ perl Porting/manicheck
381
382
383Commit MANIFEST if it has changed:
384
385 $ git commit -m 'Updating MANIFEST in preparation for release of 5.x.y' MANIFEST
386
387
388
389=item *
390
391I<You MUST SKIP this step for SNAPSHOT>
392
393A dd an entry to F<pod/perlhist.pod> with the current date:
394
395 5.8.9-RC1 2008-Nov-10
396
397Make sure the correct pumpking is listed, and if this is the first release
398under the stewardship of a new pumpking, make sure that his or her name
399is listed in the section entitled C<THE KEEPERS OF THE PUMPKIN>.
400
401Be sure to commit your changes:
402
403 $ git commit -m 'Updating perlhist in preparation for release of 5.x.y pod/perlhist.pod
404
405
406=item *
407
408Build perl, then make sure it passes its own test suite, and installs:
409
410 $ ./Configure -des -Dusedevel -Dprefix=/tmp/perl-5.x.y-pretest
411 $ make test install
412
413=item *
414
415Create a tarball. Use the C<-s> option to specify a suitable suffix for
416the tarball and directory name:
417
418 $ cd root/of/perl/tree
419 $ make distclean
420 $ git clean -xdf # make sure perl and git agree on files
421
422 $ perl Porting/makerel -b -s `git describe` # for a snapshot
423 $ perl Porting/makerel -b -s RC1 # for a release candidate
424 $ perl Porting/makerel -b # for a final release
425
426This creates the directory F<../perl-x.y.z-RC1> or similar, copies all
427the MANIFEST files into it, sets the correct permissions on them,
428adds DOS line endings to some, then tars it up as
429F<../perl-x.y.z-RC1.tar.gz>. With C<-b>, it also creates a C<tar.bz2> file.
430
431XXX if we go for extra tags and branches stuff, then add the extra details
432here
433
434=item *
435
436Copy the tarballs (.gz and possibly .bz2) to a web server somewhere you
437have access to.
438
439=item *
440
441Download the tarball to some other machine. For a release candidate,
442you really want to test your tarball on two or more different platforms
443and architectures. The #p5p IRC channel on irc.perl.org is a good place
444to find willing victims.
445
446=item *
447
448Check that basic configuration and tests work on each test machine:
449
450 $ ./Configure -des && make all test
f6af4394
DM
451
452=item *
453
8c35d285
JV
454Check that the test harness and install work on each test machine:
455
456 $ ./Configure -des -Dprefix=/install/path && make all test_harness install
457
458=item *
459
460Check that the output of C<perl -v> and C<perl -V> are as expected,
461especially as regards version numbers, patch and/or RC levels, and @INC
462paths.
463
464Note that the results may be different without a F<.git/> directory,
465which is why you should test from the tarball.
466
467=item *
468
469Bootstrap the CPAN client on the clean install:
470
471 $ ./bin/perl -MCPAN -e'shell'
472
473=item *
474
475Install Inline.pm
476
477 $ ./bin/perl -MCPAN -e'install Inline'
478
479Check that your perl can run this:
480
481 $ ./bin/perl -lwe 'use Inline C => "int answer() { return 42;} "; print answer'
482
483=item *
484
485Bootstrap the CPANPLUS client on the clean install:
486
487 $ ./bin/cpanp
488
489
490=item *
491
492Install an XS module.
493
494=item *
495
496If all is well, announce the snapshot to p5p. (For a release candidate,
497instead follow the further steps described later.)
498
499
500=item *
501
502
503I<You MAY SKIP this step for SNAPSHOT>
504
f6af4394
DM
505Re-read the perldelta to try to find any embarrassing typos and thinkos;
506remove any C<TODO> or C<XXX> flags; and run through pod and spell
636a1918
DM
507checkers, e.g.
508
509 podchecker -warnings -warnings pod/perl5101delta.pod
510 spell pod/perl5101delta.pod
f6af4394
DM
511
512=item *
513
8c35d285
JV
514I<You MUST SKIP this step for SNAPSHOT>
515
f6af4394
DM
516Update patchlevel.h to add a C<-RC1>-or-whatever string; or, if this is a
517final release, remove it. [ XXX how now?? see 34813 for old way ]
518
519=item *
520
8c35d285
JV
521I<You MUST SKIP this step for SNAPSHOT>
522
f6af4394 523Update C<Module::Corelist>.
210de33e 524
ce4f4fe2 525Note that if this is a maint release, you should run the following actions
210de33e
DM
526from the maint directory, but edit the C<Corelist.pm> in I<blead> and
527subsequently cherry-pick it.
528
dc2f75c0
JV
529corelist.pl uses ftp.funet.fi to verify information about dual-lifed
530modules on CPAN. It can use a full, local CPAN mirror or fall back
531to C<wget> or C<curl> to fetch only package metadata remotely.
210de33e 532
dc2f75c0
JV
533(If you'd prefer to have a full CPAN mirror, see
534http://www.cpan.org/misc/cpan-faq.html#How_mirror_CPAN)
210de33e 535
210de33e 536
dc2f75c0 537Then change to your perl checkout.
210de33e 538
dc2f75c0 539If you have a local CPAN mirror, run:
210de33e 540
4d2c8158
JV
541 $ make perl
542 $ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror
210de33e 543
dc2f75c0 544Otherwise, run:
210de33e 545
4d2c8158
JV
546 $ make perl
547 $ ./perl -Ilib Porting/corelist.pl cpan
210de33e 548
dc2f75c0 549This will chug for a while. Assuming all goes well, it will
4d2c8158 550update lib/Module/CoreList.pm.
210de33e 551
dc2f75c0 552Check that file over carefully:
210de33e 553
dc2f75c0
JV
554 $ git diff lib/Module/CoreList.pm
555
556
557If necessary, bump C<$VERSION> (there's no need to do this for
558every RC; in RC1, bump the version to a new clean number that will
559appear in the final release, and leave as-is for the later RCs and final).
210de33e 560
ce4f4fe2 561Edit the version number in the new C<< 'Module::CoreList' => 'X.YZ' >>
210de33e
DM
562entry, as that is likely to reflect the previous version number.
563
8c35d285 564If this is a final release (rather than a release candidate):
dc2f75c0 565
4d2c8158
JV
566=over 4
567
568=item *
569
570Update this version's entry in the C<%released> hash with today's date.
571
572=item *
573
574Make sure that the script has correctly updated the C<CAVEATS> section
575
576=back
210de33e 577
dc2f75c0
JV
578Finally, commit the new version of Module::CoreList:
579
580 $ git commit -m 'Updated Module::CoreList for the 5.x.y release' \
581 lib/Module/Corelist.pm
582
7277a900 583
f6af4394
DM
584=item *
585
addebd58
DM
586Disarm the patchlevel.h change [ XXX expand ]
587
588=item *
589
8c35d285
JV
590I<You MAY SKIP this step for SNAPSHOT>
591
f6af4394
DM
592Wait for the smoke tests to catch up with the commit which this release is
593based on (or at least the last commit of any consequence).
7277a900 594
f6af4394
DM
595Then check that the smoke tests pass (particularly on Win32). If not, go
596back and fix things.
7277a900 597
7277a900 598
f6af4394 599=item *
7277a900 600
8c35d285
JV
601I<You MUST SKIP this step for SNAPSHOT>
602
f6af4394 603Once smoking is okay, upload it to PAUSE. This is the point of no return.
db3f805e
JV
604If anything goes wrong after this point, you will need to re-prepare
605a new release with a new minor version or RC number.
606
addebd58 607You may wish to create a .bz2 version of the tarball and upload that too.
f6af4394 608
210de33e
DM
609=item *
610
8c35d285
JV
611I<You MUST SKIP this step for SNAPSHOT>
612
db3f805e 613Create a tag for the exact git revsion you built the release from:
210de33e
DM
614
615 $ git tag perl-5.10.1-RC1 -m'Release Candidate 1 of Perl 5.10.1'
616 $ git push origin tag perl-5.10.1-RC1
f6af4394
DM
617
618=item *
619
db3f805e 620Mail p5p to announce your new release, with a quote you prepared earlier.
f6af4394
DM
621
622=item *
623
8c35d285
JV
624I<You MAY SKIP this step for SNAPSHOT>
625
f6af4394 626Wait 24 hours or so, then post the announcement to use.perl.org.
addebd58
DM
627(if you don't have access rights to post news, ask someone like Rafael to
628do it for you.)
f6af4394 629
f6af4394 630=item *
7277a900 631
8c35d285 632I<You MUST SKIP this step for SNAPSHOT, RC, BLEAD>
7277a900 633
f6af4394
DM
634Ask Jarkko to update http://www.cpan.org/src/README.html and
635Rafael to update http://dev.perl.org/perl5/
7277a900 636
f6af4394 637=item *
7277a900 638
8c35d285
JV
639I<You MUST SKIP this step for SNAPSHOT, RC>
640
f6af4394
DM
641Create a new empty perlNNNdelta.pod file for the current release + 1;
642see F<Porting/how_to_write_a_perldelta.pod>.
643[ XXX Perhaps we should have an empty template file we can copy in. ]
7277a900 644
a2cba4bc 645In addition, edit F<pod.lst>, adding the new entry as 'D', and unmark previous
57433fbf 646entry as 'D',
a2cba4bc 647
57433fbf 648Change perlNNNdelta references to the new version in these files
7277a900 649
f6af4394
DM
650 INSTALL
651 win32/Makefile.mk
652 win32/Makefile
653 Makefile.SH
654 README
7277a900 655
f6af4394
DM
656Also, edit the previous delta file to change the C<NAME> from C<perldelta>
657to C<perlNNNdelta>.
7277a900 658
f6af4394
DM
659These two lists of files probably aren't exhaustive; do a recursive grep
660on the previous filename to look for suitable candidates.
7277a900 661
f6af4394 662(see 16410843ea for an example).
7277a900 663
f6af4394 664=item *
7277a900 665
57433fbf
JV
666Run C<perl pod/buildtoc --build-all> to update the following files:
667
668 MANIFEST
669 pod/perl.pod
670 win32/pod.mak
671 vms/descrip_mms.template
672
673If you modified perldelta.pod, (F<vms/descrip_mms.template> will
674needs a manual edit to bump the C<perldelta.pod> entry - it would
675be good for someone to figure out the fix.)
676
677=item *
678
8c35d285 679I<You MUST SKIP this step for SNAPSHOT, RC, BLEAD>
dc0a62a1 680
8c35d285
JV
681If this was a maint release, then edit F<Porting/mergelog> to change
682all the C<d> (deferred) flags to C<.> (needs review).
addebd58 683
8c35d285
JV
684XXX - we should be able to use git to automate much of the role
685previously filled by the mergelog.
addebd58
DM
686
687=item *
688
8c35d285 689I<You MUST SKIP this step for SNAPSHOT, RC, BLEAD>
addebd58 690
8c35d285
JV
691If this was a major release (5.x.0), then create a new maint branch
692based on the commit tagged as the current release and bump the version
693in the blead branch in git, e.g. 5.12.0 to 5.13.0.
addebd58
DM
694
695[ XXX probably lots more stuff to do, including perldelta,
f6af4394 696C<lib/feature.pm> ]
7277a900 697
8c35d285 698XXX need a git recipe
addebd58
DM
699
700=item *
701
8c35d285
JV
702I<You MUST SKIP this step for SNAPSHOT, RC, BLEAD>
703
f6af4394
DM
704Copy the perlNNNdelta.pod for this release into the other branches, and
705remember to update these files on those branches too:
7277a900 706
f6af4394
DM
707 MANIFEST
708 pod.lst
709 pod/perl.pod
710 vms/descrip_mms.template
711 win32/pod.mak
7277a900 712
f6af4394 713(see fc5be80860 for an example).
7277a900 714
f6af4394 715=item *
7277a900 716
8c35d285
JV
717I<You MUST SKIP this step for SNAPSHOT>
718
f6af4394
DM
719Make sure any recent F<pod/perlhist.pod> entries are copied to
720F<perlhist.pod> on other branches; typically the RC* and final entries,
721e.g.
7277a900 722
f6af4394
DM
723 5.8.9-RC1 2008-Nov-10
724 5.8.9-RC2 2008-Dec-06
725 5.8.9 2008-Dec-14
7277a900 726
6e40fbf9
DM
727=item *
728
8c35d285
JV
729I<You MUST SKIP this step for SNAPSHOT, RC>
730
6e40fbf9
DM
731Remind the current maintainer of C<Module::CoreList> to push a new release
732to CPAN.
733
8c35d285
JV
734=item *
735
736I<You MUST RETIRE to your preferred PUB, CAFE or SEASIDE VILLA for some much-needed
737rest and relaxation>.
738
739Thanks for releasing perl!
740
7277a900
GS
741=back
742
743=head1 SOURCE
744
f6af4394
DM
745Based on
746http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2009-05/msg00608.html,
747plus a whole bunch of other sources, including private correspondence.
7277a900
GS
748
749=cut
750