Commit | Line | Data |
---|---|---|
49781f4a AB |
1 | =encoding utf8 |
2 | ||
7277a900 GS |
3 | =head1 NAME |
4 | ||
5 | release_managers_guide - Releasing a new version of perl 5.x | |
6 | ||
dc0a4df9 DM |
7 | Note that things change at each release, so there may be new things not |
8 | covered here, or tools may need updating. | |
9 | ||
c78277ad DR |
10 | =head1 MAKING A CHECKLIST |
11 | ||
12 | If you are preparing to do a release, you can run the | |
13 | F<Porting/make-rmg-checklist> script to generate a new version of this | |
14 | document that starts with a checklist for your release. | |
15 | ||
16 | This script is run as: | |
17 | ||
78a62309 SH |
18 | perl Porting/make-rmg-checklist \ |
19 | --type [BLEAD-POINT or MAINT or ...] > /tmp/rmg.pod | |
c78277ad DR |
20 | |
21 | You can also pass the C<--html> flag to generate an HTML document instead of | |
22 | POD. | |
f6af4394 | 23 | |
78a62309 SH |
24 | perl Porting/make-rmg-checklist --html \ |
25 | --type [BLEAD-POINT or MAINT or ...] > /tmp/rmg.html | |
0056d3d2 | 26 | |
7277a900 GS |
27 | =head1 SYNOPSIS |
28 | ||
f6af4394 | 29 | This document describes the series of tasks required - some automatic, some |
dc0a4df9 DM |
30 | manual - to produce a perl release of some description, be that a release |
31 | candidate, or final, numbered release of maint or blead. | |
f6af4394 | 32 | |
8c35d285 | 33 | The release process has traditionally been executed by the current |
ee76d676 JV |
34 | pumpking. Blead releases from 5.11.0 forward are made each month on the |
35 | 20th by a non-pumpking release engineer. The release engineer roster | |
36 | and schedule can be found in Porting/release_schedule.pod. | |
7277a900 | 37 | |
fdaa3f94 CBW |
38 | This document both helps as a check-list for the release engineer |
39 | and is a base for ideas on how the various tasks could be automated | |
8c35d285 | 40 | or distributed. |
7277a900 | 41 | |
da571fa1 | 42 | The checklist of a typical release cycle is as follows: |
f6af4394 | 43 | |
636a1918 | 44 | (5.10.1 is released, and post-release actions have been done) |
f6af4394 DM |
45 | |
46 | ...time passes... | |
47 | ||
f6af4394 DM |
48 | a few weeks before the release, a number of steps are performed, |
49 | including bumping the version to 5.10.2 | |
636a1918 | 50 | |
e158965a | 51 | ...a few weeks pass... |
46743ef7 | 52 | |
f6af4394 DM |
53 | perl-5.10.2-RC1 is released |
54 | ||
55 | perl-5.10.2 is released | |
56 | ||
57 | post-release actions are performed, including creating new | |
c5b87fed | 58 | perldelta.pod |
f6af4394 DM |
59 | |
60 | ... the cycle continues ... | |
7277a900 GS |
61 | |
62 | =head1 DETAILS | |
63 | ||
6a958a95 DM |
64 | Some of the tasks described below apply to all four types of |
65 | release of Perl. (blead, RC, final release of maint, final | |
8c35d285 | 66 | release of blead). Some of these tasks apply only to a subset |
fdaa3f94 | 67 | of these release types. If a step does not apply to a given |
8c35d285 JV |
68 | type of release, you will see a notation to that effect at |
69 | the beginning of the step. | |
70 | ||
71 | =head2 Release types | |
72 | ||
73 | =over 4 | |
74 | ||
8c35d285 JV |
75 | =item Release Candidate (RC) |
76 | ||
d60a1044 DM |
77 | A release candidate is an attempt to produce a tarball that is a close as |
78 | possible to the final release. Indeed, unless critical faults are found | |
79 | during the RC testing, the final release will be identical to the RC | |
80 | barring a few minor fixups (updating the release date in F<perlhist.pod>, | |
81 | removing the RC status from F<patchlevel.h>, etc). If faults are found, | |
82 | then the fixes should be put into a new release candidate, never directly | |
83 | into a final release. | |
8c35d285 | 84 | |
6a958a95 DM |
85 | |
86 | =item Stable/Maint release (MAINT). | |
87 | ||
88 | A release with an even version number, and subversion number > 0, such as | |
89 | 5.14.1 or 5.14.2. | |
8c35d285 JV |
90 | |
91 | At this point you should have a working release candidate with few or no | |
92 | changes since. | |
93 | ||
94 | It's essentially the same procedure as for making a release candidate, but | |
95 | with a whole bunch of extra post-release steps. | |
96 | ||
74648505 DM |
97 | Note that for a maint release there are two versions of this guide to |
98 | consider: the one in the maint branch, and the one in blead. Which one to | |
99 | use is a fine judgement. The blead one will be most up-to-date, while | |
100 | it might describe some steps or new tools that aren't applicable to older | |
101 | maint branches. It is probably best to review both versions of this | |
102 | document, but to most closely follow the steps in the maint version. | |
103 | ||
6a958a95 DM |
104 | =item A blead point release (BLEAD-POINT) |
105 | ||
106 | A release with an odd version number, such as 5.15.0 or 5.15.1. | |
107 | ||
108 | This isn't for production, so it has less stability requirements than for | |
109 | other release types, and isn't preceded by RC releases. Other than that, | |
110 | it is similar to a MAINT release. | |
111 | ||
112 | =item Blead final release (BLEAD-FINAL) | |
113 | ||
114 | A release with an even version number, and subversion number == 0, such as | |
dc0a4df9 | 115 | 5.14.0. That is to say, it's the big new release once per year. |
8c35d285 JV |
116 | |
117 | It's essentially the same procedure as for making a release candidate, but | |
6a958a95 | 118 | with a whole bunch of extra post-release steps, even more than for MAINT. |
8c35d285 JV |
119 | |
120 | =back | |
7277a900 | 121 | |
da571fa1 | 122 | =for checklist begin |
dc0a4df9 | 123 | |
fd838dcf JV |
124 | =head2 Prerequisites |
125 | ||
126 | Before you can make an official release of perl, there are a few | |
127 | hoops you need to jump through: | |
128 | ||
00c28750 | 129 | =head3 PAUSE account with pumpkin status |
8c35d285 | 130 | |
fd838dcf JV |
131 | Make sure you have a PAUSE account suitable for uploading a perl release. |
132 | If you don't have a PAUSE account, then request one: | |
133 | ||
134 | https://pause.perl.org/pause/query?ACTION=request_id | |
135 | ||
9a3b7d40 FR |
136 | Check that your account is allowed to upload perl distros: go to |
137 | L<https://pause.perl.org/pause/authenquery?ACTION=who_pumpkin> and check that | |
138 | your PAUSE ID is listed there. If not, ask Andreas KE<0xf6>nig to add your ID | |
139 | to the list of people allowed to upload something called perl. You can find | |
140 | Andreas' email address at: | |
4d2c8158 | 141 | |
fd838dcf JV |
142 | https://pause.perl.org/pause/query?ACTION=pause_04imprint |
143 | ||
a72d816c RS |
144 | =head3 rt.perl.org update access |
145 | ||
146 | Make sure you have permission to close tickets on L<http://rt.perl.org/> | |
147 | so you can respond to bug report as necessary during your stint. If you | |
148 | don't, make an account (if you don't have one) and contact the pumpking | |
149 | with your username to get ticket-closing permission. | |
150 | ||
da571fa1 | 151 | =head3 git checkout and commit bit |
fd838dcf JV |
152 | |
153 | You will need a working C<git> installation, checkout of the perl | |
154 | git repository and perl commit bit. For information about working | |
c222ef46 | 155 | with perl and git, see F<pod/perlgit.pod>. |
fd838dcf JV |
156 | |
157 | If you are not yet a perl committer, you won't be able to make a | |
158 | release. Have a chat with whichever evil perl porter tried to talk | |
159 | you into the idea in the first place to figure out the best way to | |
160 | resolve the issue. | |
161 | ||
96644a2c DG |
162 | =head3 web-based file share |
163 | ||
164 | You will need to be able to share tarballs with #p5p members for | |
165 | pre-release testing, and you may wish to upload to PAUSE via URL. | |
166 | Make sure you have a way of sharing files, such as a web server or | |
167 | file-sharing service. | |
168 | ||
169 | Porters have access to the "dromedary" server (users.perl5.git.perl.org), | |
405350d5 A |
170 | which has a F<public_html> directory to share files with. |
171 | (L<http://users.perl5.git.perl.org/~username/perl-5.xx.y.tar.gz>) | |
96644a2c DG |
172 | |
173 | If you use Dropbox, you can append "raw=1" as a parameter to their usual | |
174 | sharing link to allow direct download (albeit with redirects). | |
175 | ||
845a9291 MM |
176 | =head3 git clone of https://github.com/perlorg/perlweb |
177 | ||
178 | For updating the L<http://dev.perl.org> web pages, either a Github account or | |
179 | sweet-talking somebody with a Github account into obedience is needed. This | |
180 | is only needed on the day of the release or shortly afterwards. | |
181 | ||
da571fa1 | 182 | =head3 Quotation for release announcement epigraph |
f6af4394 | 183 | |
dffcb1c0 | 184 | You will need a quotation to use as an epigraph to your release announcement. |
46743ef7 | 185 | |
c282dc5e A |
186 | =head3 Install the previous version of perl |
187 | ||
188 | During the testing phase of the release you have created, you will be | |
189 | asked to compare the installed files with a previous install. Save yourself | |
190 | some time on release day, and have a (clean) install of the previous | |
191 | version ready. | |
192 | ||
2e831dfd | 193 | =head2 Building a release - advance actions |
8c35d285 | 194 | |
9c39c536 A |
195 | The work of building a release candidate for an even numbered release |
196 | (BLEAD-FINAL) of perl generally starts several weeks before the first | |
197 | release candidate. Some of the following steps should be done regularly, | |
198 | but all I<must> be done in the run up to a release. | |
7277a900 | 199 | |
dc0a4df9 | 200 | =head3 dual-life CPAN module synchronisation |
f6af4394 | 201 | |
1d84c074 | 202 | To see which core distro versions differ from the current CPAN versions: |
f6af4394 | 203 | |
1d84c074 | 204 | $ ./perl -Ilib Porting/core-cpan-diff -x -a |
7277a900 | 205 | |
1dbf7599 DG |
206 | However, this only checks whether the version recorded in |
207 | F<Porting/Maintainers.pl> differs from the latest on CPAN. It doesn't tell you | |
208 | if the code itself has diverged from CPAN. | |
7277a900 | 209 | |
1d84c074 JL |
210 | You can also run an actual diff of the contents of the modules, comparing core |
211 | to CPAN, to ensure that there were no erroneous/extraneous changes that need to | |
212 | be dealt with. You do this by not passing the C<-x> option: | |
7277a900 | 213 | |
1d84c074 JL |
214 | $ ./perl -Ilib Porting/core-cpan-diff -a -o /tmp/corediffs |
215 | ||
3804a1f7 SH |
216 | Passing C<-u cpan> will probably be helpful, since it limits the search to |
217 | distributions with 'cpan' upstream source. (It's OK for blead upstream to | |
218 | differ from CPAN because those dual-life releases usually come I<after> perl | |
219 | is released.) | |
1dbf7599 DG |
220 | |
221 | See also the C<-d> and C<-v> options for more detail (and the C<-u> option as | |
222 | mentioned above). You'll probably want to use the C<-c cachedir> option to | |
223 | avoid repeated CPAN downloads and may want to use C<-m file:///mirror/path> if | |
224 | you made a local CPAN mirror. Note that a minicpan mirror won't actually work, | |
225 | but can provide a good first pass to quickly get a list of modules which | |
226 | definitely haven't changed, to avoid having to download absolutely everything. | |
227 | ||
193c036f SH |
228 | For a BLEAD-POINT or BLEAD-FINAL release with 'cpan' upstream, if a CPAN |
229 | release appears to be ahead of blead, then consider updating it (or asking the | |
230 | relevant porter to do so). (However, if this is a BLEAD-FINAL release or one of | |
231 | the last BLEAD-POINT releases before it and hence blead is in some kind of | |
232 | "code freeze" state (e.g. the sequence might be "contentious changes freeze", | |
233 | then "user-visible changes freeze" and finally "full code freeze") then any | |
234 | CPAN module updates must be subject to the same restrictions, so it may not be | |
235 | possible to update all modules until after the BLEAD-FINAL release.) If blead | |
236 | contains edits to a 'cpan' upstream module, this is naughty but sometimes | |
237 | unavoidable to keep blead tests passing. Make sure the affected file has a | |
238 | CUSTOMIZED entry in F<Porting/Maintainers.pl>. | |
7277a900 | 239 | |
6a958a95 | 240 | If you are making a MAINT release, run C<core-cpan-diff> on both blead and |
636a1918 DM |
241 | maint, then diff the two outputs. Compare this with what you expect, and if |
242 | necessary, fix things up. For example, you might think that both blead | |
243 | and maint are synchronised with a particular CPAN module, but one might | |
fdaa3f94 | 244 | have some extra changes. |
636a1918 | 245 | |
9e08bfd8 | 246 | =head3 How to sync a CPAN module with a cpanE<sol> distro |
9c39c536 A |
247 | |
248 | =over 4 | |
249 | ||
250 | =item * | |
251 | ||
252 | Fetch the most recent version from CPAN. | |
253 | ||
254 | =item * | |
255 | ||
256 | Unpack the retrieved tarball. Rename the old directory; rename the new | |
257 | directory to the original name. | |
258 | ||
259 | =item * | |
260 | ||
9e40a104 | 261 | Restore any F<.gitignore> file. This can be done by issuing |
02cbdfef | 262 | C<git checkout .gitignore> in the F<cpan/Distro> directory. |
9c39c536 A |
263 | |
264 | =item * | |
265 | ||
266 | Remove files we do not need. That is, remove any files that match the | |
812ce6dc | 267 | entries in C<@IGNORABLE> in F<Porting/Maintainers.pl>, and anything that |
9c39c536 A |
268 | matches the C<EXCLUDED> section of the distro's entry in the C<%Modules> |
269 | hash. | |
270 | ||
271 | =item * | |
272 | ||
273 | Restore any files mentioned in the C<CUSTOMIZED> section, using | |
274 | C<git checkout>. Make any new customizations if necessary. Also, | |
275 | restore any files that are mentioned in C<@IGNORE>, but were checked | |
c5fb089a | 276 | into the repository anyway. |
9c39c536 A |
277 | |
278 | =item * | |
279 | ||
280 | For any new files in the distro, determine whether they are needed. | |
0f5c5828 | 281 | If not, delete them, and list them in either C<EXCLUDED> or C<@IGNORABLE>. |
9c39c536 A |
282 | Otherwise, add them to C<MANIFEST>, and run C<git add> to add the files |
283 | to the repository. | |
284 | ||
285 | =item * | |
286 | ||
287 | For any files that are gone, remove them from C<MANIFEST>, and use | |
288 | C<git rm> to tell git the files will be gone. | |
289 | ||
290 | =item * | |
291 | ||
292 | If the C<MANIFEST> file was changed in any of the previous steps, run | |
293 | C<perl Porting/manisort --output MANIFEST.sort; mv MANIFEST.sort MANIFEST>. | |
294 | ||
295 | =item * | |
296 | ||
297 | For any files that have an execute bit set, either remove the execute | |
02cbdfef | 298 | bit, or edit F<Porting/exec-bit.txt> |
9c39c536 A |
299 | |
300 | =item * | |
301 | ||
0b7399e1 | 302 | Run C<make> (or C<nmake> on Windows), see if C<perl> compiles. |
9c39c536 A |
303 | |
304 | =item * | |
305 | ||
306 | Run the tests for the package. | |
307 | ||
308 | =item * | |
309 | ||
812ce6dc | 310 | Run the tests in F<t/porting> (C<make test_porting>). |
9c39c536 A |
311 | |
312 | =item * | |
313 | ||
02cbdfef | 314 | Update the C<DISTRIBUTION> entry in F<Porting/Maintainers.pl>. |
9c39c536 A |
315 | |
316 | =item * | |
317 | ||
318 | Run a full configure/build/test cycle. | |
319 | ||
320 | =item * | |
321 | ||
322 | If everything is ok, commit the changes. | |
323 | ||
324 | =back | |
325 | ||
326 | For entries with a non-simple C<FILES> section, or with a C<MAP>, you | |
327 | may have to take more steps than listed above. | |
328 | ||
02cbdfef | 329 | F<Porting/sync-with-cpan> is a script that automates most of the steps |
0b7399e1 SH |
330 | above; but see the comments at the beginning of the file. In particular, |
331 | it has not yet been exercised on Windows, but will certainly require a set | |
332 | of Unix tools such as Cygwin, and steps that run C<make> will need to run | |
333 | C<nmake> instead. | |
9c39c536 | 334 | |
dc0a4df9 | 335 | =head3 dual-life CPAN module stability |
7277a900 | 336 | |
f6af4394 | 337 | Ensure dual-life CPAN modules are stable, which comes down to: |
7277a900 | 338 | |
78a62309 SH |
339 | for each module that fails its regression tests on $current |
340 | did it fail identically on $previous? | |
341 | if yes, "SEP" (Somebody Else's Problem) | |
342 | else work out why it failed (a bisect is useful for this) | |
ed380305 | 343 | |
78a62309 | 344 | attempt to group failure causes |
ed380305 | 345 | |
78a62309 SH |
346 | for each failure cause |
347 | is that a regression? | |
348 | if yes, figure out how to fix it | |
349 | (more code? revert the code that broke it) | |
350 | else | |
351 | (presumably) it's relying on something un-or-under-documented | |
352 | should the existing behaviour stay? | |
353 | yes - goto "regression" | |
354 | no - note it in perldelta as a significant bugfix | |
355 | (also, try to inform the module's author) | |
1aff5354 | 356 | |
00c28750 | 357 | =head3 monitor smoke tests for failures |
7277a900 | 358 | |
5157df7a | 359 | Similarly, monitor the smoking of core tests, and try to fix. See |
a66bda92 MH |
360 | L<http://smoke.procura.nl/index.html>, L<http://perl5.test-smoke.org/> |
361 | and L<http://perl.develop-help.com> for a summary. See also | |
5157df7a AB |
362 | L<http://www.nntp.perl.org/group/perl.daily-build.reports/> which has |
363 | the raw reports. | |
7277a900 | 364 | |
636a1918 DM |
365 | Similarly, monitor the smoking of perl for compiler warnings, and try to |
366 | fix. | |
367 | ||
5c296d48 SH |
368 | =for checklist skip BLEAD-POINT |
369 | ||
370 | =head3 monitor CPAN testers for failures | |
371 | ||
372 | For any release except a BLEAD-POINT: Examine the relevant analysis report(s) | |
373 | at http://analysis.cpantesters.org/beforemaintrelease to see how the impending | |
374 | release is performing compared to previous releases with regard to building | |
375 | and testing CPAN modules. | |
376 | ||
2fc8e8ba RS |
377 | That page accepts a query parameter, C<pair> that takes a pair of |
378 | colon-delimited versions to use for comparison. For example: | |
379 | ||
380 | http://analysis.cpantesters.org/beforemaintrelease?pair=5.20.2:5.22.0%20RC1 | |
381 | ||
00c28750 | 382 | =head3 update perldelta |
636a1918 | 383 | |
f6af4394 | 384 | Get perldelta in a mostly finished state. |
db3f805e | 385 | |
04c2c53e | 386 | Read F<Porting/how_to_write_a_perldelta.pod>, and try to make sure that |
636a1918 DM |
387 | every section it lists is, if necessary, populated and complete. Copy |
388 | edit the whole document. | |
f6af4394 | 389 | |
1dbf7599 DG |
390 | You won't be able to automatically fill in the "Updated Modules" section until |
391 | after Module::CoreList is updated (as described below in | |
392 | L<"update Module::CoreList">). | |
f6af4394 | 393 | |
dc0a4df9 DM |
394 | =head3 Bump the version number |
395 | ||
30f926b5 JL |
396 | Do not do this yet for a BLEAD-POINT release! You will do this at the end of |
397 | the release process. | |
398 | ||
dc0a4df9 | 399 | Increase the version number (e.g. from 5.12.0 to 5.12.1). |
04dbb930 | 400 | |
30f926b5 | 401 | For a release candidate for a stable perl, this should happen a week or two |
04dbb930 DG |
402 | before the first release candidate to allow sufficient time for testing and |
403 | smoking with the target version built into the perl executable. For | |
c5fb089a | 404 | subsequent release candidates and the final release, it is not necessary to |
04dbb930 | 405 | bump the version further. |
f6af4394 | 406 | |
8b2227e6 | 407 | There is a tool to semi-automate this process: |
f6af4394 | 408 | |
78a62309 | 409 | $ ./perl -Ilib Porting/bump-perl-version -i 5.10.0 5.10.1 |
f6af4394 | 410 | |
8b2227e6 LB |
411 | Remember that this tool is largely just grepping for '5.10.0' or whatever, |
412 | so it will generate false positives. Be careful not change text like | |
413 | "this was fixed in 5.10.0"! | |
ceb7f800 | 414 | |
8b2227e6 | 415 | Use git status and git diff to select changes you want to keep. |
ceb7f800 | 416 | |
f6af4394 DM |
417 | Be particularly careful with F<INSTALL>, which contains a mixture of |
418 | C<5.10.0>-type strings, some of which need bumping on every release, and | |
e03f126c | 419 | some of which need to be left unchanged. |
2f05d209 | 420 | See below in L<"update INSTALL"> for more details. |
e03f126c | 421 | |
cdf175f7 SH |
422 | For the first RC release leading up to a BLEAD-FINAL release, update the |
423 | description of which releases are now "officially" supported in | |
424 | F<pod/perlpolicy.pod>. | |
425 | ||
6a958a95 DM |
426 | When doing a BLEAD-POINT or BLEAD-FINAL release, also make sure the |
427 | C<PERL_API_*> constants in F<patchlevel.h> are in sync with the version | |
ac2aec01 SH |
428 | you're releasing, unless you're absolutely sure the release you're about to |
429 | make is 100% binary compatible to an earlier release. When releasing a MAINT | |
430 | perl version, the C<PERL_API_*> constants C<MUST NOT> be changed as we aim | |
431 | to guarantee binary compatibility in maint branches. | |
45ce9531 | 432 | |
17163f85 DM |
433 | After editing, regenerate uconfig.h (this must be run on a system with a |
434 | /bin/sh available): | |
22be9667 | 435 | |
f185f654 | 436 | $ perl regen/uconfig_h.pl |
22be9667 | 437 | |
78957677 JL |
438 | This might not cause any new changes. |
439 | ||
82ce0493 A |
440 | You may also need to regen opcodes: |
441 | ||
f185f654 | 442 | $ ./perl -Ilib regen/opcode.pl |
82ce0493 | 443 | |
22be9667 JV |
444 | Test your changes: |
445 | ||
f185f654 KW |
446 | $ git clean -xdf # careful if you don't have local files to keep! |
447 | $ ./Configure -des -Dusedevel | |
448 | $ make | |
449 | $ make test | |
22be9667 | 450 | |
2c1c14b5 A |
451 | Do note that at this stage, porting tests will fail. They will continue |
452 | to fail until you've updated Module::CoreList, as described below. | |
453 | ||
54356a6f JV |
454 | Commit your changes: |
455 | ||
f185f654 KW |
456 | $ git status |
457 | $ git diff | |
458 | B<review the delta carefully> | |
54356a6f | 459 | |
f185f654 | 460 | $ git commit -a -m 'Bump the perl version in various places for 5.x.y' |
dc0a62a1 | 461 | |
21768cb3 | 462 | At this point you may want to compare the commit with a previous bump to |
ac2aec01 | 463 | see if they look similar. See commit f7cf42bb69 for an example of a |
21768cb3 FC |
464 | previous version bump. |
465 | ||
dc0a4df9 DM |
466 | When the version number is bumped, you should also update Module::CoreList |
467 | (as described below in L<"update Module::CoreList">) to reflect the new | |
81fc59ef DG |
468 | version number. |
469 | ||
dc0a4df9 | 470 | =head3 update INSTALL |
dc0a62a1 | 471 | |
2f05d209 SH |
472 | Review and update INSTALL to account for the change in version number. |
473 | The lines in F<INSTALL> about "is not binary compatible with" may require a | |
474 | correct choice of earlier version to declare incompatibility with. These are | |
475 | in the "Changes and Incompatibilities" and "Coexistence with earlier versions | |
476 | of perl 5" sections. | |
dc0a62a1 | 477 | |
6a958a95 DM |
478 | Be particularly careful with the section "Upgrading from 5.X.Y or earlier". |
479 | The "X.Y" needs to be changed to the most recent version that we are | |
480 | I<not> binary compatible with. | |
481 | ||
482 | For MAINT and BLEAD-FINAL releases, this needs to refer to the last | |
483 | release in the previous development cycle (so for example, for a 5.14.x | |
484 | release, this would be 5.13.11). | |
485 | ||
486 | For BLEAD-POINT releases, it needs to refer to the previous BLEAD-POINT | |
96644a2c DG |
487 | release (so for 5.15.3 this would be 5.15.2). If the last release manager |
488 | followed instructions, this should have already been done after the last | |
489 | blead release, so you may find nothing to do here. | |
6a958a95 | 490 | |
52d097d9 S |
491 | =head3 Check copyright years |
492 | ||
493 | Check that the copyright years are up to date by running: | |
494 | ||
78a62309 | 495 | $ ./perl t/porting/copyright.t --now |
52d097d9 S |
496 | |
497 | Remedy any test failures by editing README or perl.c accordingly (search for | |
498 | the "Copyright"). If updating perl.c, check if the file's own copyright date in | |
499 | the C comment at the top needs updating, as well as the one printed by C<-v>. | |
500 | ||
dc0a4df9 | 501 | =head3 Check more build configurations |
b82efa27 | 502 | |
d8fc5aa0 DR |
503 | Try running the full test suite against multiple Perl configurations. Here are |
504 | some sets of Configure flags you can try: | |
52a66c2c | 505 | |
d8fc5aa0 | 506 | =over 4 |
7277a900 | 507 | |
d8fc5aa0 DR |
508 | =item * |
509 | ||
510 | C<-Duseshrplib -Dusesitecustomize> | |
511 | ||
512 | =item * | |
513 | ||
514 | C<-Duserelocatableinc> | |
515 | ||
516 | =item * | |
517 | ||
518 | C<-Dusethreads> | |
519 | ||
520 | =back | |
7277a900 | 521 | |
d8fc5aa0 DR |
522 | If you have multiple compilers on your machine, you might also consider |
523 | compiling with C<-Dcc=$other_compiler>. | |
dc0a4df9 DM |
524 | |
525 | =head3 update perlport | |
7277a900 | 526 | |
347f5124 RGS |
527 | L<perlport> has a section currently named I<Supported Platforms> that |
528 | indicates which platforms are known to build in the current release. | |
529 | If necessary update the list and the indicated version number. | |
530 | ||
1dbf7599 DG |
531 | =head3 check a readonly build |
532 | ||
533 | Even before other prep work, follow the steps in L<build the tarball> and test | |
534 | it locally. Because a perl source tarballs sets many files read-only, it could | |
535 | test differently than tests run from the repository. After you're sure | |
536 | permissions aren't a problem, delete the generated directory and tarballs. | |
6a958a95 | 537 | |
2e831dfd DM |
538 | =head2 Building a release - on the day |
539 | ||
b1288acc | 540 | This section describes the actions required to make a release |
f6b1864d | 541 | that are performed near to, or on the actual release day. |
2e831dfd | 542 | |
dc0a4df9 | 543 | =head3 re-check earlier actions |
2e831dfd | 544 | |
dc0a4df9 | 545 | Review all the actions in the previous section, |
2e831dfd DM |
546 | L<"Building a release - advance actions"> to ensure they are all done and |
547 | up-to-date. | |
548 | ||
ff721450 JL |
549 | =head3 create a release branch |
550 | ||
551 | For BLEAD-POINT releases, making a release from a release branch avoids the | |
552 | need to freeze blead during the release. This is less important for | |
553 | BLEAD-FINAL, MAINT, and RC releases, since blead will already be frozen in | |
554 | those cases. Create the branch by running | |
555 | ||
78a62309 | 556 | git checkout -b release-5.xx.yy |
ff721450 | 557 | |
dc0a4df9 | 558 | =head3 build a clean perl |
8c35d285 | 559 | |
1dbf7599 | 560 | Make sure you have a gitwise-clean perl directory (no modified files, |
a0db33fe | 561 | unpushed commits etc): |
8c35d285 | 562 | |
a0db33fe | 563 | $ git status |
24c5e187 | 564 | $ git clean -dxf |
8c35d285 | 565 | |
dc0a4df9 | 566 | then configure and build perl so that you have a Makefile and porting tools: |
8c35d285 | 567 | |
52a66c2c | 568 | $ ./Configure -Dusedevel -des && make |
8c35d285 | 569 | |
a8ec9917 SH |
570 | =head3 Check module versions |
571 | ||
572 | For each Perl release since the previous release of the current branch, check | |
573 | for modules that have identical version numbers but different contents by | |
574 | running: | |
575 | ||
e89d87cc | 576 | $ ./perl -Ilib Porting/cmpVERSION.pl --tag=v5.X.YY |
a8ec9917 SH |
577 | |
578 | (This is done automatically by F<t/porting/cmp_version.t> for the previous | |
579 | release of the current branch, but not for any releases from other branches.) | |
580 | ||
581 | Any modules that fail will need a version bump, plus a nudge to the upstream | |
582 | maintainer for 'cpan' upstream modules. | |
583 | ||
dc0a4df9 | 584 | =head3 update Module::CoreList |
8c35d285 | 585 | |
0429cb0e SH |
586 | =head4 Bump Module::CoreList* $VERSIONs |
587 | ||
78a62309 SH |
588 | If necessary, bump C<$Module::CoreList::VERSION> (there's no need to do this |
589 | for every RC; in RC1, bump the version to a new clean number that will | |
0429cb0e SH |
590 | appear in the final release, and leave as-is for the later RCs and final). |
591 | It may also happen that C<Module::CoreList> has been modified in blead, and | |
592 | hence has a new version number already. (But make sure it is not the same | |
593 | number as a CPAN release.) | |
594 | ||
595 | C<$Module::CoreList::TieHashDelta::VERSION> and | |
596 | C<$Module::CoreList::Utils::VERSION> should always be equal to | |
597 | C<$Module::CoreList::VERSION>. If necessary, bump those two versions to match | |
598 | before proceeding. | |
599 | ||
77087aae AC |
600 | The files to modify are: |
601 | ||
602 | =over 4 | |
603 | ||
604 | =item * | |
605 | ||
606 | F<dist/Module-CoreList/lib/Module/CoreList.pm> | |
607 | ||
608 | =item * | |
609 | ||
610 | F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm> | |
611 | ||
612 | =item * | |
613 | ||
614 | F<dist/Module-CoreList/lib/Module/CoreList/TieHashDelta.pm> | |
615 | ||
616 | =back | |
94691c19 | 617 | |
0429cb0e | 618 | =head4 Update C<Module::CoreList> with module version data for the new release. |
bfadf2ba | 619 | |
6a958a95 | 620 | Note that if this is a MAINT release, you should run the following actions |
1bac61bb | 621 | from the maint branch, but commit the C<CoreList.pm> changes in |
a9d1f3db LB |
622 | I<blead> and subsequently cherry-pick any releases since the last |
623 | maint release and then your recent commit. XXX need a better example | |
bfadf2ba | 624 | |
89781932 DM |
625 | [ Note that the procedure for handling Module::CoreList in maint branches |
626 | is a bit complex, and the RMG currently don't describe a full and | |
627 | workable approach. The main issue is keeping Module::CoreList | |
628 | and its version number synchronised across all maint branches, blead and | |
629 | CPAN, while having to bump its version number for every RC release. | |
630 | See this brief p5p thread: | |
631 | ||
632 | Message-ID: <20130311174402.GZ2294@iabyn.com> | |
633 | ||
634 | If you can devise a workable system, feel free to try it out, and to | |
38e4b857 | 635 | update the RMG accordingly! |
89781932 DM |
636 | |
637 | DAPM May 2013 ] | |
638 | ||
a0db33fe | 639 | F<corelist.pl> uses ftp.funet.fi to verify information about dual-lived |
218a07e7 SH |
640 | modules on CPAN. It can use a full, local CPAN mirror and/or fall back |
641 | on HTTP::Tiny to fetch package metadata remotely. | |
bfadf2ba | 642 | |
fdaa3f94 | 643 | (If you'd prefer to have a full CPAN mirror, see |
bfadf2ba JV |
644 | http://www.cpan.org/misc/cpan-faq.html#How_mirror_CPAN) |
645 | ||
a0db33fe | 646 | Then change to your perl checkout, and if necessary, |
bfadf2ba | 647 | |
595f83ae | 648 | $ make |
bfadf2ba | 649 | |
bf8ea215 | 650 | Then, If you have a local CPAN mirror, run: |
bfadf2ba | 651 | |
bfadf2ba JV |
652 | $ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror |
653 | ||
654 | Otherwise, run: | |
655 | ||
bfadf2ba JV |
656 | $ ./perl -Ilib Porting/corelist.pl cpan |
657 | ||
52a66c2c | 658 | This will chug for a while, possibly reporting various warnings about |
2a720090 | 659 | badly-indexed CPAN modules unrelated to the modules actually in core. |
2ce7d676 | 660 | Assuming all goes well, it will update |
ab0bff1f | 661 | F<dist/Module-CoreList/lib/Module/CoreList.pm> and possibly |
244e6e4e | 662 | F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm>. |
bfadf2ba | 663 | |
ab0bff1f | 664 | Check those files over carefully: |
bfadf2ba | 665 | |
d5bddf6e | 666 | $ git diff dist/Module-CoreList/lib/Module/CoreList.pm |
244e6e4e | 667 | $ git diff dist/Module-CoreList/lib/Module/CoreList/Utils.pm |
1dbf7599 | 668 | |
00c28750 DR |
669 | =head4 Bump version in Module::CoreList F<Changes> |
670 | ||
0429cb0e | 671 | Also edit Module::CoreList's new version number in its F<Changes> file. |
f8804d60 | 672 | This file is F<dist/Module-CoreList/Changes>. |
e8c01f92 | 673 | |
00c28750 DR |
674 | =head4 Add Module::CoreList version bump to perldelta |
675 | ||
14071f95 MH |
676 | Add a perldelta entry for the new Module::CoreList version. You only |
677 | need to do this if you want to add notes about the changes included | |
678 | with this version of Module::CoreList. Otherwise, its version bump | |
679 | will be automatically filled in below in L<finalize perldelta>. | |
70855f8b | 680 | |
da571fa1 DR |
681 | =for checklist skip RC |
682 | ||
09abf5f8 | 683 | =head4 Update C<%Module::CoreList::released> |
da571fa1 | 684 | |
09abf5f8 SH |
685 | For any release except an RC: Update this version's entry in the C<%released> |
686 | hash with today's date. | |
bfadf2ba | 687 | |
00c28750 DR |
688 | =head4 Commit Module::CoreList changes |
689 | ||
bfadf2ba | 690 | Finally, commit the new version of Module::CoreList: |
6a958a95 | 691 | (unless this is for MAINT; in which case commit it to blead first, then |
a0db33fe | 692 | cherry-pick it back). |
bfadf2ba | 693 | |
78a62309 SH |
694 | $ git commit -m 'Update Module::CoreList for 5.x.y' \ |
695 | dist/Module-CoreList/Changes \ | |
696 | dist/Module-CoreList/lib/Module/CoreList.pm \ | |
697 | dist/Module-CoreList/lib/Module/CoreList/Utils.pm | |
bfadf2ba | 698 | |
1dbf7599 DG |
699 | =head4 Rebuild and test |
700 | ||
78a62309 SH |
701 | Build and test to get the changes into the currently built lib directory and to |
702 | ensure all tests are passing. | |
1dbf7599 DG |
703 | |
704 | =head3 finalize perldelta | |
705 | ||
706 | Finalize the perldelta. In particular, fill in the Acknowledgements | |
707 | section, which can be generated with something like: | |
708 | ||
78a62309 | 709 | $ perl Porting/acknowledgements.pl v5.15.0..HEAD |
1dbf7599 | 710 | |
78a62309 SH |
711 | Fill in the "New/Updated Modules" sections now that Module::CoreList is |
712 | updated: | |
2c5d738b | 713 | |
78a62309 SH |
714 | $ ./perl -Ilib Porting/corelist-perldelta.pl \ |
715 | --mode=update pod/perldelta.pod | |
be2822b0 SH |
716 | |
717 | For a MAINT release use something like this instead: | |
718 | ||
78a62309 SH |
719 | $ ./perl -Ilib Porting/corelist-perldelta.pl 5.020001 5.020002 \ |
720 | --mode=update pod/perldelta.pod | |
2c5d738b SH |
721 | |
722 | Ideally, also fill in a summary of the major changes to each module for which | |
723 | an entry has been added by F<corelist-perldelta.pl>. | |
1dbf7599 DG |
724 | |
725 | Re-read the perldelta to try to find any embarrassing typos and thinkos; | |
726 | remove any C<TODO> or C<XXX> flags; update the "Known Problems" section | |
727 | with any serious issues for which fixes are not going to happen now; and | |
728 | run through pod and spell checkers, e.g. | |
729 | ||
730 | $ podchecker -warnings -warnings pod/perldelta.pod | |
731 | $ spell pod/perldelta.pod | |
732 | ||
733 | Also, you may want to generate and view an HTML version of it to check | |
734 | formatting, e.g. | |
735 | ||
78a62309 SH |
736 | $ ./perl -Ilib ext/Pod-Html/bin/pod2html pod/perldelta.pod > \ |
737 | /tmp/perldelta.html | |
1dbf7599 DG |
738 | |
739 | Another good HTML preview option is http://search.cpan.org/pod2html | |
740 | ||
741 | If you make changes, be sure to commit them. | |
742 | ||
743 | =for checklist skip BLEAD-POINT MAINT RC | |
744 | ||
745 | =head3 remove stale perldeltas | |
746 | ||
747 | For the first RC release that is ONLY for a BLEAD-FINAL, the perldeltas | |
1f6591ac | 748 | from the BLEAD-POINT releases since the previous BLEAD-FINAL should have |
1dbf7599 DG |
749 | now been consolidated into the current perldelta, and hence are now just |
750 | useless clutter. They can be removed using: | |
751 | ||
752 | $ git rm <file1> <file2> ... | |
753 | ||
754 | For example, for RC0 of 5.16.0: | |
755 | ||
756 | $ cd pod | |
757 | $ git rm perldelta515*.pod | |
758 | ||
1f6591ac | 759 | =for checklist skip BLEAD-FINAL BLEAD-POINT |
1dbf7599 DG |
760 | |
761 | =head3 add recent perldeltas | |
762 | ||
763 | For the first RC for a MAINT release, copy in any recent perldeltas from | |
764 | blead that have been added since the last release on this branch. This | |
765 | should include any recent maint releases on branches older than your one, | |
766 | but not newer. For example if you're producing a 5.14.x release, copy any | |
767 | perldeltas from recent 5.10.x, 5.12.x etc maint releases, but not from | |
768 | 5.16.x or higher. Remember to | |
769 | ||
770 | $ git add <file1> <file2> ... | |
771 | ||
772 | =head3 update and commit perldelta files | |
773 | ||
774 | If you have added or removed any perldelta files via the previous two | |
775 | steps, then edit F<pod/perl.pod> to add/remove them from its table of | |
776 | contents, then run F<Porting/pod_rules.pl> to propagate your changes there | |
777 | into all the other files that mention them (including F<MANIFEST>). You'll | |
778 | need to C<git add> the files that it changes. | |
779 | ||
780 | Then build a clean perl and do a full test | |
781 | ||
782 | $ git status | |
783 | $ git clean -dxf | |
784 | $ ./Configure -Dusedevel -des | |
785 | $ make | |
786 | $ make test | |
787 | ||
788 | Once all tests pass, commit your changes. | |
789 | ||
790 | =head3 build a clean perl | |
791 | ||
792 | If you skipped the previous step (adding/removing perldeltas), | |
793 | again, make sure you have a gitwise-clean perl directory (no modified files, | |
794 | unpushed commits etc): | |
795 | ||
796 | $ git status | |
797 | $ git clean -dxf | |
798 | ||
799 | then configure and build perl so that you have a Makefile and porting tools: | |
800 | ||
801 | $ ./Configure -Dusedevel -des && make | |
802 | ||
1f6591ac | 803 | =for checklist skip BLEAD-FINAL BLEAD-POINT |
80dd5f25 DM |
804 | |
805 | =head3 synchronise from blead's perlhist.pod | |
806 | ||
807 | For the first RC for a MAINT release, copy in the latest | |
808 | F<pod/perlhist.pod> from blead; this will include details of newer | |
809 | releases in all branches. In theory, blead's version should be a strict | |
c26b8729 AC |
810 | superset of the one in this branch, but it's probably safest to examine the |
811 | changes first, to ensure that there's nothing in this branch that was | |
812 | forgotten from blead. An easy way to do that is with C<< git checkout -p >>, | |
813 | to selectively apply any changes from the blead version to your current | |
814 | branch: | |
815 | ||
816 | $ git fetch origin | |
817 | $ git checkout -p origin/blead pod/perlhist.pod | |
80dd5f25 DM |
818 | $ git commit -m 'sync perlhist from blead' pod/perlhist.pod |
819 | ||
dc0a4df9 | 820 | =head3 update perlhist.pod |
a0db33fe | 821 | |
e8a7a70e JV |
822 | Add an entry to F<pod/perlhist.pod> with the release date, e.g.: |
823 | ||
824 | David 5.10.1 2009-Aug-06 | |
a0db33fe | 825 | |
a420fd35 MH |
826 | List yourself in the left-hand column, and if this is the first release |
827 | that you've ever done, make sure that your name is listed in the section | |
828 | entitled C<THE KEEPERS OF THE PUMPKIN>. | |
a0db33fe | 829 | |
56e2d9fb | 830 | I<If you're making a BLEAD-FINAL release>, also update the "SELECTED |
bd4ce907 RS |
831 | RELEASE SIZES" section with the output of |
832 | F<Porting/perlhist_calculate.pl>. | |
833 | ||
a0db33fe DM |
834 | Be sure to commit your changes: |
835 | ||
836 | $ git commit -m 'add new release to perlhist' pod/perlhist.pod | |
8c35d285 | 837 | |
da571fa1 | 838 | =for checklist skip BLEAD-POINT |
dc0a4df9 DM |
839 | |
840 | =head3 update patchlevel.h | |
8c35d285 | 841 | |
6a958a95 | 842 | I<You MUST SKIP this step for a BLEAD-POINT release> |
d7eb1120 | 843 | |
a42352ee DM |
844 | Update F<patchlevel.h> to add a C<-RC1>-or-whatever string; or, if this is |
845 | a final release, remove it. For example: | |
d7eb1120 DM |
846 | |
847 | static const char * const local_patches[] = { | |
848 | NULL | |
849 | + ,"RC1" | |
0bf51988 SH |
850 | #ifdef PERL_GIT_UNCOMMITTED_CHANGES |
851 | ,"uncommitted-changes" | |
852 | #endif | |
d7eb1120 DM |
853 | |
854 | Be sure to commit your change: | |
855 | ||
856 | $ git commit -m 'bump version to RCnnn' patchlevel.h | |
857 | ||
4612967b CBW |
858 | =head3 run makemeta to update META files |
859 | ||
e4fbed99 | 860 | $ ./perl -Ilib Porting/makemeta |
4612967b CBW |
861 | |
862 | Be sure to commit any changes (if applicable): | |
863 | ||
e4fbed99 | 864 | $ git status # any changes? |
4612967b | 865 | $ git commit -m 'Update META files' META.* |
dc0a4df9 DM |
866 | |
867 | =head3 build, test and check a fresh perl | |
d7eb1120 | 868 | |
a0db33fe DM |
869 | Build perl, then make sure it passes its own test suite, and installs: |
870 | ||
871 | $ git clean -xdf | |
a42352ee DM |
872 | $ ./Configure -des -Dprefix=/tmp/perl-5.x.y-pretest |
873 | ||
874 | # or if it's an odd-numbered version: | |
a0db33fe | 875 | $ ./Configure -des -Dusedevel -Dprefix=/tmp/perl-5.x.y-pretest |
a42352ee | 876 | |
a0db33fe DM |
877 | $ make test install |
878 | ||
52a66c2c DM |
879 | Check that the output of C</tmp/perl-5.x.y-pretest/bin/perl -v> and |
880 | C</tmp/perl-5.x.y-pretest/bin/perl -V> are as expected, | |
a0db33fe | 881 | especially as regards version numbers, patch and/or RC levels, and @INC |
c5fb089a | 882 | paths. Note that as they have been built from a git working |
52a66c2c | 883 | directory, they will still identify themselves using git tags and |
01725c10 A |
884 | commits. (Note that for an odd-numbered version, perl will install |
885 | itself as C<perl5.x.y>). C<perl -v> will identify itself as: | |
886 | ||
f185f654 | 887 | This is perl 5, version X, subversion Y (v5.X.Y (v5.X.Z-NNN-gdeadbeef)) |
01725c10 | 888 | |
78957677 | 889 | where 5.X.Z is the latest tag, NNN the number of commits since this tag, |
01725c10 | 890 | and C<< deadbeef >> commit of that tag. |
52a66c2c DM |
891 | |
892 | Then delete the temporary installation. | |
893 | ||
c90225ed | 894 | =head3 create the release tag |
dc0a4df9 | 895 | |
c90225ed | 896 | Create the tag identifying this release (e.g.): |
96054f12 | 897 | |
b6d23947 | 898 | $ git tag v5.11.0 -m "First release of the v5.11 series!" |
e8c01f92 | 899 | |
6a958a95 | 900 | It is B<VERY> important that from this point forward, you not push |
f662f3b7 JV |
901 | your git changes to the Perl master repository. If anything goes |
902 | wrong before you publish your newly-created tag, you can delete | |
903 | and recreate it. Once you push your tag, we're stuck with it | |
904 | and you'll need to use a new version number for your release. | |
905 | ||
dc0a4df9 | 906 | =head3 build the tarball |
a0db33fe | 907 | |
0dcf3caa | 908 | Before you run the following, you might want to install 7-Zip (the |
0dcb816b | 909 | C<p7zip-full> package under Debian or the C<p7zip> port on MacPorts) or |
0dcf3caa LB |
910 | the AdvanceCOMP suite (e.g. the C<advancecomp> package under Debian, |
911 | or the C<advancecomp> port on macports - 7-Zip on Windows is the | |
912 | same code as AdvanceCOMP, so Windows users get the smallest files | |
913 | first time). These compress about 5% smaller than gzip and bzip2. | |
914 | Over the lifetime of your distribution this will save a lot of | |
915 | people a small amount of download time and disk space, which adds | |
916 | up. | |
917 | ||
2174049d CBW |
918 | In order to produce the C<xz> tarball, XZ Utils are required. The C<xz> |
919 | utility is included with most modern UNIX-type operating systems and | |
920 | is available for Cygwin. A Windows port is available from | |
921 | L<http://tukaani.org/xz/>. | |
922 | ||
96644a2c DG |
923 | B<IMPORTANT>: if you are on OS X, you must export C<COPYFILE_DISABLE=1> |
924 | to prevent OS X resource files from being included in your tarball. After | |
925 | creating the tarball following the instructions below, inspect it to ensure | |
926 | you don't have files like F<._foobar>. | |
927 | ||
8c35d285 JV |
928 | Create a tarball. Use the C<-s> option to specify a suitable suffix for |
929 | the tarball and directory name: | |
930 | ||
f185f654 KW |
931 | $ cd root/of/perl/tree |
932 | $ make distclean # make sure distclean works | |
933 | $ git clean -xdf # make sure perl and git agree on files | |
934 | # git clean should not output anything! | |
935 | $ git status # and there's nothing lying around | |
8c35d285 | 936 | |
f185f654 KW |
937 | $ perl Porting/makerel -bx -s RC1 # for a release candidate |
938 | $ perl Porting/makerel -bx # for the release itself | |
8c35d285 JV |
939 | |
940 | This creates the directory F<../perl-x.y.z-RC1> or similar, copies all | |
ac2aec01 SH |
941 | the MANIFEST files into it, sets the correct permissions on them, then |
942 | tars it up as F<../perl-x.y.z-RC1.tar.gz>. With C<-b>, it also creates a | |
2174049d | 943 | C<tar.bz2> file. The C<-x> also produces a C<tar.xz> file. |
8c35d285 | 944 | |
6480287f MT |
945 | If you're getting your tarball suffixed with -uncommitted and you're sure |
946 | your changes were all committed, you can override the suffix with: | |
947 | ||
948 | $ perl Porting/makerel -b -s '' | |
96054f12 | 949 | |
8c35d285 JV |
950 | XXX if we go for extra tags and branches stuff, then add the extra details |
951 | here | |
952 | ||
dc0a4df9 | 953 | Finally, clean up the temporary directory, e.g. |
a42352ee DM |
954 | |
955 | $ rm -rf ../perl-x.y.z-RC1 | |
956 | ||
dc0a4df9 DM |
957 | =head3 test the tarball |
958 | ||
00c28750 | 959 | Once you have a tarball it's time to test the tarball (not the repository). |
dc0a4df9 | 960 | |
00c28750 | 961 | =head4 Copy the tarball to a web server |
a42352ee | 962 | |
2174049d | 963 | Copy the tarballs (.gz and possibly .bz2 and .xz) to a web server somewhere you |
8c35d285 JV |
964 | have access to. |
965 | ||
96644a2c | 966 | =head4 Download the tarball to another machine and unpack it |
8c35d285 | 967 | |
fdaa3f94 | 968 | Download the tarball to some other machine. For a release candidate, |
8c35d285 | 969 | you really want to test your tarball on two or more different platforms |
96644a2c DG |
970 | and architectures. |
971 | ||
972 | =head4 Ask #p5p to test the tarball on different platforms | |
973 | ||
974 | Once you've verified the tarball can be downloaded and unpacked, | |
975 | ask the #p5p IRC channel on irc.perl.org for volunteers to test the | |
976 | tarballs on whatever platforms they can. | |
977 | ||
978 | If you're not confident in the tarball, you can defer this step until after | |
979 | your own tarball testing, below. | |
8c35d285 | 980 | |
00c28750 | 981 | =head4 Check that F<Configure> works |
8c35d285 JV |
982 | |
983 | Check that basic configuration and tests work on each test machine: | |
984 | ||
e07c44df MH |
985 | $ ./Configure -des && make all test |
986 | ||
987 | # Or for a development release: | |
bf8aad21 | 988 | $ ./Configure -Dusedevel -des && make all test |
f6af4394 | 989 | |
00c28750 | 990 | =head4 Run the test harness and install |
f6af4394 | 991 | |
8c35d285 JV |
992 | Check that the test harness and install work on each test machine: |
993 | ||
f185f654 KW |
994 | $ make distclean |
995 | $ ./Configure -des -Dprefix=/install/path && make all test_harness install | |
996 | $ cd /install/path | |
8c35d285 | 997 | |
00c28750 | 998 | =head4 Check C<perl -v> and C<perl -V> |
8c35d285 JV |
999 | |
1000 | Check that the output of C<perl -v> and C<perl -V> are as expected, | |
1001 | especially as regards version numbers, patch and/or RC levels, and @INC | |
fdaa3f94 | 1002 | paths. |
8c35d285 JV |
1003 | |
1004 | Note that the results may be different without a F<.git/> directory, | |
1005 | which is why you should test from the tarball. | |
1006 | ||
00c28750 | 1007 | =head4 Run the Installation Verification Procedure utility |
459fc3ca | 1008 | |
9651cacc | 1009 | $ ./perl utils/perlivp |
459fc3ca DM |
1010 | ... |
1011 | All tests successful. | |
1012 | $ | |
1013 | ||
00c28750 | 1014 | =head4 Compare the installed paths to the last release |
459fc3ca | 1015 | |
d60a1044 DM |
1016 | Compare the pathnames of all installed files with those of the previous |
1017 | release (i.e. against the last installed tarball on this branch which you | |
1018 | have previously verified using this same procedure). In particular, look | |
1019 | for files in the wrong place, or files no longer included which should be. | |
1020 | For example, suppose the about-to-be-released version is 5.10.1 and the | |
1021 | previous is 5.10.0: | |
1022 | ||
1023 | cd installdir-5.10.0/ | |
1024 | find . -type f | perl -pe's/5\.10\.0/5.10.1/g' | sort > /tmp/f1 | |
1025 | cd installdir-5.10.1/ | |
1026 | find . -type f | sort > /tmp/f2 | |
1027 | diff -u /tmp/f[12] | |
1028 | ||
29205e9c | 1029 | =head4 Bootstrap the CPAN client |
d60a1044 | 1030 | |
8c35d285 JV |
1031 | Bootstrap the CPAN client on the clean install: |
1032 | ||
29205e9c | 1033 | $ bin/cpan |
8c35d285 | 1034 | |
61a1ab54 MH |
1035 | # Or, perhaps: |
1036 | $ bin/cpan5.xx.x | |
1037 | ||
29205e9c | 1038 | =head4 Install the Inline module with CPAN and test it |
8c35d285 | 1039 | |
a42352ee DM |
1040 | Try installing a popular CPAN module that's reasonably complex and that |
1041 | has dependencies; for example: | |
8c35d285 | 1042 | |
65651c62 | 1043 | CPAN> install Inline::C |
a42352ee | 1044 | CPAN> quit |
8c35d285 JV |
1045 | |
1046 | Check that your perl can run this: | |
1047 | ||
16c60e4e | 1048 | $ bin/perl -lwe "use Inline C => q[int f() { return 42;}]; print f" |
a42352ee DM |
1049 | 42 |
1050 | $ | |
8c35d285 | 1051 | |
00c28750 | 1052 | =head4 Make sure that perlbug works |
8c35d285 | 1053 | |
00c28750 | 1054 | Test L<perlbug> with the following: |
47b1f096 | 1055 | |
a14438df | 1056 | $ bin/perlbug |
47b1f096 DM |
1057 | ... |
1058 | Subject: test bug report | |
fdaa3f94 CBW |
1059 | Local perl administrator [yourself]: |
1060 | Editor [vi]: | |
1061 | Module: | |
1062 | Category [core]: | |
1063 | Severity [low]: | |
47b1f096 DM |
1064 | (edit report) |
1065 | Action (Send/Display/Edit/Subject/Save to File): f | |
fdaa3f94 | 1066 | Name of file to save message in [perlbug.rep]: |
47b1f096 DM |
1067 | Action (Send/Display/Edit/Subject/Save to File): q |
1068 | ||
1069 | and carefully examine the output (in F<perlbug.rep]>), especially | |
1070 | the "Locally applied patches" section. If everything appears okay, then | |
75a012fe DM |
1071 | delete the file, and try it again, this time actually submitting the bug |
1072 | report. Check that it shows up, then remember to close it! | |
47b1f096 | 1073 | |
da571fa1 | 1074 | =for checklist skip BLEAD-POINT |
dc0a4df9 DM |
1075 | |
1076 | =head3 monitor smokes | |
47b1f096 | 1077 | |
1dbf7599 DG |
1078 | XXX This is probably irrelevant if working on a release branch, though |
1079 | MAINT or RC might want to push a smoke branch and wait. | |
1080 | ||
f6af4394 DM |
1081 | Wait for the smoke tests to catch up with the commit which this release is |
1082 | based on (or at least the last commit of any consequence). | |
7277a900 | 1083 | |
f6af4394 DM |
1084 | Then check that the smoke tests pass (particularly on Win32). If not, go |
1085 | back and fix things. | |
7277a900 | 1086 | |
6a958a95 | 1087 | Note that for I<BLEAD-POINT> releases this may not be practical. It takes a |
1eefd7d5 | 1088 | long time for the smokers to catch up, especially the Win32 |
6a958a95 DM |
1089 | smokers. This is why we have a RC cycle for I<MAINT> and I<BLEAD-FINAL> |
1090 | releases, but for I<BLEAD-POINT> releases sometimes the best you can do is | |
1091 | to plead with people on IRC to test stuff on their platforms, fire away, | |
1092 | and then hope for the best. | |
7277a900 | 1093 | |
dc0a4df9 | 1094 | =head3 upload to PAUSE |
7277a900 | 1095 | |
f6af4394 | 1096 | Once smoking is okay, upload it to PAUSE. This is the point of no return. |
db3f805e JV |
1097 | If anything goes wrong after this point, you will need to re-prepare |
1098 | a new release with a new minor version or RC number. | |
1099 | ||
a14438df DM |
1100 | https://pause.perl.org/ |
1101 | ||
1102 | (Login, then select 'Upload a file to CPAN') | |
1103 | ||
45924287 RS |
1104 | If your workstation is not connected to a high-bandwidth, |
1105 | high-reliability connection to the Internet, you should probably use the | |
1106 | "GET URL" feature (rather than "HTTP UPLOAD") to have PAUSE retrieve the | |
1107 | new release from wherever you put it for testers to find it. This will | |
1108 | eliminate anxious gnashing of teeth while you wait to see if your | |
1109 | 15 megabyte HTTP upload successfully completes across your slow, twitchy | |
96644a2c DG |
1110 | cable modem. |
1111 | ||
96644a2c | 1112 | You can make use of your home directory on dromedary for |
c27b4e97 SH |
1113 | this purpose: F<http://users.perl5.git.perl.org/~USERNAME> maps to |
1114 | F</home/USERNAME/public_html>, where F<USERNAME> is your login account | |
96644a2c DG |
1115 | on dromedary. |
1116 | ||
1117 | I<Remember>: if your upload is partially successful, you | |
c27b4e97 | 1118 | may need to contact a PAUSE administrator or even bump the version of perl. |
45924287 | 1119 | |
5cd8f091 | 1120 | Upload the .gz, .xz, and .bz2 versions of the tarball. |
f6af4394 | 1121 | |
1dbf7599 DG |
1122 | Do not proceed any further until you are sure that your tarballs are on CPAN. |
1123 | Check your authors directory www.cpan.org (the globally balanced "fast" | |
1124 | mirror) to confirm that your uploads have been successful. | |
c27b4e97 | 1125 | |
1dbf7599 | 1126 | =for checklist skip RC BLEAD-POINT |
00c28750 DR |
1127 | |
1128 | =head3 wait for indexing | |
1129 | ||
1dbf7599 | 1130 | I<You MUST SKIP this step for RC and BLEAD-POINT> |
76526317 FR |
1131 | |
1132 | Wait until you receive notification emails from the PAUSE indexer | |
1133 | confirming that your uploads have been received. IMPORTANT -- you will | |
1134 | probably get an email that indexing has failed, due to module permissions. | |
1135 | This is considered normal. | |
1136 | ||
da571fa1 | 1137 | =for checklist skip BLEAD-POINT |
dc0a4df9 DM |
1138 | |
1139 | =head3 disarm patchlevel.h | |
f6af4394 | 1140 | |
6a958a95 | 1141 | I<You MUST SKIP this step for BLEAD-POINT release> |
113f3f4c | 1142 | |
a42352ee | 1143 | Disarm the F<patchlevel.h> change; for example, |
d7eb1120 DM |
1144 | |
1145 | static const char * const local_patches[] = { | |
1146 | NULL | |
1147 | - ,"RC1" | |
0bf51988 SH |
1148 | #ifdef PERL_GIT_UNCOMMITTED_CHANGES |
1149 | ,"uncommitted-changes" | |
1150 | #endif | |
d7eb1120 DM |
1151 | |
1152 | Be sure to commit your change: | |
1153 | ||
1154 | $ git commit -m 'disarm RCnnn bump' patchlevel.h | |
dc0a4df9 DM |
1155 | |
1156 | =head3 announce to p5p | |
2e831dfd | 1157 | |
db3f805e | 1158 | Mail p5p to announce your new release, with a quote you prepared earlier. |
f6af4394 | 1159 | |
098d30ef | 1160 | Use the template at Porting/release_announcement_template.txt |
dc0a4df9 | 1161 | |
a8cecd9d RS |
1162 | Send a carbon copy to C<noc@metacpan.org> |
1163 | ||
ff721450 JL |
1164 | =head3 merge release branch back to blead |
1165 | ||
c90225ed | 1166 | Merge the (local) release branch back into master now, and delete it. |
ff721450 | 1167 | |
78a62309 SH |
1168 | git checkout blead |
1169 | git pull | |
1170 | git merge release-5.xx.yy | |
1171 | git push | |
1172 | git branch -d release-5.xx.yy | |
ff721450 | 1173 | |
121e9ff0 SH |
1174 | Note: The merge will create a merge commit if other changes have been pushed |
1175 | to blead while you've been working on your release branch. Do NOT rebase your | |
1176 | branch to avoid the merge commit (as you might normally do when merging a | |
1177 | small branch into blead) since doing so will invalidate the tag that you | |
1178 | created earlier. | |
1179 | ||
c90225ed SH |
1180 | =head3 publish the release tag |
1181 | ||
1182 | Now that you've shipped the new perl release to PAUSE and pushed your changes | |
1183 | to the Perl master repository, it's time to publish the tag you created | |
1184 | earlier too (e.g.): | |
1185 | ||
1186 | $ git push origin tag v5.11.0 | |
1187 | ||
dc0a4df9 | 1188 | =head3 update epigraphs.pod |
f6af4394 | 1189 | |
85531b0a | 1190 | Add your quote to F<Porting/epigraphs.pod> and commit it. |
70d95cc9 SH |
1191 | You can include the customary link to the release announcement even before your |
1192 | message reaches the web-visible archives by looking for the X-List-Archive | |
1193 | header in your message after receiving it back via perl5-porters. | |
dc0a4df9 | 1194 | |
b02b3ec7 DR |
1195 | =head3 blog about your epigraph |
1196 | ||
1197 | If you have a blog, please consider writing an entry in your blog explaining | |
1198 | why you chose that particular quote for your epigraph. | |
1199 | ||
da571fa1 DR |
1200 | =for checklist skip RC |
1201 | ||
d274ee9d SH |
1202 | =head3 Release schedule |
1203 | ||
1204 | I<You MUST SKIP this step for RC> | |
1205 | ||
1206 | Tick the entry for your release in F<Porting/release_schedule.pod>. | |
1207 | ||
1208 | =for checklist skip RC | |
1209 | ||
dc0a4df9 | 1210 | =head3 Module::CoreList nagging |
85531b0a | 1211 | |
bc4c40f2 | 1212 | I<You MUST SKIP this step for RC> |
8c35d285 | 1213 | |
75a012fe DM |
1214 | Remind the current maintainer of C<Module::CoreList> to push a new release |
1215 | to CPAN. | |
7277a900 | 1216 | |
da571fa1 | 1217 | =for checklist skip RC |
dc0a4df9 DM |
1218 | |
1219 | =head3 new perldelta | |
a2cba4bc | 1220 | |
bc4c40f2 | 1221 | I<You MUST SKIP this step for RC> |
7277a900 | 1222 | |
bcfe7366 | 1223 | Create a new perldelta. |
5ef3945b | 1224 | |
bcfe7366 | 1225 | =over 4 |
8e967a1c | 1226 | |
bcfe7366 | 1227 | =item * |
8e967a1c | 1228 | |
bcfe7366 | 1229 | Confirm that you have a clean checkout with no local changes. |
c5b87fed | 1230 | |
bcfe7366 | 1231 | =item * |
17163f85 | 1232 | |
bcfe7366 | 1233 | Run F<Porting/new-perldelta.pl> |
8e967a1c | 1234 | |
bcfe7366 | 1235 | =item * |
17163f85 | 1236 | |
bcfe7366 | 1237 | Run the C<git add> commands it outputs to add new and modified files. |
7277a900 | 1238 | |
bcfe7366 | 1239 | =item * |
7277a900 | 1240 | |
bcfe7366 | 1241 | Verify that the build still works, by running C<./Configure> and |
e0373c35 | 1242 | C<make test_porting>. (On Win32 use the appropriate make utility). |
17163f85 | 1243 | |
bcfe7366 | 1244 | =item * |
17163f85 | 1245 | |
bcfe7366 NC |
1246 | If F<t/porting/podcheck.t> spots errors in the new F<pod/perldelta.pod>, |
1247 | run C<./perl -MTestInit t/porting/podcheck.t | less> for more detail. | |
1248 | Skip to the end of its test output to see the options it offers you. | |
57433fbf | 1249 | |
bcfe7366 | 1250 | =item * |
75a012fe | 1251 | |
bcfe7366 | 1252 | When C<make test_porting> passes, commit the new perldelta. |
75a012fe | 1253 | |
bcfe7366 | 1254 | =back |
75a012fe | 1255 | |
21768cb3 | 1256 | At this point you may want to compare the commit with a previous bump to |
ac2aec01 | 1257 | see if they look similar. See commit ba03bc34a4 for an example of a |
75a012fe | 1258 | previous version bump. |
57433fbf | 1259 | |
30f926b5 | 1260 | =for checklist skip MAINT RC |
dc0a4df9 DM |
1261 | |
1262 | =head3 bump version | |
57433fbf | 1263 | |
30f926b5 | 1264 | I<You MUST SKIP this step for RC and MAINT> |
dc0a62a1 | 1265 | |
6a958a95 DM |
1266 | If this was a BLEAD-FINAL release (i.e. the first release of a new maint |
1267 | series, 5.x.0 where x is even), then bump the version in the blead branch | |
1268 | in git, e.g. 5.12.0 to 5.13.0. | |
17163f85 | 1269 | |
6d5e92cd FC |
1270 | First, add a new feature bundle to F<regen/feature.pl>, initially by just |
1271 | copying the exiting entry, and bump the file's $VERSION (after the __END__ | |
1272 | marker); e.g. | |
17163f85 DM |
1273 | |
1274 | "5.14" => [qw(switch say state unicode_strings)], | |
1275 | + "5.15" => [qw(switch say state unicode_strings)], | |
addebd58 | 1276 | |
57fef7cc FC |
1277 | Run F<regen/feature.pl> to propagate the changes to F<lib/feature.pm>. |
1278 | ||
dc0a4df9 DM |
1279 | Then follow the section L<"Bump the version number"> to bump the version |
1280 | in the remaining files and test and commit. | |
17163f85 | 1281 | |
30f926b5 JL |
1282 | If this was a BLEAD-POINT release, then just follow the section |
1283 | L<"Bump the version number">. | |
1284 | ||
2136887a DG |
1285 | After bumping the version, follow the section L<"update INSTALL"> to |
1286 | ensure all version number references are correct. | |
17163f85 | 1287 | |
5f9f8ddf SH |
1288 | (Note: The version is NOT bumped immediately after a MAINT release in order |
1289 | to avoid confusion and wasted time arising from bug reports relating to | |
1290 | "intermediate versions" such as 5.20.1-and-a-bit: If the report is caused | |
1291 | by a bug that gets fixed in 5.20.2 and this intermediate version already | |
1292 | calls itself 5.20.2 then much time can be wasted in figuring out why there | |
1293 | is a failure from something that "should have been fixed". If the bump is | |
1294 | late then there is a much smaller window of time for such confusing bug | |
1295 | reports to arise. (The opposite problem -- trying to figure out why there | |
1296 | *is* a bug in something calling itself 5.20.1 when in fact the bug was | |
1297 | introduced later -- shouldn't arise for MAINT releases since they should, | |
1298 | in theory, only contain bug fixes but never regressions.)) | |
1299 | ||
d5c37431 NC |
1300 | =head3 clean build and test |
1301 | ||
1302 | Run a clean build and test to make sure nothing obvious is broken. | |
1303 | ||
1304 | In particular, F<Porting/perldelta_template.pod> is intentionally exempted | |
1305 | from podchecker tests, to avoid false positives about placeholder text. | |
1306 | However, once it's copied to F<pod/perldelta.pod> the contents can now | |
5cd8f091 | 1307 | cause test failures. Problems should be resolved by doing one of the |
ef4474b5 KW |
1308 | following: |
1309 | ||
1310 | =over | |
1311 | ||
1312 | =item 1 | |
1313 | ||
1314 | Replace placeholder text with correct text. | |
1315 | ||
1316 | =item 2 | |
1317 | ||
1318 | If the problem is from a broken placeholder link, you can add it to the | |
1319 | array C<@perldelta_ignore_links> in F<t/porting/podcheck.t>. Lines | |
1320 | containing such links should be marked with C<XXX> so that they get | |
1321 | cleaned up before the next release. | |
1322 | ||
1323 | =item 3 | |
1324 | ||
1325 | Following the instructions output by F<t/porting/podcheck.t> on how to | |
1326 | update its exceptions database. | |
1327 | ||
1328 | =back | |
d5c37431 | 1329 | |
dc0a4df9 DM |
1330 | =head3 push commits |
1331 | ||
1332 | Finally, push any commits done above. | |
1333 | ||
1334 | $ git push origin .... | |
1335 | ||
da571fa1 | 1336 | =for checklist skip BLEAD-POINT MAINT RC |
dc0a4df9 DM |
1337 | |
1338 | =head3 create maint branch | |
17163f85 | 1339 | |
6a958a95 | 1340 | I<You MUST SKIP this step for RC, BLEAD-POINT, MAINT> |
17163f85 | 1341 | |
6a958a95 DM |
1342 | If this was a BLEAD-FINAL release (i.e. the first release of a new maint |
1343 | series, 5.x.0 where x is even), then create a new maint branch based on | |
1344 | the commit tagged as the current release. | |
7277a900 | 1345 | |
233ca920 JV |
1346 | Assuming you're using git 1.7.x or newer: |
1347 | ||
17163f85 | 1348 | $ git checkout -b maint-5.12 v5.12.0 |
233ca920 | 1349 | $ git push origin -u maint-5.12 |
addebd58 | 1350 | |
dc0a4df9 | 1351 | |
da571fa1 DR |
1352 | =for checklist skip BLEAD-POINT MAINT RC |
1353 | ||
d5722260 DK |
1354 | =head3 make the maint branch available in the APC |
1355 | ||
1356 | Clone the new branch into /srv/gitcommon/branches on camel so the APC will | |
1357 | receive its changes. | |
1358 | ||
07697565 | 1359 | $ git clone --branch maint-5.14 /gitroot/perl.git \ |
d5722260 | 1360 | ? /srv/gitcommon/branches/perl-5.14.x |
07697565 | 1361 | $ chmod -R g=u /srv/gitcommon/branches/perl-5.14.x |
d5722260 DK |
1362 | |
1363 | And nag the sysadmins to make this directory available via rsync. | |
1364 | ||
1dbf7599 DG |
1365 | XXX Who are the sysadmins? Contact info? |
1366 | ||
da571fa1 | 1367 | =for checklist skip BLEAD-POINT RC |
d5722260 | 1368 | |
f6b1864d | 1369 | =head3 copy perldelta.pod to blead |
addebd58 | 1370 | |
6a958a95 | 1371 | I<You MUST SKIP this step for RC, BLEAD-POINT> |
8c35d285 | 1372 | |
f6b1864d | 1373 | Copy the perldelta.pod for this release into blead; for example: |
7277a900 | 1374 | |
f185f654 KW |
1375 | $ cd ..../blead |
1376 | $ cp -i ../5.10.x/pod/perldelta.pod pod/perl5101delta.pod #for example | |
1377 | $ git add pod/perl5101delta.pod | |
75a012fe | 1378 | |
5d0d3de0 SH |
1379 | Don't forget to set the NAME correctly in the new file (e.g. perl5101delta |
1380 | rather than perldelta). | |
1381 | ||
0aef0fe5 | 1382 | Edit F<pod/perl.pod> to add an entry for the file, e.g.: |
75a012fe DM |
1383 | |
1384 | perl5101delta Perl changes in version 5.10.1 | |
bc4c40f2 | 1385 | |
75a012fe | 1386 | Then rebuild various files: |
7277a900 | 1387 | |
00b85c8d | 1388 | $ perl Porting/pod_rules.pl |
75a012fe | 1389 | |
c90225ed | 1390 | Finally, commit and push: |
75a012fe DM |
1391 | |
1392 | $ git commit -a -m 'add perlXXXdelta' | |
c90225ed | 1393 | $ git push origin .... |
dc0a4df9 | 1394 | |
819435de | 1395 | =for checklist skip BLEAD-POINT |
7277a900 | 1396 | |
819435de | 1397 | =head3 copy perlhist.pod entries to blead |
1dbf7599 | 1398 | |
f6af4394 | 1399 | Make sure any recent F<pod/perlhist.pod> entries are copied to |
80dd5f25 | 1400 | F<perlhist.pod> on blead. e.g. |
7277a900 | 1401 | |
78a62309 | 1402 | 5.8.9 2008-Dec-14 |
7277a900 | 1403 | |
dc0a4df9 | 1404 | =head3 Relax! |
a3738a12 | 1405 | |
bc4c40f2 JV |
1406 | I<You MUST RETIRE to your preferred PUB, CAFE or SEASIDE VILLA for some |
1407 | much-needed rest and relaxation>. | |
8c35d285 JV |
1408 | |
1409 | Thanks for releasing perl! | |
1410 | ||
b28f69c2 Z |
1411 | =head2 Building a release - the day after |
1412 | ||
ab0bff1f | 1413 | =for checklist skip BLEAD-FINAL, MAINT, RC |
042e7a25 | 1414 | |
ab0bff1f | 1415 | =head3 update Module::CoreList |
042e7a25 DG |
1416 | |
1417 | I<After a BLEAD-POINT release only> | |
1418 | ||
1419 | After Module::CoreList has shipped to CPAN by the maintainer, update | |
1420 | Module::CoreList in the source so that it reflects the new blead | |
ab0bff1f SH |
1421 | version number: |
1422 | ||
1423 | =over 4 | |
1424 | ||
1425 | =item * | |
1426 | ||
1427 | Update F<Porting/Maintainers.pl> to list the new DISTRIBUTION on CPAN, | |
1428 | which should be identical to what is currently in blead. | |
1429 | ||
1430 | =item * | |
1431 | ||
1432 | Bump the $VERSION in F<dist/Module-CoreList/lib/Module/CoreList.pm>, | |
1433 | F<dist/Module-CoreList/lib/Module/CoreList/TieHashDelta.pm> and | |
1434 | F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm>. | |
1435 | ||
1436 | =item * | |
1437 | ||
1438 | If you have a local CPAN mirror, run: | |
1439 | ||
1440 | $ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror | |
1441 | ||
1442 | Otherwise, run: | |
1443 | ||
1444 | $ ./perl -Ilib Porting/corelist.pl cpan | |
1445 | ||
a4a5107a | 1446 | This will update F<dist/Module-CoreList/lib/Module/CoreList.pm> and |
244e6e4e SH |
1447 | F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm> as it did before, |
1448 | but this time adding new sections for the next BLEAD-POINT release. | |
ab0bff1f SH |
1449 | |
1450 | =item * | |
1451 | ||
1452 | Add the new $Module::CoreList::VERSION to | |
1453 | F<dist/Module-CoreList/Changes>. | |
1454 | ||
1455 | =item * | |
1456 | ||
1457 | Update F<pod/perldelta.pod> to mention the upgrade to Module::CoreList. | |
1458 | ||
1459 | =item * | |
1460 | ||
1461 | Remake perl to get your changed .pm files propagated into F<lib/> and | |
1462 | then run at least the F<dist/Module-CoreList/t/*.t> tests and the | |
1463 | test_porting makefile target to check that they're ok. | |
1464 | ||
1465 | =item * | |
1466 | ||
1467 | Run | |
1468 | ||
f185f654 KW |
1469 | $ ./perl -Ilib -MModule::CoreList \ |
1470 | -le 'print Module::CoreList->find_version($]) ? "ok" : "not ok"' | |
ab0bff1f SH |
1471 | |
1472 | and check that it outputs "ok" to prove that Module::CoreList now knows | |
1473 | about blead's current version. | |
1474 | ||
1475 | =item * | |
1476 | ||
1477 | Commit and push your changes. | |
1478 | ||
1479 | =back | |
042e7a25 | 1480 | |
dc0a4df9 DM |
1481 | =head3 check tarball availability |
1482 | ||
1483 | Check various website entries to make sure the that tarball has appeared | |
1484 | and is properly indexed: | |
1485 | ||
b28f69c2 Z |
1486 | =over 4 |
1487 | ||
1488 | =item * | |
1489 | ||
98df743a Z |
1490 | Check your author directory under L<http://www.cpan.org/authors/id/> |
1491 | to ensure that the tarballs are available on the website. | |
b28f69c2 Z |
1492 | |
1493 | =item * | |
1494 | ||
a95b3d6a KW |
1495 | Check F</src> on CPAN (on a fast mirror) to ensure that links to |
1496 | the new tarballs have appeared: There should be links in F</src/5.0> | |
ac2aec01 | 1497 | (which is accumulating all new versions), and (for BLEAD-FINAL and |
a95b3d6a | 1498 | MAINT only) an appropriate mention in F</src/README.html> (which describes |
ac2aec01 | 1499 | the latest versions in each stable branch, with links). |
98df743a | 1500 | |
a95b3d6a KW |
1501 | The F</src/5.0> links should appear automatically, some hours after upload. |
1502 | If they don't, or the F</src> description is inadequate, | |
98df743a | 1503 | ask Ask <ask@perl.org>. |
b28f69c2 Z |
1504 | |
1505 | =item * | |
1506 | ||
a95b3d6a | 1507 | Check L<http://www.cpan.org/src/> to ensure that the F</src> updates |
98df743a Z |
1508 | have been correctly mirrored to the website. |
1509 | If they haven't, ask Ask <ask@perl.org>. | |
1510 | ||
1511 | =item * | |
b28f69c2 | 1512 | |
98df743a Z |
1513 | Check L<http://search.cpan.org> to see if it has indexed the distribution. |
1514 | It should be visible at a URL like C<http://search.cpan.org/dist/perl-5.10.1/>. | |
b28f69c2 | 1515 | |
dc0a4df9 | 1516 | =back |
b28f69c2 | 1517 | |
e7b51df1 | 1518 | =for checklist skip RC |
dc0a4df9 DM |
1519 | |
1520 | =head3 update dev.perl.org | |
1521 | ||
e7b51df1 | 1522 | I<You MUST SKIP this step for a RC release> |
98df743a | 1523 | |
5fbaa27a | 1524 | In your C<perlweb> repository, link to the new release. For a new |
7a664ed5 RS |
1525 | latest-maint release, edit F<docs/shared/tpl/stats.html>. Otherwise, |
1526 | edit F<docs/dev/perl5/index.html>. | |
1527 | ||
1528 | Then make a pull request to Leo Lapworth. If this fails for some reason | |
1529 | and you cannot cajole anybody else into submitting that change, you can | |
1530 | mail Leo as last resort. | |
b28f69c2 | 1531 | |
7dbb22ac A |
1532 | This repository can be found on L<github|https://github.com/perlorg/perlweb>. |
1533 | ||
1dbf7599 DG |
1534 | =head3 update release manager's guide |
1535 | ||
1536 | Go over your notes from the release (you did take some, right?) and update | |
1537 | F<Porting/release_managers_guide.pod> with any fixes or information that | |
1538 | will make life easier for the next release manager. | |
1539 | ||
da571fa1 | 1540 | =for checklist end |
b28f69c2 | 1541 | |
7277a900 GS |
1542 | =head1 SOURCE |
1543 | ||
f6af4394 DM |
1544 | Based on |
1545 | http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2009-05/msg00608.html, | |
1546 | plus a whole bunch of other sources, including private correspondence. | |
7277a900 GS |
1547 | |
1548 | =cut | |
1549 |