Skip to content

Commit

Permalink
add info about release to my CREDITS entry. Update release.json. Revi…
Browse files Browse the repository at this point in the history
…se release_manager_guide.pod with respect to the ops2c bootstrapping steps. That mechanism is complicated enough without the clumsy half-explanation.
  • Loading branch information
Whiteknight committed Apr 19, 2011
1 parent 1cfacea commit 8a1b743
Show file tree
Hide file tree
Showing 3 changed files with 26 additions and 12 deletions.
2 changes: 1 addition & 1 deletion CREDITS
Expand Up @@ -100,7 +100,7 @@ E: yDNA@cpan.org
N: Andrew Whitworth
D: Internals development
D: Documentation
D: Release manager for 0.8.2, 1.3.0, 1.5.0, 2.4.0 and 2.11.0
D: Release manager for 0.8.2, 1.3.0, 1.5.0, 2.4.0, 2.11.0 and 3.3.0
E: wknight8111@gmail.com
U: Whiteknight

Expand Down
22 changes: 18 additions & 4 deletions docs/project/release_manager_guide.pod
Expand Up @@ -49,6 +49,10 @@ You might also select a name (and optionally a quote) for your release.
For example, you could select a name from
L<http://en.wikipedia.org/wiki/List_of_parrots>.

NOTE: Build a recent version of Parrot to have available during the release
to help with bootstrapping. You must have a version of Parrot built and
available to you for some of the subsequent steps.

=item 1.

The day of the release has come.
Expand Down Expand Up @@ -126,10 +130,20 @@ Give yourself credit for the release in F<CREDITS>.

=item f

To have parrot configured and have run C<make> with the old version number is
condition for this step. Run C<./ops2c --core> (or C<make bootstrap-ops>,
ignoring errors) followed by C<make reconfig> and C<make> to update the names
of version-specific internal functions.
This is a bootstrapping step, which requires you to have an existing parrot
executable available, preferrably from the previous release or pre-release
development version from the master branch.

You *must* do this with a previous version of Parrot built before you updated
the VERSION file. You *must* update VERSION before doing this step.

Run C<./ops2c --core> (or C<make bootstrap-ops>, ignoring errors) followed
by C<make reconfig> and C<make> to update the names of version-specific
internal functions.

This step uses the older Parrot to create new ops core files and routines
using the new version number. The released version of Parrot requires these
files and the new VERSION.

=item g

Expand Down
14 changes: 7 additions & 7 deletions tools/release/release.json
@@ -1,9 +1,9 @@
{
"release.version" : "3.2.0",
"release.name" : "Nanday Parakeet",
"release.version" : "3.3.0",
"release.name" : "",
"release.day" : "Tuesday",
"release.date" : "15 March 2011",
"release.nextdate" : "19 April 2011",
"release.date" : "19 April 2011",
"release.nextdate" : "17 May 2011",

"web.root" : "http://parrot.org/",
"web.source" : "download",
Expand All @@ -12,10 +12,10 @@
"web.org_root" : "https://github.com/parrot",

"bugday.day" : "Saturday",
"bugday.date" : "16 April 2011",
"bugday.date" : "14 May 2011",

"wiki.root" : "https://trac.parrot.org/parrot/wiki/",
"wiki.bugday" : "bug_day_2011_04_16",
"wiki.bugday" : "bug_day_2011_05_14",

"ftp.path" : "ftp://ftp.parrot.org/pub/parrot/releases/devel/3.2.0/"
"ftp.path" : "ftp://ftp.parrot.org/pub/parrot/releases/supported/3.3.0/"
}

0 comments on commit 8a1b743

Please sign in to comment.