5 0. Announce to parrot-porters and #parrot at least a couple days in
6 advance, asking if there are any showstopping bugs.
8 1. Make sure you're up to date:
12 You may want to ask the developer base to stop committing big
13 changes; it will avoid complications. Or you could create a release
14 branch before releasing, rather than after. Then you could fold the
15 release-oriented changes into the trunk once the release is done.
16 {{ TODO: explain how to do this }}
18 2. Update files with version-specific information:
20 a. Increment the version number in:
23 - compilers/imcc/main.c
27 b. Change the information in DEVELOPING to reflect this release's
28 version number and date.
32 d. Update ChangeLog, NEWS, docs/ROADMAP.pod, and docs/BROKEN.pod.
34 e. Make sure RESPONSIBLE_PARTIES is still accurate.
36 f. Run "perl t/harness t/distro/*.t", and either fix what those tests
37 complain about, or fix them so they don't complain.
39 g. Update PBC_COMPAT, perhaps by collapsing intra-release entries
40 into a single entry naming the release.
42 h. Run C<perl tools/dev/pbc_header.pl --upd t/native_pbc/*.pbc>
43 to update version and fingerprint in the native tests.
45 i. Make sure everything works:
48 $ perl Configure.pl ...
49 $ make -s all world fulltest
53 4. Make the release tarball:
55 $ make release VERSION=a.b.c
57 ... where a.b.c is the version number. This will create the tarball,
58 named parrot-a.b.c.tar.gz.
60 5. Untar parrot-a.b.c.tar.gz into another area
62 6. Make sure everything works:
68 7. Tag the release as "RELEASE_a_b_c", where a.b.c is the version
71 $ export SVNPARROT=https://svn.perl.org/parrot
72 $ svn copy -m"tagged release a.b.c \
73 "$SVNPARROT/trunk $SVNPARROT/tags/RELEASE_a_b_c
79 9. Compose and send out the announcements -- parrot-porters,
80 perl6-language, perl6-announce, perl5-porters, use Perl, PerlMonks,
81 comp.lang.perl.misc, etc.
83 9a. Submit the use Perl announcement story to Slashdot, Newsforge, etc.
85 Don't forget to set a Reply-To: or Followup-To: header.
87 10. You're done! Help yourself to a beer, cola or other celebratory
92 This document was written after a couple of subtly incorrectly assembled
93 releases--usually when someone forgot to delete DEVELOPING, but at least
94 once where the MANIFEST check failed. The intent of this file is to
95 document what must be done to release so that such mistakes don't happen
100 Appendix [1] parrot repository layout as of end of Apr 2005:
107 $ svn ls $SVNPARROT/tags