Permalink
Browse files

More release_guide.pod improvements.

  • Loading branch information...
1 parent 4549f3c commit 48c17910660d0aee080e69e061220b410feba7b4 @pmichaud pmichaud committed Jul 8, 2009
Showing with 13 additions and 0 deletions.
  1. +13 −0 docs/release_guide.pod
View
@@ -101,6 +101,8 @@ As the actual release date nears, review the git log history
to see if any additional items need to be added to the ChangeLog.
This can be conveniently done with "git log --since=yyyy-mm-dd --reverse".
+ $ git commit docs/ChangeLog
+
=item 5.
When it's time to cut the release, create a new release announcement
@@ -111,12 +113,17 @@ some small details about the choice of release name. (If the
details are a bit lengthy, this can often best be done as a separate
section at the bottom of the announcement.)
+ $ git add docs/announce/YYYY-MM
+ $ git commit docs
+
=item 6.
Update the release dates and names at the top of this file
(docs/release-guide.pod). Also improve these instructions if
you find any steps that are missing.
+ $ git commit docs/release-guide.pod
+
=item 7.
Make sure everything compiles and runs from a known clean state:
@@ -128,11 +135,17 @@ Make sure everything compiles and runs from a known clean state:
$ make spectest
Continue adjusting things until make spectest passes as expected.
+Often this means fixing a bug, fudging a test, or removing a
+test from t/spectest.data . Use your best judgement or ask others
+if uncertain what to do here.
=item 8.
Make sure any locally modified files have been pushed back to github.
+ $ git status
+ $ git push
+
=item 9.
Create an initial tarball by entering C<make release VERSION=YYYY-MM>,

0 comments on commit 48c1791

Please sign in to comment.