<commit_before># Copyright (C) 2007, The Perl Foundation.
# $Id$

=head1 Release Instructions

To prepare a release:

=over 4

=item 0.

Announce to parrot-porters and #parrot at least a couple days in advance,
asking if there are any showstopping bugs. You might also select a name
for your release (e.g., perhaps select a name from
L<http://en.wikipedia.org/wiki/List_of_parrots>).

=item 1.

Make sure you're up to date:

 $ svn update

You may want to ask the developer base to stop committing big changes;
it will avoid complications. Or you could create a release branch before
releasing, rather than after. Then you could fold the release-oriented
changes into the trunk once the release is done.

TODO: explain how to do this

=item 2.

Update files with version-specific information:

=over 4

=item a

Increment the version number in the following files:
F<VERSION>, F<parrot.spec>, F<MANIFEST.generated>, F<META.yml>,
F<README>.

Also update the version number, date, and your name in the
following files: F<DEVELOPING>, F<docs/parrothist.pod>,
and F<docs/ROADMAP.pod>

=item b

Update F<ChangeLog>, F<NEWS> with the new version number and any other
changes that have occurred since the last release: Hopefully these files
are being updated as committers work.

=item c

Make sure F<RESPONSIBLE_PARTIES> is still accurate.

=item d

Run C<perl t/harness t/distro/*.t>, and either fix what those tests
complain about, or fix them so they don't complain.

=item e

Update F<PBC_COMPAT>, perhaps by collapsing intra-release entries
into a single entry naming the release.

=item f

Run C<perl tools/dev/pbc_header.pl --upd t/native_pbc/*.pbc>
to update version and fingerprint in the native tests.

=item g

Make sure everything works:

 $ make realclean<commit_msg>small update to release docs<commit_after># Copyright (C) 2007, The Perl Foundation.
# $Id$

=head1 Release Instructions

To prepare a release:

=over 4

=item 0.

Announce to parrot-porters and #parrot at least a couple days in advance,
asking if there are any showstopping bugs. You might also select a name
for your release (e.g., perhaps select a name from
L<http://en.wikipedia.org/wiki/List_of_parrots>).

=item 1.

Make sure you're up to date:

 $ svn update

You may want to ask the developer base to stop committing big changes;
it will avoid complications. Or you could create a release branch before
releasing, rather than after. Then you could fold the release-oriented
changes into the trunk once the release is done.

TODO: explain how to do this

=item 2.

Update files with version-specific information:

=over 4

=item a

Increment the version number in the following files:
F<VERSION>, F<parrot.spec>, F<MANIFEST.generated>, F<META.yml>,
F<README>.

Also update the version number, date, and your name in the
following files: F<DEVELOPING>, F<docs/parrothist.pod>,
and F<docs/ROADMAP.pod>

=item b

Update F<ChangeLog>, F<NEWS> with the new version number and any other
changes that have occurred since the last release: Hopefully these files
are being updated as committers work.

=item c

Make sure F<RESPONSIBLE_PARTIES> is still accurate.

=item d

Configure parrot and run C<perl t/harness t/distro/*.t>, and either fix 
what those tests complain about, or fix them so they don't complain.

=item e

Update F<PBC_COMPAT>, perhaps by collapsing intra-release entries
into a single entry naming the release.

=item f

Run C<perl tools/dev/pbc_header.pl --upd t/native_pbc/*.pbc>
to update version and fingerprint in the native tests.

=item g

Make sure everything works:

 $ make realclean
{'fraction_non_alphanumeric': 0.07419804741980474, 'fraction_numerical': 0.005578800557880056, 'mean_word_length': 4.312592592592592, 'pattern_counts': {'":': 0, '<': 33, '<?xml version=': 0, '>': 33, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4808433', 'n_tokens_mistral': 1159, 'n_tokens_neox': 1089, 'n_words': 514}