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 | ||
c67d51c3 DM |
7 | As of August 2009, this file is mostly complete, although it is missing |
8 | some detail on doing a major release (e.g. 5.10.0 -> 5.12.0). Note that | |
d60a1044 DM |
9 | things change at each release, so there may be new things not covered |
10 | here, or tools may need updating. | |
f6af4394 | 11 | |
7277a900 GS |
12 | =head1 SYNOPSIS |
13 | ||
f6af4394 DM |
14 | This document describes the series of tasks required - some automatic, some |
15 | manual - to produce a perl release of some description, be that a snaphot, | |
8c35d285 | 16 | release candidate, or final, numbered release of maint or blead. |
f6af4394 | 17 | |
8c35d285 | 18 | The release process has traditionally been executed by the current |
ee76d676 JV |
19 | pumpking. Blead releases from 5.11.0 forward are made each month on the |
20 | 20th by a non-pumpking release engineer. The release engineer roster | |
21 | and schedule can be found in Porting/release_schedule.pod. | |
7277a900 | 22 | |
8c35d285 JV |
23 | This document both helps as a check-list for the release engineer |
24 | and is a base for ideas on how the various tasks could be automated | |
25 | or distributed. | |
7277a900 | 26 | |
636a1918 | 27 | The outline of a typical release cycle is as follows: |
f6af4394 | 28 | |
636a1918 | 29 | (5.10.1 is released, and post-release actions have been done) |
f6af4394 DM |
30 | |
31 | ...time passes... | |
32 | ||
33 | an occasional snapshot is released, that still identifies itself as | |
34 | 5.10.1 | |
35 | ||
36 | ...time passes... | |
37 | ||
38 | a few weeks before the release, a number of steps are performed, | |
39 | including bumping the version to 5.10.2 | |
636a1918 DM |
40 | |
41 | ...a few weeks passes... | |
46743ef7 | 42 | |
f6af4394 DM |
43 | perl-5.10.2-RC1 is released |
44 | ||
45 | perl-5.10.2 is released | |
46 | ||
47 | post-release actions are performed, including creating new | |
c5b87fed | 48 | perldelta.pod |
f6af4394 DM |
49 | |
50 | ... the cycle continues ... | |
7277a900 GS |
51 | |
52 | =head1 DETAILS | |
53 | ||
8c35d285 JV |
54 | Some of the tasks described below apply to all four types of |
55 | release of Perl. (snapshot, RC, final release of maint, final | |
56 | release of blead). Some of these tasks apply only to a subset | |
57 | of these release types. If a step does not apply to a given | |
58 | type of release, you will see a notation to that effect at | |
59 | the beginning of the step. | |
60 | ||
61 | =head2 Release types | |
62 | ||
63 | =over 4 | |
64 | ||
65 | =item Snapshot | |
66 | ||
67 | A snapshot is intended to encourage in-depth testing from time-to-time, | |
68 | for example after a key point in the stabilisation of a branch. It | |
69 | requires fewer steps than a full release, and the version number of perl in | |
70 | the tarball will usually be the same as that of the previous release. | |
71 | ||
72 | =item Release Candidate (RC) | |
73 | ||
d60a1044 DM |
74 | A release candidate is an attempt to produce a tarball that is a close as |
75 | possible to the final release. Indeed, unless critical faults are found | |
76 | during the RC testing, the final release will be identical to the RC | |
77 | barring a few minor fixups (updating the release date in F<perlhist.pod>, | |
78 | removing the RC status from F<patchlevel.h>, etc). If faults are found, | |
79 | then the fixes should be put into a new release candidate, never directly | |
80 | into a final release. | |
8c35d285 JV |
81 | |
82 | =item Stable/Maint release | |
83 | ||
84 | At this point you should have a working release candidate with few or no | |
85 | changes since. | |
86 | ||
87 | It's essentially the same procedure as for making a release candidate, but | |
88 | with a whole bunch of extra post-release steps. | |
89 | ||
90 | =item Blead release | |
91 | ||
92 | It's essentially the same procedure as for making a release candidate, but | |
93 | with a whole bunch of extra post-release steps. | |
94 | ||
95 | =back | |
7277a900 | 96 | |
fd838dcf JV |
97 | =head2 Prerequisites |
98 | ||
99 | Before you can make an official release of perl, there are a few | |
100 | hoops you need to jump through: | |
101 | ||
102 | =over 4 | |
103 | ||
8c35d285 JV |
104 | =item PAUSE account |
105 | ||
106 | I<SKIP this step for SNAPSHOT> | |
fd838dcf JV |
107 | |
108 | Make sure you have a PAUSE account suitable for uploading a perl release. | |
109 | If you don't have a PAUSE account, then request one: | |
110 | ||
111 | https://pause.perl.org/pause/query?ACTION=request_id | |
112 | ||
113 | Check that your account is allowed to upload perl distros: goto | |
b386fa44 | 114 | L<https://pause.perl.org/>, login, then select 'upload file to CPAN'; there |
fd838dcf | 115 | should be a "For pumpkings only: Send a CC" tickbox. If not, ask Andreas |
e03f126c | 116 | KE<0xf6>nig to add your ID to the list of people allowed to upload something |
fd838dcf | 117 | called perl. You can find Andreas' email address at: |
4d2c8158 | 118 | |
fd838dcf JV |
119 | https://pause.perl.org/pause/query?ACTION=pause_04imprint |
120 | ||
fdabea7a JV |
121 | =item search.cpan.org |
122 | ||
123 | Make sure that search.cpan.org knows that you're allowed to upload | |
124 | perl distros. Contact Graham Barr to make sure that you're on the right | |
125 | list. | |
126 | ||
8c35d285 JV |
127 | =item CPAN mirror |
128 | ||
129 | Some release engineering steps require a full mirror of the CPAN. | |
130 | Work to fall back to using a remote mirror via HTTP is incomplete | |
131 | but ongoing. (No, a minicpan mirror is not sufficient) | |
132 | ||
133 | =item git checkout and commit bit | |
fd838dcf JV |
134 | |
135 | You will need a working C<git> installation, checkout of the perl | |
136 | git repository and perl commit bit. For information about working | |
c222ef46 | 137 | with perl and git, see F<pod/perlgit.pod>. |
fd838dcf JV |
138 | |
139 | If you are not yet a perl committer, you won't be able to make a | |
140 | release. Have a chat with whichever evil perl porter tried to talk | |
141 | you into the idea in the first place to figure out the best way to | |
142 | resolve the issue. | |
143 | ||
f6af4394 | 144 | |
8c35d285 | 145 | =item Quotation for release announcement epigraph |
f6af4394 | 146 | |
8c35d285 | 147 | I<SKIP this step for SNAPSHOT and RC> |
f6af4394 | 148 | |
8c35d285 JV |
149 | For a numbered blead or maint release of perl, you will need a quotation |
150 | to use as an epigraph to your release announcement. (There's no harm | |
151 | in having one for a snapshot, but it's not required). | |
46743ef7 | 152 | |
f6af4394 DM |
153 | |
154 | =back | |
155 | ||
b82efa27 | 156 | |
2e831dfd | 157 | =head2 Building a release - advance actions |
8c35d285 JV |
158 | |
159 | The work of building a release candidate for a numbered release of | |
160 | perl generally starts several weeks before the first release candidate. | |
52a66c2c DM |
161 | Some of the following steps should be done regularly, but all I<must> be |
162 | done in the run up to a release. | |
7277a900 GS |
163 | |
164 | =over 4 | |
165 | ||
f6af4394 DM |
166 | =item * |
167 | ||
8c35d285 JV |
168 | I<You MAY SKIP this step for SNAPSHOT> |
169 | ||
f6af4394 DM |
170 | Ensure that dual-life CPAN modules are synchronised with CPAN. Basically, |
171 | run the following: | |
172 | ||
db3f805e | 173 | $ ./perl -Ilib Porting/core-cpan-diff -a -o /tmp/corediffs |
7277a900 | 174 | |
f6af4394 DM |
175 | to see any inconsistencies between the core and CPAN versions of distros, |
176 | then fix the core, or cajole CPAN authors as appropriate. See also the | |
177 | C<-d> and C<-v> options for more detail. You'll probably want to use the | |
04dbb930 DG |
178 | C<-c cachedir> option to avoid repeated CPAN downloads and may want to |
179 | use C<-m file:///mirror/path> if you made a local CPAN mirror. | |
7277a900 | 180 | |
f6af4394 | 181 | To see which core distro versions differ from the current CPAN versions: |
7277a900 | 182 | |
db3f805e | 183 | $ ./perl -Ilib Porting/core-cpan-diff -x -a |
7277a900 | 184 | |
52a66c2c | 185 | If you are making a maint release, run C<core-cpan-diff> on both blead and |
636a1918 DM |
186 | maint, then diff the two outputs. Compare this with what you expect, and if |
187 | necessary, fix things up. For example, you might think that both blead | |
188 | and maint are synchronised with a particular CPAN module, but one might | |
189 | have some extra changes. | |
190 | ||
f6af4394 | 191 | =item * |
7277a900 | 192 | |
8c35d285 JV |
193 | I<You MAY SKIP this step for SNAPSHOT> |
194 | ||
f6af4394 | 195 | Ensure dual-life CPAN modules are stable, which comes down to: |
7277a900 GS |
196 | |
197 | for each module that fails its regression tests on $current | |
f6af4394 DM |
198 | did it fail identically on $previous? |
199 | if yes, "SEP" (Somebody Else's Problem) | |
200 | else work out why it failed (a bisect is useful for this) | |
7277a900 GS |
201 | |
202 | attempt to group failure causes | |
203 | ||
204 | for each failure cause | |
f6af4394 DM |
205 | is that a regression? |
206 | if yes, figure out how to fix it | |
207 | (more code? revert the code that broke it) | |
208 | else | |
209 | (presumably) it's relying on something un-or-under-documented | |
210 | should the existing behaviour stay? | |
211 | yes - goto "regression" | |
212 | no - note it in perldelta as a significant bugfix | |
213 | (also, try to inform the module's author) | |
1aff5354 | 214 | |
f6af4394 | 215 | =item * |
7277a900 | 216 | |
8c35d285 JV |
217 | I<You MAY SKIP this step for SNAPSHOT> |
218 | ||
f6af4394 | 219 | Similarly, monitor the smoking of core tests, and try to fix. |
f85d27e8 | 220 | See L<http://doc.procura.nl/smoke/index.html> for a summary. |
7277a900 | 221 | |
f6af4394 | 222 | =item * |
7277a900 | 223 | |
8c35d285 JV |
224 | I<You MAY SKIP this step for SNAPSHOT> |
225 | ||
636a1918 DM |
226 | Similarly, monitor the smoking of perl for compiler warnings, and try to |
227 | fix. | |
228 | ||
229 | =item * | |
230 | ||
8c35d285 JV |
231 | I<You MAY SKIP this step for SNAPSHOT> |
232 | ||
f6af4394 | 233 | Get perldelta in a mostly finished state. |
db3f805e | 234 | |
04c2c53e | 235 | Read F<Porting/how_to_write_a_perldelta.pod>, and try to make sure that |
636a1918 DM |
236 | every section it lists is, if necessary, populated and complete. Copy |
237 | edit the whole document. | |
f6af4394 DM |
238 | |
239 | =item * | |
240 | ||
8c35d285 JV |
241 | I<You MUST SKIP this step for SNAPSHOT> |
242 | ||
04dbb930 DG |
243 | Bump the version number (e.g. from 5.12.0 to 5.12.1). |
244 | ||
245 | For a blead release, this can happen on the day of the release. For a | |
246 | release candidate for a stable perl, this should happen a week or two | |
247 | before the first release candidate to allow sufficient time for testing and | |
248 | smoking with the target version built into the perl executable. For | |
249 | subsequent release candidates and the final release, it it not necessary to | |
250 | bump the version further. | |
f6af4394 DM |
251 | |
252 | There is a tool to semi-automate this process. It works in two stages. | |
253 | First, it generates a list of suggested changes, which you review and | |
254 | edit; then you feed this list back and it applies the edits. So, first | |
52a66c2c DM |
255 | scan the source directory looking for likely candidates. The command line |
256 | arguments are the old and new version numbers, and -s means scan: | |
f6af4394 | 257 | |
30cdbfa1 | 258 | $ ./perl -Ilib Porting/bump-perl-version -s 5.10.0 5.10.1 > /tmp/scan |
f6af4394 | 259 | |
52a66c2c | 260 | This produces a file containing a list of suggested edits, e.g.: |
f6af4394 DM |
261 | |
262 | NetWare/Makefile | |
263 | ||
264 | 89: -MODULE_DESC = "Perl 5.10.0 for NetWare" | |
265 | +MODULE_DESC = "Perl 5.10.1 for NetWare" | |
266 | ||
267 | i.e. in the file F<NetWare/Makefile>, line 89 would be changed as shown. | |
268 | Review the file carefully, and delete any -/+ line pairs that you don't | |
52a66c2c DM |
269 | want changing. You can also edit just the C<+> line to change the |
270 | suggested replacement text. Remember that this tool is largely just | |
271 | grepping for '5.10.0' or whatever, so it will generate false positives. Be | |
272 | careful not change text like "this was fixed in 5.10.0"! Then run: | |
f6af4394 | 273 | |
30cdbfa1 | 274 | $ ./perl -Ilib Porting/bump-perl-version -u < /tmp/scan |
f6af4394 | 275 | |
54356a6f | 276 | which will update all the files shown. |
f6af4394 DM |
277 | |
278 | Be particularly careful with F<INSTALL>, which contains a mixture of | |
279 | C<5.10.0>-type strings, some of which need bumping on every release, and | |
e03f126c Z |
280 | some of which need to be left unchanged. |
281 | The line in F<INSTALL> about "is binary incompatible with" requires a | |
282 | correct choice of earlier version to declare incompatibility with. | |
283 | ||
284 | Also note that this tool | |
52a66c2c DM |
285 | currently only detects a single substitution per line: so in particular, |
286 | this line in README.vms needs special handling: | |
f6af4394 DM |
287 | |
288 | rename perl-5^.10^.1.dir perl-5_10_1.dir | |
7277a900 | 289 | |
45ce9531 | 290 | When doing a blead release, also make sure the C<PERL_API_*> constants in |
e43cb88f TM |
291 | F<patchlevel.h> are in sync with the version you're releasing, unless you're |
292 | absolutely sure the release you're about to make is 100% binary compatible | |
293 | to an earlier release. When releasing a stable perl version, the C<PERL_API_*> | |
294 | constants C<MUST NOT> be changed as we aim to guarantee binary compatibility | |
295 | in maint branches. | |
45ce9531 | 296 | |
54356a6f JV |
297 | Commit your changes: |
298 | ||
299 | $ git st | |
e91bd5c0 LB |
300 | $ git diff |
301 | B<review the delta carefully> | |
54356a6f JV |
302 | |
303 | $ git commit -a -m 'Bump the perl version in various places for 5.x.y' | |
dc0a62a1 | 304 | |
81fc59ef DG |
305 | When the version number is bumped, you should also update Module::CoreList (as |
306 | described below in L<"Building a release - on the day">) to reflect the new | |
307 | version number. | |
308 | ||
dc0a62a1 DM |
309 | =item * |
310 | ||
8c35d285 JV |
311 | I<You MUST SKIP this step for SNAPSHOT> |
312 | ||
dc0a62a1 DM |
313 | Review and update INSTALL to account for the change in version number; |
314 | in particular, the "Coexistence with earlier versions of perl 5" section. | |
315 | ||
c1b1cb88 FR |
316 | Be particularly careful with the section "Upgrading from 5.X.Y or earlier". For |
317 | stable releases, this needs to refer to the last release in the previous | |
318 | development cycle. For blead releases, it needs to refer to the previous blead | |
319 | release. | |
320 | ||
f6af4394 | 321 | =item * |
7277a900 | 322 | |
b82efa27 RS |
323 | I<You MUST SKIP this step for SNAPSHOT> |
324 | ||
325 | Update the F<Changes> file to contain the git log command which would show | |
326 | all the changes in this release. You will need assume the existence of a | |
327 | not-yet created tag for the forthcoming release; e.g. | |
328 | ||
329 | git log ... perl-5.10.0..perl-5.12.0 | |
330 | ||
331 | Due to warts in the perforce-to-git migration, some branches require extra | |
332 | exclusions to avoid other branches being pulled in. Make sure you have the | |
333 | correct incantation: replace the not-yet-created tag with C<HEAD> and see | |
334 | if C<git log> produces roughly the right number of commits across roughly the | |
335 | right time period (you may find C<git log --pretty=oneline | wc> useful). | |
336 | ||
337 | =item * | |
338 | ||
52a66c2c DM |
339 | Check some more build configurations. The check that setuid builds and |
340 | installs is for < 5.11.0 only. | |
341 | ||
342 | $ sh Configure -Dprefix=/tmp/perl-5.x.y -Uinstallusrbinperl \ | |
343 | -Duseshrplib -Dd_dosuid | |
344 | $ make | |
345 | $ LD_LIBRARY_PATH=`pwd` make test # or similar for useshrplib | |
7277a900 | 346 | |
52a66c2c DM |
347 | $ make suidperl |
348 | $ su -c 'make install' | |
349 | $ ls -l .../bin/sperl | |
350 | -rws--x--x 1 root root 69974 2009-08-22 21:55 .../bin/sperl | |
7277a900 | 351 | |
52a66c2c | 352 | (Then delete the installation directory.) |
7277a900 | 353 | |
52a66c2c | 354 | XXX think of other configurations that need testing. |
7277a900 | 355 | |
f6af4394 | 356 | =item * |
7277a900 | 357 | |
8c35d285 JV |
358 | I<You MAY SKIP this step for SNAPSHOT> |
359 | ||
347f5124 RGS |
360 | L<perlport> has a section currently named I<Supported Platforms> that |
361 | indicates which platforms are known to build in the current release. | |
362 | If necessary update the list and the indicated version number. | |
363 | ||
2e831dfd DM |
364 | =back |
365 | ||
366 | =head2 Building a release - on the day | |
367 | ||
368 | This section describes the actions required to make a release (or snapshot | |
369 | etc) that are performed on the actual day. | |
370 | ||
371 | =over 4 | |
372 | ||
373 | =item * | |
374 | ||
375 | Review all the items in the previous section, | |
376 | L<"Building a release - advance actions"> to ensure they are all done and | |
377 | up-to-date. | |
378 | ||
8c35d285 JV |
379 | =item * |
380 | ||
04dbb930 DG |
381 | For a blead release, if you did not bump the perl version number as part |
382 | of I<advance actions>, do that now. | |
383 | ||
384 | =item * | |
385 | ||
a0db33fe | 386 | I<You MAY SKIP this step for SNAPSHOT> |
2e831dfd | 387 | |
04dbb930 | 388 | Finalize the perldelta. In particular, fill in the Acknowledgements |
38195a8c DG |
389 | section. You can generate a list of contributors with checkAUTHORS.pl. |
390 | For example: | |
391 | ||
392 | $ git log --pretty=fuller v5.13.2..HEAD | \ | |
393 | perl Porting/checkAUTHORS.pl --who - | |
04dbb930 | 394 | |
a0db33fe DM |
395 | Re-read the perldelta to try to find any embarrassing typos and thinkos; |
396 | remove any C<TODO> or C<XXX> flags; update the "Known Problems" section | |
397 | with any serious issues for which fixes are not going to happen now; and | |
398 | run through pod and spell checkers, e.g. | |
2e831dfd | 399 | |
c5b87fed FR |
400 | $ podchecker -warnings -warnings pod/perldelta.pod |
401 | $ spell pod/perldelta.pod | |
2e831dfd | 402 | |
a0db33fe DM |
403 | Also, you may want to generate and view an HTML version of it to check |
404 | formatting, e.g. | |
2e831dfd | 405 | |
c5b87fed | 406 | $ perl pod/pod2html pod/perldelta.pod > /tmp/perldelta.html |
2e831dfd | 407 | |
38195a8c DG |
408 | Another good HTML preview option is http://search.cpan.org/pod2html |
409 | ||
410 | If you make changes, be sure to commit them. | |
411 | ||
8c35d285 JV |
412 | =item * |
413 | ||
a0db33fe DM |
414 | Make sure you have a gitwise-clean perl directory (no modified files, |
415 | unpushed commits etc): | |
8c35d285 | 416 | |
a0db33fe | 417 | $ git status |
24c5e187 | 418 | $ git clean -dxf |
8c35d285 JV |
419 | |
420 | =item * | |
421 | ||
a0db33fe DM |
422 | If not already built, Configure and build perl so that you have a Makefile |
423 | and porting tools: | |
8c35d285 | 424 | |
52a66c2c | 425 | $ ./Configure -Dusedevel -des && make |
8c35d285 JV |
426 | |
427 | =item * | |
428 | ||
bfadf2ba JV |
429 | I<You MUST SKIP this step for SNAPSHOT> |
430 | ||
1bac61bb | 431 | Update C<Module::CoreList> with module version data for the new release. |
bfadf2ba JV |
432 | |
433 | Note that if this is a maint release, you should run the following actions | |
1bac61bb | 434 | from the maint branch, but commit the C<CoreList.pm> changes in |
38195a8c | 435 | I<blead> and subsequently cherry-pick it. XXX need a better example |
bfadf2ba | 436 | |
a0db33fe | 437 | F<corelist.pl> uses ftp.funet.fi to verify information about dual-lived |
bfadf2ba | 438 | modules on CPAN. It can use a full, local CPAN mirror or fall back |
e8c01f92 SH |
439 | to C<wget> or C<curl> to fetch only package metadata remotely. (If you're |
440 | on Win32, then installing Cygwin is one way to have commands like C<wget> | |
441 | and C<curl> available.) | |
bfadf2ba JV |
442 | |
443 | (If you'd prefer to have a full CPAN mirror, see | |
444 | http://www.cpan.org/misc/cpan-faq.html#How_mirror_CPAN) | |
445 | ||
a0db33fe | 446 | Then change to your perl checkout, and if necessary, |
bfadf2ba | 447 | |
595f83ae | 448 | $ make |
bfadf2ba | 449 | |
81fc59ef DG |
450 | If this not the first update for this version (e.g. if it was updated |
451 | when the version number was originally bumped), first edit | |
d5bddf6e | 452 | F<dist/Module-CoreList/lib/Module/CoreList.pm> to delete the existing |
2ce7d676 RGS |
453 | entries for this version from the C<%released> and C<%version> hashes: |
454 | they will have a key like C<5.010001> for 5.10.1. | |
52a66c2c DM |
455 | |
456 | XXX the edit-in-place functionality of Porting/corelist.pl should | |
457 | be fixed to handle this automatically. | |
458 | ||
bf8ea215 | 459 | Then, If you have a local CPAN mirror, run: |
bfadf2ba | 460 | |
bfadf2ba JV |
461 | $ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror |
462 | ||
463 | Otherwise, run: | |
464 | ||
bfadf2ba JV |
465 | $ ./perl -Ilib Porting/corelist.pl cpan |
466 | ||
52a66c2c | 467 | This will chug for a while, possibly reporting various warnings about |
2a720090 | 468 | badly-indexed CPAN modules unrelated to the modules actually in core. |
2ce7d676 | 469 | Assuming all goes well, it will update |
d5bddf6e | 470 | F<dist/Module-CoreList/lib/Module/CoreList.pm>. |
bfadf2ba JV |
471 | |
472 | Check that file over carefully: | |
473 | ||
d5bddf6e | 474 | $ git diff dist/Module-CoreList/lib/Module/CoreList.pm |
bfadf2ba | 475 | |
bfadf2ba JV |
476 | If necessary, bump C<$VERSION> (there's no need to do this for |
477 | every RC; in RC1, bump the version to a new clean number that will | |
478 | appear in the final release, and leave as-is for the later RCs and final). | |
479 | ||
480 | Edit the version number in the new C<< 'Module::CoreList' => 'X.YZ' >> | |
481 | entry, as that is likely to reflect the previous version number. | |
482 | ||
e8c01f92 SH |
483 | Also edit Module::CoreList's new version number in its F<Changes> file and |
484 | in its F<META.yml> file. | |
485 | ||
3dbfcde0 AB |
486 | You should also add the version you're about to release to the |
487 | L<Module::CoreList/CAVEATS> section which enumerates the perl releases | |
488 | that Module::CoreList covers. | |
489 | ||
a0db33fe | 490 | In addition, if this is a final release (rather than a release candidate): |
bfadf2ba JV |
491 | |
492 | =over 4 | |
493 | ||
494 | =item * | |
495 | ||
496 | Update this version's entry in the C<%released> hash with today's date. | |
497 | ||
498 | =item * | |
499 | ||
500 | Make sure that the script has correctly updated the C<CAVEATS> section | |
501 | ||
502 | =back | |
503 | ||
504 | Finally, commit the new version of Module::CoreList: | |
a0db33fe DM |
505 | (unless this is for maint; in which case commit it blead first, then |
506 | cherry-pick it back). | |
bfadf2ba | 507 | |
770cf6ff | 508 | $ git commit -m 'Update Module::CoreList for 5.x.y' dist/Module-CoreList/lib/Module/CoreList.pm |
bfadf2ba | 509 | |
bfadf2ba JV |
510 | =item * |
511 | ||
a0db33fe | 512 | Check that the manifest is sorted and correct: |
8c35d285 | 513 | |
a0db33fe | 514 | $ make distclean |
300b5357 | 515 | $ git clean -xdf # This shouldn't be necessary if distclean is correct |
a0db33fe | 516 | $ perl Porting/manicheck |
d5bddf6e | 517 | |
7081fd3a | 518 | If manicheck turns up anything wrong, update MANIFEST and begin this step again. |
a0db33fe | 519 | |
7081fd3a JV |
520 | $ ./configure -des -Dusedevel |
521 | $ make test_porting | |
a0db33fe DM |
522 | $ git commit -m 'Update MANIFEST' MANIFEST |
523 | ||
524 | =item * | |
525 | ||
526 | I<You MUST SKIP this step for SNAPSHOT> | |
527 | ||
528 | Add an entry to F<pod/perlhist.pod> with the current date, e.g.: | |
529 | ||
530 | David 5.10.1-RC1 2009-Aug-06 | |
531 | ||
532 | Make sure that the correct pumpking is listed in the left-hand column, and | |
533 | if this is the first release under the stewardship of a new pumpking, make | |
534 | sure that his or her name is listed in the section entitled | |
535 | C<THE KEEPERS OF THE PUMPKIN>. | |
536 | ||
537 | Be sure to commit your changes: | |
538 | ||
539 | $ git commit -m 'add new release to perlhist' pod/perlhist.pod | |
8c35d285 JV |
540 | |
541 | =item * | |
542 | ||
38195a8c | 543 | I<You MUST SKIP this step for SNAPSHOT or BLEAD release> |
d7eb1120 | 544 | |
a42352ee DM |
545 | Update F<patchlevel.h> to add a C<-RC1>-or-whatever string; or, if this is |
546 | a final release, remove it. For example: | |
d7eb1120 DM |
547 | |
548 | static const char * const local_patches[] = { | |
549 | NULL | |
550 | + ,"RC1" | |
551 | PERL_GIT_UNPUSHED_COMMITS /* do not remove this line */ | |
552 | ||
553 | Be sure to commit your change: | |
554 | ||
555 | $ git commit -m 'bump version to RCnnn' patchlevel.h | |
556 | ||
557 | =item * | |
558 | ||
a0db33fe DM |
559 | Build perl, then make sure it passes its own test suite, and installs: |
560 | ||
561 | $ git clean -xdf | |
a42352ee DM |
562 | $ ./Configure -des -Dprefix=/tmp/perl-5.x.y-pretest |
563 | ||
564 | # or if it's an odd-numbered version: | |
a0db33fe | 565 | $ ./Configure -des -Dusedevel -Dprefix=/tmp/perl-5.x.y-pretest |
a42352ee | 566 | |
a0db33fe DM |
567 | $ make test install |
568 | ||
569 | =item * | |
570 | ||
52a66c2c DM |
571 | Check that the output of C</tmp/perl-5.x.y-pretest/bin/perl -v> and |
572 | C</tmp/perl-5.x.y-pretest/bin/perl -V> are as expected, | |
a0db33fe | 573 | especially as regards version numbers, patch and/or RC levels, and @INC |
52a66c2c DM |
574 | paths. Note that as they have been been built from a git working |
575 | directory, they will still identify themselves using git tags and | |
576 | commits. | |
577 | ||
578 | Then delete the temporary installation. | |
579 | ||
580 | =item * | |
581 | ||
a0db33fe DM |
582 | Push all your recent commits: |
583 | ||
584 | $ git push origin .... | |
585 | ||
96054f12 JV |
586 | |
587 | =item * | |
588 | ||
589 | I<You MUST SKIP this step for SNAPSHOT> | |
590 | ||
e8c01f92 | 591 | Tag the release (e.g.): |
96054f12 JV |
592 | |
593 | $ git tag v5.11.0 -m'First release of the v5.11 series!' | |
594 | ||
e8c01f92 SH |
595 | (Adjust the syntax appropriately if you're working on Win32, i.e. use |
596 | C<-m "..."> rather than C<-m'...'>.) | |
597 | ||
f662f3b7 JV |
598 | It is VERY important that from this point forward, you not push |
599 | your git changes to the Perl master repository. If anything goes | |
600 | wrong before you publish your newly-created tag, you can delete | |
601 | and recreate it. Once you push your tag, we're stuck with it | |
602 | and you'll need to use a new version number for your release. | |
603 | ||
a0db33fe DM |
604 | =item * |
605 | ||
8c35d285 JV |
606 | Create a tarball. Use the C<-s> option to specify a suitable suffix for |
607 | the tarball and directory name: | |
608 | ||
609 | $ cd root/of/perl/tree | |
610 | $ make distclean | |
75a012fe DM |
611 | $ git clean -xdf # make sure perl and git agree on files |
612 | $ git status # and there's nothing lying around | |
8c35d285 JV |
613 | |
614 | $ perl Porting/makerel -b -s `git describe` # for a snapshot | |
615 | $ perl Porting/makerel -b -s RC1 # for a release candidate | |
616 | $ perl Porting/makerel -b # for a final release | |
617 | ||
618 | This creates the directory F<../perl-x.y.z-RC1> or similar, copies all | |
619 | the MANIFEST files into it, sets the correct permissions on them, | |
620 | adds DOS line endings to some, then tars it up as | |
621 | F<../perl-x.y.z-RC1.tar.gz>. With C<-b>, it also creates a C<tar.bz2> file. | |
622 | ||
6480287f MT |
623 | If you're getting your tarball suffixed with -uncommitted and you're sure |
624 | your changes were all committed, you can override the suffix with: | |
625 | ||
626 | $ perl Porting/makerel -b -s '' | |
96054f12 | 627 | |
8c35d285 JV |
628 | XXX if we go for extra tags and branches stuff, then add the extra details |
629 | here | |
630 | ||
631 | =item * | |
632 | ||
a42352ee DM |
633 | Clean up the temporary directory, e.g. |
634 | ||
635 | $ rm -rf ../perl-x.y.z-RC1 | |
636 | ||
637 | =item * | |
638 | ||
8c35d285 JV |
639 | Copy the tarballs (.gz and possibly .bz2) to a web server somewhere you |
640 | have access to. | |
641 | ||
642 | =item * | |
643 | ||
644 | Download the tarball to some other machine. For a release candidate, | |
645 | you really want to test your tarball on two or more different platforms | |
646 | and architectures. The #p5p IRC channel on irc.perl.org is a good place | |
647 | to find willing victims. | |
648 | ||
649 | =item * | |
650 | ||
651 | Check that basic configuration and tests work on each test machine: | |
652 | ||
653 | $ ./Configure -des && make all test | |
f6af4394 DM |
654 | |
655 | =item * | |
656 | ||
8c35d285 JV |
657 | Check that the test harness and install work on each test machine: |
658 | ||
a42352ee | 659 | $ make distclean |
8c35d285 | 660 | $ ./Configure -des -Dprefix=/install/path && make all test_harness install |
a42352ee | 661 | $ cd /install/path |
8c35d285 JV |
662 | |
663 | =item * | |
664 | ||
665 | Check that the output of C<perl -v> and C<perl -V> are as expected, | |
666 | especially as regards version numbers, patch and/or RC levels, and @INC | |
667 | paths. | |
668 | ||
669 | Note that the results may be different without a F<.git/> directory, | |
670 | which is why you should test from the tarball. | |
671 | ||
672 | =item * | |
673 | ||
459fc3ca DM |
674 | Run the Installation Verification Procedure utility: |
675 | ||
676 | $ bin/perlivp | |
677 | ... | |
678 | All tests successful. | |
679 | $ | |
680 | ||
681 | =item * | |
682 | ||
d60a1044 DM |
683 | Compare the pathnames of all installed files with those of the previous |
684 | release (i.e. against the last installed tarball on this branch which you | |
685 | have previously verified using this same procedure). In particular, look | |
686 | for files in the wrong place, or files no longer included which should be. | |
687 | For example, suppose the about-to-be-released version is 5.10.1 and the | |
688 | previous is 5.10.0: | |
689 | ||
690 | cd installdir-5.10.0/ | |
691 | find . -type f | perl -pe's/5\.10\.0/5.10.1/g' | sort > /tmp/f1 | |
692 | cd installdir-5.10.1/ | |
693 | find . -type f | sort > /tmp/f2 | |
694 | diff -u /tmp/f[12] | |
695 | ||
696 | =item * | |
697 | ||
8c35d285 JV |
698 | Bootstrap the CPAN client on the clean install: |
699 | ||
75a012fe | 700 | $ bin/perl -MCPAN -e'shell' |
8c35d285 | 701 | |
e8c01f92 SH |
702 | (Use C<... -e "shell"> instead on Win32. You probably also need a set of |
703 | Unix command-line tools available for CPAN to function correctly without | |
704 | Perl alternatives like LWP installed. Cygwin is an obvious choice.) | |
705 | ||
8c35d285 JV |
706 | =item * |
707 | ||
a42352ee DM |
708 | Try installing a popular CPAN module that's reasonably complex and that |
709 | has dependencies; for example: | |
8c35d285 | 710 | |
a42352ee DM |
711 | CPAN> install Inline |
712 | CPAN> quit | |
8c35d285 JV |
713 | |
714 | Check that your perl can run this: | |
715 | ||
75a012fe | 716 | $ bin/perl -lwe 'use Inline C => "int f() { return 42;} "; print f' |
a42352ee DM |
717 | 42 |
718 | $ | |
8c35d285 | 719 | |
e8c01f92 SH |
720 | (Use C<... -lwe "use ..."> instead on Win32.) |
721 | ||
8c35d285 JV |
722 | =item * |
723 | ||
724 | Bootstrap the CPANPLUS client on the clean install: | |
725 | ||
75a012fe | 726 | $ bin/cpanp |
8c35d285 | 727 | |
e8c01f92 SH |
728 | (Again, on Win32 you'll need something like Cygwin installed, but make sure |
729 | that you don't end up with its various F<bin/cpan*> programs being found on | |
730 | the PATH before those of the Perl that you're trying to test.) | |
731 | ||
8c35d285 JV |
732 | =item * |
733 | ||
a42352ee | 734 | Install an XS module, for example: |
8c35d285 | 735 | |
a42352ee DM |
736 | CPAN Terminal> i DBI |
737 | CPAN Terminal> quit | |
738 | $ bin/perl -MDBI -e 1 | |
75a012fe | 739 | $ |
8c35d285 JV |
740 | |
741 | =item * | |
742 | ||
bc4c40f2 JV |
743 | I<If you're building a SNAPSHOT, you should STOP HERE> |
744 | ||
745 | =item * | |
8c35d285 | 746 | |
7f89f796 | 747 | Check that the L<perlbug> utility works. Try the following: |
47b1f096 | 748 | |
a14438df | 749 | $ bin/perlbug |
47b1f096 DM |
750 | ... |
751 | Subject: test bug report | |
752 | Local perl administrator [yourself]: | |
753 | Editor [vi]: | |
754 | Module: | |
755 | Category [core]: | |
756 | Severity [low]: | |
757 | (edit report) | |
758 | Action (Send/Display/Edit/Subject/Save to File): f | |
759 | Name of file to save message in [perlbug.rep]: | |
760 | Action (Send/Display/Edit/Subject/Save to File): q | |
761 | ||
762 | and carefully examine the output (in F<perlbug.rep]>), especially | |
763 | the "Locally applied patches" section. If everything appears okay, then | |
75a012fe DM |
764 | delete the file, and try it again, this time actually submitting the bug |
765 | report. Check that it shows up, then remember to close it! | |
47b1f096 DM |
766 | |
767 | =item * | |
768 | ||
f6af4394 DM |
769 | Wait for the smoke tests to catch up with the commit which this release is |
770 | based on (or at least the last commit of any consequence). | |
7277a900 | 771 | |
f6af4394 DM |
772 | Then check that the smoke tests pass (particularly on Win32). If not, go |
773 | back and fix things. | |
7277a900 | 774 | |
7277a900 | 775 | |
f6af4394 | 776 | =item * |
7277a900 | 777 | |
f6af4394 | 778 | Once smoking is okay, upload it to PAUSE. This is the point of no return. |
db3f805e JV |
779 | If anything goes wrong after this point, you will need to re-prepare |
780 | a new release with a new minor version or RC number. | |
781 | ||
a14438df DM |
782 | https://pause.perl.org/ |
783 | ||
784 | (Login, then select 'Upload a file to CPAN') | |
785 | ||
45924287 RS |
786 | If your workstation is not connected to a high-bandwidth, |
787 | high-reliability connection to the Internet, you should probably use the | |
788 | "GET URL" feature (rather than "HTTP UPLOAD") to have PAUSE retrieve the | |
789 | new release from wherever you put it for testers to find it. This will | |
790 | eliminate anxious gnashing of teeth while you wait to see if your | |
791 | 15 megabyte HTTP upload successfully completes across your slow, twitchy | |
c27b4e97 SH |
792 | cable modem. You can make use of your home directory on dromedary for |
793 | this purpose: F<http://users.perl5.git.perl.org/~USERNAME> maps to | |
794 | F</home/USERNAME/public_html>, where F<USERNAME> is your login account | |
795 | on dromedary. I<Remember>: if your upload is partially successful, you | |
796 | may need to contact a PAUSE administrator or even bump the version of perl. | |
45924287 | 797 | |
a42352ee | 798 | Upload both the .gz and .bz2 versions of the tarball. |
f6af4394 | 799 | |
c27b4e97 | 800 | Wait until you receive notification emails from the PAUSE indexer |
38195a8c | 801 | confirming that your uploads have been received. IMPORTANT -- you will |
b28f69c2 Z |
802 | probably get an email that indexing has failed, due to module permissions. |
803 | This is considered normal. | |
38195a8c DG |
804 | |
805 | Do not proceed any further until you are sure that your tarballs are on | |
806 | CPAN. Check your authors directory on one of the "fast" CPAN mirrors | |
b28f69c2 | 807 | (e.g., cpan.hexten.net |
38195a8c | 808 | or cpan.cpantesters.org) to confirm that your uploads have been successful. |
c27b4e97 | 809 | |
210de33e DM |
810 | =item * |
811 | ||
f662f3b7 | 812 | Now that you've shipped the new perl release to PAUSE, it's |
e8c01f92 | 813 | time to publish the tag you created earlier to the public git repo (e.g.): |
f662f3b7 JV |
814 | |
815 | $ git push origin tag v5.11.0 | |
f6af4394 DM |
816 | |
817 | =item * | |
818 | ||
a42352ee | 819 | Disarm the F<patchlevel.h> change; for example, |
d7eb1120 DM |
820 | |
821 | static const char * const local_patches[] = { | |
822 | NULL | |
823 | - ,"RC1" | |
824 | PERL_GIT_UNPUSHED_COMMITS /* do not remove this line */ | |
825 | ||
826 | Be sure to commit your change: | |
827 | ||
828 | $ git commit -m 'disarm RCnnn bump' patchlevel.h | |
a14438df | 829 | $ git push origin .... |
d7eb1120 | 830 | |
2e831dfd DM |
831 | |
832 | =item * | |
833 | ||
db3f805e | 834 | Mail p5p to announce your new release, with a quote you prepared earlier. |
f6af4394 DM |
835 | |
836 | =item * | |
837 | ||
85531b0a DG |
838 | Add your quote to F<Porting/epigraphs.pod> and commit it. |
839 | ||
840 | =item * | |
841 | ||
bc4c40f2 | 842 | I<You MUST SKIP this step for RC> |
8c35d285 | 843 | |
75a012fe DM |
844 | Remind the current maintainer of C<Module::CoreList> to push a new release |
845 | to CPAN. | |
7277a900 | 846 | |
75a012fe | 847 | =item * |
a2cba4bc | 848 | |
bc4c40f2 | 849 | I<You MUST SKIP this step for RC> |
7277a900 | 850 | |
c5b87fed | 851 | Create a new perldelta. |
7277a900 | 852 | |
5ef3945b SH |
853 | First, update the F<.gitignore> file in the F<pod/> folder to ignore the next |
854 | release's generated F<pod/perlNNNdelta.pod> file rather than this releases's | |
855 | one which we are about to set in stone (where NNN is the perl version number | |
856 | without the dots. i.e. 5135 for 5.13.5). | |
857 | ||
858 | Then, move the existing F<pod/perldelta.pod> to F<pod/perlNNNdelta.pod>. | |
7277a900 | 859 | |
c5b87fed FR |
860 | Now edit the moved delta file to change the C<NAME> from C<perldelta> to |
861 | C<perlNNNdelta>. | |
7277a900 | 862 | |
c5b87fed FR |
863 | Then create a new empty perldelta.pod file for the new release; see |
864 | F<Porting/how_to_write_a_perldelta.pod>. | |
8e967a1c | 865 | |
c5b87fed | 866 | You should be able to do this by just copying in a skeleton template and |
5ef3945b | 867 | then doing a quick fix up of the version numbers. |
8e967a1c | 868 | |
c5b87fed | 869 | Then commit the move and the new file. |
8e967a1c | 870 | |
c5b87fed | 871 | For example, assuming you just released 5.10.1: |
8e967a1c | 872 | |
c5b87fed FR |
873 | $ git mv pod/perldelta.pod pod/perl5101delta.pod |
874 | $ (edit pod/perl5101delta.pod to retitle) | |
8e967a1c | 875 | $ git add pod/perl5101delta.pod |
c5b87fed FR |
876 | |
877 | $ cp -i Porting/perldelta_template.pod pod/perldelta.pod | |
878 | $ (edit pod/perldelta.pod) | |
879 | $ git add pod/perldelta.pod | |
880 | $ git commit -m 'create perldelta for 5.10.2' | |
8e967a1c DG |
881 | |
882 | Now you need to update various tables of contents, most of which can be | |
883 | generated automatically. | |
7277a900 | 884 | |
c5b87fed FR |
885 | Edit F<pod.lst>: add the new entry, flagged as 'd', and unflag the previous |
886 | entry from being 'd'; for example: | |
75a012fe | 887 | |
c5b87fed FR |
888 | -d perl5101delta Perl changes in version 5.10.1 |
889 | +d perl5102delta Perl changes in version 5.10.2 | |
75a012fe | 890 | + perl5101delta Perl changes in version 5.10.1 |
7277a900 | 891 | |
75a012fe DM |
892 | Run C<perl pod/buildtoc --build-all> to update the F<perldelta> version in |
893 | the following files: | |
57433fbf JV |
894 | |
895 | MANIFEST | |
75a012fe DM |
896 | Makefile.SH |
897 | pod.lst | |
57433fbf | 898 | pod/perl.pod |
57433fbf | 899 | vms/descrip_mms.template |
75a012fe DM |
900 | win32/Makefile |
901 | win32/makefile.mk | |
902 | win32/pod.mak | |
903 | ||
75a012fe DM |
904 | Finally, commit: |
905 | ||
c5b87fed | 906 | $ git commit -a -m 'update TOC for perlNNNdelta' |
75a012fe DM |
907 | |
908 | At this point you may want to compare the commit with a previous bump to | |
5ef3945b | 909 | see if they look similar. See commit 2b6e134265 for an example of a |
75a012fe | 910 | previous version bump. |
57433fbf JV |
911 | |
912 | =item * | |
913 | ||
bc4c40f2 | 914 | I<You MUST SKIP this step for RC, BLEAD> |
dc0a62a1 | 915 | |
66d8ce14 JV |
916 | If this was the first release of a new maint series, (5.x.0 where x is |
917 | even), then create a new maint branch based on the commit tagged as | |
918 | the current release and bump the version in the blead branch in git, | |
919 | e.g. 5.12.0 to 5.13.0. | |
addebd58 DM |
920 | |
921 | [ XXX probably lots more stuff to do, including perldelta, | |
f6af4394 | 922 | C<lib/feature.pm> ] |
7277a900 | 923 | |
233ca920 JV |
924 | Assuming you're using git 1.7.x or newer: |
925 | ||
926 | $ git checkout -b maint-5.12 | |
927 | $ git push origin -u maint-5.12 | |
addebd58 DM |
928 | |
929 | =item * | |
930 | ||
bc4c40f2 | 931 | I<You MUST SKIP this step for RC, BLEAD> |
8c35d285 | 932 | |
c5b87fed | 933 | Copy the perldelta.pod for this release into the other branches; for |
75a012fe | 934 | example: |
7277a900 | 935 | |
c5b87fed | 936 | $ cp -i ../5.10.x/pod/perldelta.pod pod/perl5101delta.pod # for example |
75a012fe DM |
937 | $ git add pod/perl5101delta.pod |
938 | ||
939 | Edit F<pod.lst> to add an entry for the file, e.g.: | |
940 | ||
941 | perl5101delta Perl changes in version 5.10.1 | |
bc4c40f2 | 942 | |
75a012fe | 943 | Then rebuild various files: |
7277a900 | 944 | |
75a012fe DM |
945 | $ perl pod/buildtoc --build-all |
946 | ||
947 | Finally, commit: | |
948 | ||
949 | $ git commit -a -m 'add perlXXXdelta' | |
7277a900 | 950 | |
f6af4394 | 951 | =item * |
7277a900 | 952 | |
f6af4394 DM |
953 | Make sure any recent F<pod/perlhist.pod> entries are copied to |
954 | F<perlhist.pod> on other branches; typically the RC* and final entries, | |
955 | e.g. | |
7277a900 | 956 | |
f6af4394 DM |
957 | 5.8.9-RC1 2008-Nov-10 |
958 | 5.8.9-RC2 2008-Dec-06 | |
959 | 5.8.9 2008-Dec-14 | |
7277a900 | 960 | |
6e40fbf9 DM |
961 | =item * |
962 | ||
a3738a12 DM |
963 | If necessary, send an email to C<perlbug-admin at perl.org> requesting |
964 | that new version numbers be added to the RT fields C<Perl Version> and | |
965 | C<Fixed In>. | |
966 | ||
967 | =item * | |
968 | ||
bc4c40f2 JV |
969 | I<You MUST RETIRE to your preferred PUB, CAFE or SEASIDE VILLA for some |
970 | much-needed rest and relaxation>. | |
8c35d285 JV |
971 | |
972 | Thanks for releasing perl! | |
973 | ||
7277a900 GS |
974 | =back |
975 | ||
b28f69c2 Z |
976 | =head2 Building a release - the day after |
977 | ||
978 | =over 4 | |
979 | ||
980 | =item * | |
981 | ||
98df743a Z |
982 | Check your author directory under L<http://www.cpan.org/authors/id/> |
983 | to ensure that the tarballs are available on the website. | |
b28f69c2 Z |
984 | |
985 | =item * | |
986 | ||
98df743a Z |
987 | Check C</src> on CPAN (on a fast mirror) to ensure that links to |
988 | the new tarballs have appeared. There should be links in C</src/5.0> | |
989 | (which is accumulating all new versions), links in C</src> (which shows | |
990 | only the latest version on each branch), and an appropriate mention in | |
991 | C</src/README.html> (which describes the latest versions). | |
992 | ||
993 | These links should appear automatically, some hours after upload. | |
994 | If they don't, or the C<README.html> description is inadequate, | |
995 | ask Ask <ask@perl.org>. | |
b28f69c2 Z |
996 | |
997 | =item * | |
998 | ||
98df743a Z |
999 | Check L<http://www.cpan.org/src/> to ensure that the C</src> updates |
1000 | have been correctly mirrored to the website. | |
1001 | If they haven't, ask Ask <ask@perl.org>. | |
1002 | ||
1003 | =item * | |
b28f69c2 | 1004 | |
98df743a Z |
1005 | Check L<http://search.cpan.org> to see if it has indexed the distribution. |
1006 | It should be visible at a URL like C<http://search.cpan.org/dist/perl-5.10.1/>. | |
b28f69c2 Z |
1007 | |
1008 | =item * | |
1009 | ||
98df743a Z |
1010 | I<This step ONLY for STABLE> |
1011 | ||
1012 | Ask Rafael to update L<http://dev.perl.org/perl5/>. | |
b28f69c2 Z |
1013 | |
1014 | =back | |
1015 | ||
7277a900 GS |
1016 | =head1 SOURCE |
1017 | ||
f6af4394 DM |
1018 | Based on |
1019 | http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2009-05/msg00608.html, | |
1020 | plus a whole bunch of other sources, including private correspondence. | |
7277a900 GS |
1021 | |
1022 | =cut | |
1023 |