Commit | Line | Data |
7277a900 |
1 | |
2 | =head1 NAME |
3 | |
4 | release_managers_guide - Releasing a new version of perl 5.x |
5 | |
636a1918 |
6 | XXX as of Jul 2009, this file is still a work-in-progress. I think it |
7 | contains all the actions needed to build a release, but things may have |
8 | got skipped, and some things could do with polishing. Note that things |
9 | change each release, there may be new things not covered here, or |
10 | tools may need updating. DAPM |
f6af4394 |
11 | |
7277a900 |
12 | =head1 SYNOPSIS |
13 | |
f6af4394 |
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, |
16 | release candidate, or final release. |
17 | |
7277a900 |
18 | The release process is primarily executed by the current pumpking. |
19 | |
1aff5354 |
20 | This document both helps as a check-list for the pumpking and is |
7277a900 |
21 | a base for ideas on how the various tasks could be automated or |
22 | distributed. |
23 | |
636a1918 |
24 | The outline of a typical release cycle is as follows: |
f6af4394 |
25 | |
636a1918 |
26 | (5.10.1 is released, and post-release actions have been done) |
f6af4394 |
27 | |
28 | ...time passes... |
29 | |
30 | an occasional snapshot is released, that still identifies itself as |
31 | 5.10.1 |
32 | |
33 | ...time passes... |
34 | |
35 | a few weeks before the release, a number of steps are performed, |
36 | including bumping the version to 5.10.2 |
636a1918 |
37 | |
38 | ...a few weeks passes... |
f6af4394 |
39 | |
40 | perl-5.10.2-RC1 is released |
41 | |
42 | perl-5.10.2 is released |
43 | |
44 | post-release actions are performed, including creating new |
45 | perl5103delta.pod |
46 | |
47 | ... the cycle continues ... |
7277a900 |
48 | |
49 | =head1 DETAILS |
50 | |
7277a900 |
51 | |
f6af4394 |
52 | =head2 Building a snapshot |
53 | |
54 | A snapshot is intended to encourage in-depth testing from time-to-time, |
55 | for example after a key point in the stabilisation of a branch. It |
56 | requires less steps than a full release, and the version number of perl in |
57 | the tarball will usually still be the old one. |
58 | |
59 | =over 4 |
60 | |
61 | =item * |
62 | |
63 | As there are no regular smokes [ XXX yet - please fix?] find out about the |
64 | state of VMS. If it's bad, think again. |
65 | |
66 | =item * |
67 | |
68 | Rebuild META.yml: |
69 | |
70 | $ rm META.yml |
71 | $ make META.yml |
72 | |
73 | and commit it if it's changed. |
74 | |
75 | =item * |
76 | |
77 | Check that the manifest is sorted and correct: |
78 | |
79 | $ make distclean |
80 | $ perl Porting/manisort |
81 | $ perl Porting/manicheck |
82 | |
83 | =item * |
84 | |
85 | If this is a release candidate or final release, add an entry to |
86 | F<pod/perlhist.pod> with the current date, e.g. |
87 | |
88 | 5.8.9-RC1 2008-Nov-10 |
89 | |
ce4f4fe2 |
90 | Make sure the correct pumpking is listed, and if this is your first time, |
f6af4394 |
91 | append your name to C<THE KEEPERS OF THE PUMPKIN>. |
92 | |
93 | =item * |
94 | |
95 | Build perl, then make sure it passes its own test suite, and installs. |
96 | |
97 | =item * |
98 | |
99 | Create a tarball. Use the C<-s> option to specify a suitable suffix for |
100 | the tarball and directory name: |
101 | |
102 | $ cd root/of/perl/tree |
103 | $ git clean -xdf # make sure perl and git agree on files |
104 | |
85bdf03b |
105 | $ perl Porting/makerel -b -s `git describe` # for a snapshot |
106 | $ perl Porting/makerel -b -s RC1 # for a release candidate |
107 | $ perl Porting/makerel -b # for a final release |
f6af4394 |
108 | |
109 | This creates the directory F<../perl-x.y.z-RC1> or similar, copies all |
110 | the MANIFEST files into it, sets the correct permissions on them, |
111 | adds DOS line endings to some, then tars it up as |
85bdf03b |
112 | F<../perl-x.y.z-RC1.tar.gz>. With C<-b>, it also creates a C<tar.bz2> file. |
f6af4394 |
113 | |
114 | XXX if we go for extra tags and branches stuff, then add the extra details |
115 | here |
116 | |
117 | =item * |
118 | |
85bdf03b |
119 | Copy the tarballs (.gz and possibly .bz2) to a web server somewhere you |
120 | have access to. |
f6af4394 |
121 | |
122 | =item * |
123 | |
85bdf03b |
124 | Download the tarball to some other machine (for a release candidate, to |
125 | two or more servers: IRC is good for this). |
f6af4394 |
126 | |
127 | =item * |
128 | |
129 | Check that C<./Configure -des && make all test> works in one place. |
130 | |
131 | =item * |
132 | |
133 | Check that C<./Configure ... && make all test_harness install> works. |
134 | |
135 | =item * |
136 | |
137 | Check that the output of C<perl -v> and C<perl -V> are as expected, |
138 | especially as regards version numbers, patch and/or RC levels, and @INC |
139 | paths. Note that the results may be different without a F<.git/> directory, |
140 | which is why you should test from the tarball. |
141 | |
142 | =item * |
143 | |
144 | Bootstrap the CPAN client on the clean install. |
145 | |
146 | =item * |
147 | |
148 | Install CPANPLUS. |
149 | XXX pick something new; this is now bundled |
150 | |
9db5571e |
151 | =begin suggestion |
152 | |
153 | How about Inline. Install it, and then check that your perl can run this: |
154 | perl -lwe 'use Inline C => "int answer() { return 42;} "; print answer' |
155 | |
156 | =end |
157 | |
f6af4394 |
158 | =item * |
159 | |
160 | Bootstrap the CPANPLUS client. |
161 | |
162 | =item * |
163 | |
164 | Install an XS module. |
165 | |
166 | =item * |
167 | |
85bdf03b |
168 | If all is well, announce the snapshot to p5p. (For a release candidate, |
f6af4394 |
169 | instead follow the further steps described later.) |
170 | |
171 | =back |
172 | |
173 | =head2 Actions prior to the first release candidate |
174 | |
175 | A week or two before the first release candidate, there are some additional |
176 | tasks you should perform (actually, some of these should be done regularly |
177 | anyway, but they definitely need doing now): |
7277a900 |
178 | |
179 | =over 4 |
180 | |
f6af4394 |
181 | =item * |
182 | |
183 | Check F<Maintainers.pl> for consistency; both these commands should |
184 | produce no output: |
185 | |
186 | perl Porting/Maintainers --checkmani |
187 | perl Porting/Maintainers --checkmani lib/ ext/ |
188 | |
189 | =item * |
190 | |
191 | Ensure that dual-life CPAN modules are synchronised with CPAN. Basically, |
192 | run the following: |
193 | |
194 | ./perl -Ilib Porting/core-cpan-diff -a -o /tmp/corediffs |
7277a900 |
195 | |
f6af4394 |
196 | to see any inconsistencies between the core and CPAN versions of distros, |
197 | then fix the core, or cajole CPAN authors as appropriate. See also the |
198 | C<-d> and C<-v> options for more detail. You'll probably want to use the |
199 | C<-c cachedir> option to avoid repeated CPAN downloads. |
7277a900 |
200 | |
f6af4394 |
201 | To see which core distro versions differ from the current CPAN versions: |
7277a900 |
202 | |
f6af4394 |
203 | ./perl -Ilib Porting/core-cpan-diff -x -a |
7277a900 |
204 | |
636a1918 |
205 | if you are making a maint release, run C<core-cpan-diff> on both blead and |
206 | maint, then diff the two outputs. Compare this with what you expect, and if |
207 | necessary, fix things up. For example, you might think that both blead |
208 | and maint are synchronised with a particular CPAN module, but one might |
209 | have some extra changes. |
210 | |
f6af4394 |
211 | =item * |
7277a900 |
212 | |
f6af4394 |
213 | Ensure dual-life CPAN modules are stable, which comes down to: |
7277a900 |
214 | |
215 | for each module that fails its regression tests on $current |
f6af4394 |
216 | did it fail identically on $previous? |
217 | if yes, "SEP" (Somebody Else's Problem) |
218 | else work out why it failed (a bisect is useful for this) |
7277a900 |
219 | |
220 | attempt to group failure causes |
221 | |
222 | for each failure cause |
f6af4394 |
223 | is that a regression? |
224 | if yes, figure out how to fix it |
225 | (more code? revert the code that broke it) |
226 | else |
227 | (presumably) it's relying on something un-or-under-documented |
228 | should the existing behaviour stay? |
229 | yes - goto "regression" |
230 | no - note it in perldelta as a significant bugfix |
231 | (also, try to inform the module's author) |
1aff5354 |
232 | |
f6af4394 |
233 | =item * |
7277a900 |
234 | |
f6af4394 |
235 | Similarly, monitor the smoking of core tests, and try to fix. |
7277a900 |
236 | |
f6af4394 |
237 | =item * |
7277a900 |
238 | |
636a1918 |
239 | Similarly, monitor the smoking of perl for compiler warnings, and try to |
240 | fix. |
241 | |
242 | =item * |
243 | |
f6af4394 |
244 | Run F<Porting/cmpVERSION.pl> to compare the current source tree with the |
245 | previous version to check for for modules that have identical version |
246 | numbers but different contents, e.g.: |
7277a900 |
247 | |
f6af4394 |
248 | $ cd ~/some-perl-root |
249 | $ ./perl -Ilib Porting/cmpVERSION.pl -xd ~/my_perl-tarballs/perl-5.10.0 . |
250 | |
251 | then bump the version numbers of any non-dual-life modules that have |
252 | changed since the previous release, but which still have the old version |
253 | number. If there is more than one maintenance branch (e.g. 5.8.x, 5.10.x), |
254 | then compare against both. |
255 | |
256 | Note that some of the files listed may be generated (e.g. copied from ext/ |
257 | to lib/, or a script like lib/lib_pm.PL is run to produce lib/lib.pm); |
258 | make sure you edit the correct file! |
259 | |
260 | Once all version numbers have been bumped, re-run the checks. |
261 | |
262 | Then run again without the -x option, to check that dual-life modules are |
263 | also sensible. |
264 | |
265 | |
266 | =item * |
267 | |
268 | Get perldelta in a mostly finished state. |
636a1918 |
269 | Peruse F<Porting/how_to_write_a_perldelta.pod>, and try to make sure that |
270 | every section it lists is, if necessary, populated and complete. Copy |
271 | edit the whole document. |
f6af4394 |
272 | |
273 | =item * |
274 | |
275 | Bump the perl version number (e.g. from 5.10.0 to 5.10.1). |
276 | |
277 | There is a tool to semi-automate this process. It works in two stages. |
278 | First, it generates a list of suggested changes, which you review and |
279 | edit; then you feed this list back and it applies the edits. So, first |
280 | scan the source dir looking for likely candidates: |
281 | |
282 | $ Porting/bump-perl-version -s 5.10.0 5.10.1 > /tmp/scan |
283 | |
284 | This produces a file containing a list of suggested edits, eg: |
285 | |
286 | NetWare/Makefile |
287 | |
288 | 89: -MODULE_DESC = "Perl 5.10.0 for NetWare" |
289 | +MODULE_DESC = "Perl 5.10.1 for NetWare" |
290 | |
291 | i.e. in the file F<NetWare/Makefile>, line 89 would be changed as shown. |
292 | Review the file carefully, and delete any -/+ line pairs that you don't |
293 | want changing. Remember that this tool is largely just grepping for '5.10.0' |
294 | or whatever, so it will generate false positives. Be careful not change |
295 | text like "this was fixed in 5.10.0"! Then run: |
296 | |
297 | $ Porting/bump-perl-version -u < /tmp/scan |
298 | |
299 | which will update all the files shown; then commit the changes. |
300 | |
301 | Be particularly careful with F<INSTALL>, which contains a mixture of |
302 | C<5.10.0>-type strings, some of which need bumping on every release, and |
303 | some of which need to be left. Also note that this tool currently only |
304 | performs a single change per line, so in particular, this line in |
305 | README.vms needs special handling: |
306 | |
307 | rename perl-5^.10^.1.dir perl-5_10_1.dir |
7277a900 |
308 | |
dc0a62a1 |
309 | |
310 | =item * |
311 | |
312 | Review and update INSTALL to account for the change in version number; |
313 | in particular, the "Coexistence with earlier versions of perl 5" section. |
314 | |
f6af4394 |
315 | =item * |
7277a900 |
316 | |
f6af4394 |
317 | Update the F<Changes> file to contain the git log command which would show |
318 | all the changes in this release. You will need assume the existence of a |
319 | not-yet created tag for the forthcoming release; e.g. |
7277a900 |
320 | |
f6af4394 |
321 | git log ... perl-5.10.0..perl5.12.0 |
7277a900 |
322 | |
f6af4394 |
323 | Due to warts in the perforce-to-git migration, some branches require extra |
324 | exclusions to avoid other branches being pulled in. Make sure you have the |
325 | correct incantation: replace the not-yet-created tag with C<HEAD> and see |
326 | if git log produces roughly the right number of commits across roughly the |
327 | right time period. |
7277a900 |
328 | |
dc0a62a1 |
329 | |
f6af4394 |
330 | =item * |
7277a900 |
331 | |
f6af4394 |
332 | Check some more build configurations, e.g. |
7277a900 |
333 | |
f6af4394 |
334 | -Duseshrplib -Dd_dosuid |
335 | make suidperl |
7277a900 |
336 | |
f6af4394 |
337 | Check that setuid installs works (for < 5.11.0 only). |
338 | XXX any other configs? |
7277a900 |
339 | |
f6af4394 |
340 | =item * |
7277a900 |
341 | |
f6af4394 |
342 | Make sure you have a PAUSE account suitable for uploading a perl release. |
343 | If you don't have a PAUSE account, then request one: |
7277a900 |
344 | |
f6af4394 |
345 | https://pause.perl.org/pause/query?ACTION=request_id |
7277a900 |
346 | |
f6af4394 |
347 | Check that your account is allowed to upload perl distros: goto |
348 | https://pause.perl.org/, login, then select 'upload file to CPAN'; there |
349 | should be a "For pumpkings only: Send a CC" tickbox. If not, ask Andreas |
350 | to add your ID to the list of people allowed to upload something called |
351 | perl. |
7277a900 |
352 | |
f6af4394 |
353 | =item * |
7277a900 |
354 | |
f6af4394 |
355 | Update F<AUTHORS>, using the C<Porting/checkAUTHORS.pl> script, and if |
356 | necessary, update the script to include new alias mappings. |
7277a900 |
357 | |
f6af4394 |
358 | XXX This script is currently broken (7/2009). It needs updating to work |
359 | with git and a lack of Changes files. |
360 | |
361 | =back |
362 | |
363 | =head2 Building a release candidate |
364 | |
365 | (At this point you should already have performed the actions described in |
dc0a62a1 |
366 | L</"Actions prior to the first release candidate">.) You should review |
367 | that section to ensure that everything there has done, and to see whether |
368 | any of those actions (such as consistency checks) need to be repeated. |
f6af4394 |
369 | |
370 | =over 4 |
371 | |
372 | =item * |
373 | |
374 | Re-read the perldelta to try to find any embarrassing typos and thinkos; |
375 | remove any C<TODO> or C<XXX> flags; and run through pod and spell |
636a1918 |
376 | checkers, e.g. |
377 | |
378 | podchecker -warnings -warnings pod/perl5101delta.pod |
379 | spell pod/perl5101delta.pod |
f6af4394 |
380 | |
381 | =item * |
382 | |
383 | Update patchlevel.h to add a C<-RC1>-or-whatever string; or, if this is a |
384 | final release, remove it. [ XXX how now?? see 34813 for old way ] |
385 | |
386 | =item * |
387 | |
388 | Update C<Module::Corelist>. |
210de33e |
389 | |
ce4f4fe2 |
390 | Note that if this is a maint release, you should run the following actions |
210de33e |
391 | from the maint directory, but edit the C<Corelist.pm> in I<blead> and |
392 | subsequently cherry-pick it. |
393 | |
394 | First, in order to update the C<%upstream> and C<%bug_tracker> hashes, |
395 | the C<Porting/corelist.pl> script requires you to have a local CPAN |
396 | mirror. See http://www.cpan.org/misc/cpan-faq.html#How_mirror_CPAN for |
397 | more details, but basically: |
398 | |
399 | $ mkdir ~/cpan-mirror |
400 | $ rsync -av --delete ftp.funet.fi::CPAN ~/cpan-mirror/ |
401 | |
402 | (and re-run the rsync each time you need it to be up-to-date). |
403 | [XXX this really needs fixing to not require a whole CPAN mirror] |
404 | |
405 | If necessary, bump C<$VERSION> (there's no need to do this for |
406 | every RC; in RC1, bump the version to a new clean number that will |
407 | appear in the final release, and leave as-is for the later RCs and final). |
408 | |
409 | Then do |
410 | |
411 | $ cd ~/perl/root; make perl |
412 | $ ./perl -Ilib Porting/corelist.pl ~/cpan-mirror/ > /tmp/corelist |
413 | |
414 | This creates a file that looks something like |
415 | |
416 | 5.010001 => { |
417 | 'AnyDBM_File' => '1.00', |
418 | ... |
419 | }, |
420 | |
421 | %upstream = ( |
422 | 'App::Prove' => undef, |
423 | ... |
424 | ); |
425 | |
426 | %bug_tracker = ( |
427 | 'App::Prove' => 'http://rt.cpan.org/...', |
428 | ... |
429 | ); |
430 | |
210de33e |
431 | Cut and paste these tables into F<lib/Module/CoreList.pm>: the module |
432 | version list should be appended as the last entry in the C<%version> hash |
433 | (or replaced, if we've already added it for an earlier release candidate), |
434 | while the existing C<%upstream> and C<%bug_tracker> hashes should be |
435 | replaced with the new versions. |
436 | |
ce4f4fe2 |
437 | Edit the version number in the new C<< 'Module::CoreList' => 'X.YZ' >> |
210de33e |
438 | entry, as that is likely to reflect the previous version number. |
439 | |
440 | Then, add the current perl version to the C<CAVEATS> paragraph. |
441 | |
442 | Add or update an entry to the C<%released> hash, including today's date |
443 | (if this is just a release candidate, set the date to '????-??-??'). |
444 | |
7277a900 |
445 | |
f6af4394 |
446 | =item * |
447 | |
448 | Follow the instructions in the section L</"Building a snapshot">, then |
449 | carry on with the extra steps that follow here. |
450 | |
451 | =item * |
7277a900 |
452 | |
addebd58 |
453 | Disarm the patchlevel.h change [ XXX expand ] |
454 | |
455 | =item * |
456 | |
f6af4394 |
457 | Wait for the smoke tests to catch up with the commit which this release is |
458 | based on (or at least the last commit of any consequence). |
7277a900 |
459 | |
f6af4394 |
460 | Then check that the smoke tests pass (particularly on Win32). If not, go |
461 | back and fix things. |
7277a900 |
462 | |
7277a900 |
463 | |
f6af4394 |
464 | =item * |
7277a900 |
465 | |
f6af4394 |
466 | Once smoking is okay, upload it to PAUSE. This is the point of no return. |
addebd58 |
467 | You may wish to create a .bz2 version of the tarball and upload that too. |
f6af4394 |
468 | |
210de33e |
469 | =item * |
470 | |
471 | create a tag [XXX and branches and stuff ????], e.g.: |
472 | |
473 | $ git tag perl-5.10.1-RC1 -m'Release Candidate 1 of Perl 5.10.1' |
474 | $ git push origin tag perl-5.10.1-RC1 |
f6af4394 |
475 | |
476 | =item * |
477 | |
478 | Mail p5p to announce it, with a quote you prepared earlier. |
479 | |
480 | =item * |
481 | |
482 | Wait 24 hours or so, then post the announcement to use.perl.org. |
addebd58 |
483 | (if you don't have access rights to post news, ask someone like Rafael to |
484 | do it for you.) |
f6af4394 |
485 | |
486 | =back |
487 | |
488 | |
489 | =head2 Making a final release |
490 | |
491 | At this point you should have a working release candidate with few or no |
492 | changes since. |
493 | |
494 | It's essentially the same procedure as for making a release candidate, but |
495 | with a whole bunch of extra post-release steps. |
496 | |
497 | =over 4 |
7277a900 |
498 | |
f6af4394 |
499 | =item * |
7277a900 |
500 | |
f6af4394 |
501 | Follow the same steps as for making a release candidate, then |
7277a900 |
502 | |
f6af4394 |
503 | =item * |
7277a900 |
504 | |
f6af4394 |
505 | Ask Jarkko to update http://www.cpan.org/src/README.html and |
506 | Rafael to update http://dev.perl.org/perl5/ |
7277a900 |
507 | |
f6af4394 |
508 | =item * |
7277a900 |
509 | |
f6af4394 |
510 | Create a new empty perlNNNdelta.pod file for the current release + 1; |
511 | see F<Porting/how_to_write_a_perldelta.pod>. |
512 | [ XXX Perhaps we should have an empty template file we can copy in. ] |
7277a900 |
513 | |
a2cba4bc |
514 | In addition, edit F<pod.lst>, adding the new entry as 'D', and unmark previous |
515 | entry as 'D', then run C<perl pod/buildtoc --build-all> to update the |
516 | following files: |
7277a900 |
517 | |
f6af4394 |
518 | MANIFEST |
f6af4394 |
519 | pod/perl.pod |
a2cba4bc |
520 | win32/pod.mak |
521 | vms/descrip_mms.template |
522 | |
523 | (F<vms/descrip_mms.template> still needs a manual edit to bump the |
524 | C<perldelta.pod> entry - it would be good for someone to figure out the fix.) |
7277a900 |
525 | |
f6af4394 |
526 | and change perlNNNdelta references to the new version in these files |
7277a900 |
527 | |
f6af4394 |
528 | INSTALL |
529 | win32/Makefile.mk |
530 | win32/Makefile |
531 | Makefile.SH |
532 | README |
7277a900 |
533 | |
f6af4394 |
534 | Also, edit the previous delta file to change the C<NAME> from C<perldelta> |
535 | to C<perlNNNdelta>. |
7277a900 |
536 | |
f6af4394 |
537 | These two lists of files probably aren't exhaustive; do a recursive grep |
538 | on the previous filename to look for suitable candidates. |
7277a900 |
539 | |
f6af4394 |
540 | (see 16410843ea for an example). |
7277a900 |
541 | |
f6af4394 |
542 | =item * |
7277a900 |
543 | |
dc0a62a1 |
544 | If this was a maintenance release, then edit F<Porting/mergelog> to change |
545 | all the C<d> (deferred) flags to C<.> (needs review). |
546 | |
547 | |
548 | =item * |
549 | |
addebd58 |
550 | If this was a major release, then |
551 | |
552 | =over |
553 | |
554 | =item * |
555 | |
556 | bump the version, e.g. 5.12.0 to 5.13.0; |
557 | |
558 | =item * |
559 | |
560 | [ XXX probably lots more stuff to do, including perldelta, |
f6af4394 |
561 | C<lib/feature.pm> ] |
7277a900 |
562 | |
f6af4394 |
563 | =item * |
7277a900 |
564 | |
addebd58 |
565 | Create a new maint branch with an empty Porting/mergelog file |
566 | [ XXX and lots of other stuff too, probably ] |
567 | |
568 | =back |
569 | |
570 | =item * |
571 | |
f6af4394 |
572 | Copy the perlNNNdelta.pod for this release into the other branches, and |
573 | remember to update these files on those branches too: |
7277a900 |
574 | |
f6af4394 |
575 | MANIFEST |
576 | pod.lst |
577 | pod/perl.pod |
578 | vms/descrip_mms.template |
579 | win32/pod.mak |
7277a900 |
580 | |
f6af4394 |
581 | (see fc5be80860 for an example). |
7277a900 |
582 | |
f6af4394 |
583 | =item * |
7277a900 |
584 | |
f6af4394 |
585 | Make sure any recent F<pod/perlhist.pod> entries are copied to |
586 | F<perlhist.pod> on other branches; typically the RC* and final entries, |
587 | e.g. |
7277a900 |
588 | |
f6af4394 |
589 | 5.8.9-RC1 2008-Nov-10 |
590 | 5.8.9-RC2 2008-Dec-06 |
591 | 5.8.9 2008-Dec-14 |
7277a900 |
592 | |
6e40fbf9 |
593 | =item * |
594 | |
595 | Remind the current maintainer of C<Module::CoreList> to push a new release |
596 | to CPAN. |
597 | |
7277a900 |
598 | =back |
599 | |
600 | =head1 SOURCE |
601 | |
f6af4394 |
602 | Based on |
603 | http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2009-05/msg00608.html, |
604 | plus a whole bunch of other sources, including private correspondence. |
7277a900 |
605 | |
606 | =cut |
607 | |