Author: rgrjr
Date: Tue Aug 19 19:52:14 2008
New Revision: 30369
Modified:
trunk/docs/project/release_manager_guide.pod
Log:
[DOCS] Update release publicity instructions:
* docs/project/release_manager_guide.pod:
+ Split item 9 into three: (9) compose the announcement; (10) add it
to parrotcode.org; and (11) publicize it everywhere else. This
gives updating parrotcode.org more priority, and makes its subtasks
harder to ignore (I almost didn't see the /.htredirects bit, even
though I should have remembered it was there).
+ In the process, say that LWN.net just needs a text/plain mailing.
+ Add an Emacs "Local Variables:" section.
+ "Saturday" is capitalized.
Modified: trunk/docs/project/release_manager_guide.pod
==============================================================================
--- trunk/docs/project/release_manager_guide.pod (original)
+++ trunk/docs/project/release_manager_guide.pod Tue Aug 19 19:52:14 2008
@@ -71,7 +71,7 @@
=item C<bugday.date>
-Enter the date of the saturday before the next release.
+Enter the date of the Saturday before the next release.
=item C<rt.tracking>
@@ -189,51 +189,75 @@
=item 9.
-Compose and send out the announcements -- parrot-porters, perl6-language,
-perl6-announce, perl5-porters, use Perl, Perl Monks, etc. Don't forget to
-include the next scheduled release date.
-
-Use F<tools/util/crow.pir> to make this part easier. You can specify the
-format of your announcments like so:
+Compose the release announcement. Use F<tools/util/crow.pir> to make
+this part easier. You can specify the format of your announcements like so:
$ ./parrot tools/util/crow.pir --type=text
$ ./parrot tools/util/crow.pir --type=html
-Take the screen output and paste it into the application you need. HTML
-works well for use Perl and PerlMonks, and text for the rest.
+Take the screen output and paste it into the application you need. HTML
+works well for use Perl and PerlMonks, and text for the rest. It is not a
+bad idea to add a "highlights" section to draw attention to major new
+features, just be sure to say the same thing in both text and HTML versions.
+
+=item 10.
+
+Update the website. The svn repository for the website is at
+L<https://svn.perl.org/perl.org/docs/live/parrotcode>.
=over 4
=item a
-Submit the use Perl announcement story to Slashdot, Newsforge, LWN.net, etc.
-Don't forget to set a Reply-To: or Followup-To: header, if your mail
-client lets you.
+Add the release announcement to news/[year]/Parrot-[release].html.
+There's some additional stuff needed at the top of the file; use one of the
+old announcements as a guide.
=item b
-Modify the topic on #parrot, e.g.:
-
- /topic #parrot Parrot 0.4.8 Released | http://parrotcode.org/
+Update the top-level C<index.html> page. (The old mini-announcement may be
+commented out).
=item c
-Update the wiki frontpage at
L<http://www.perlfoundation.org/parrot/index.cgi?parrot>.
-Update the next planned release date on the wiki at
L<http://www.perlfoundation.org/parrot/index.cgi?release_schedule_2008>.
+Update C</.htredirects> to point to the proper CPAN URL.
-=item d
+=back
-Update the website. The svn repository for the website is at
-L<https://svn.perl.org/perl.org/docs/live/parrotcode>.
+If your name is Allison, Will, or chromatic, you will be able to commit these
+changes yourself; be sure to test locally in combust before pushing the update
+out. Otherwise, make the changes in your working copy and send a patch to one
+of the anointed.
-Add a release announcement to news/[year]/Parrot-[release].html.
-Update C</index.html> (The old mini-announcement may be commented out).
-Update C</.htredirects> to point to the proper CPAN URL.
+=item 11.
+
+Publicize the release by publishing the announcement through the
+following channels (and any others you can think of):
+
+=over 4
+
+=item a
+
+Send a text email to parrot-porters, perl6-language, perl6-announce,
+perl5-porters, etc. You should also include LWN.net in this mailing; email to
+C<lwn> at that domain.
+
+=item b
+
+Submit the use Perl announcement story to use Perl, Perl Monks, Slashdot,
+Newsforge, etc. Don't forget to set a Reply-To: or Followup-To: header, if
+your mail client lets you.
+
+=item c
+
+Modify the topic on #parrot, e.g.:
+
+ /topic #parrot Parrot 0.4.8 Released | http://parrotcode.org/
+
+=item d
-If your name is Allison, Will, or chromatic, you will be able to
-commit these changes yourself; be sure to test locally in combust
-before pushing the update out. Otherwise, prepare the changes and
-send a patch to one of the anointed.
+Update the wiki frontpage at
L<http://www.perlfoundation.org/parrot/index.cgi?parrot>.
+Update the next planned release date on the wiki at
L<http://www.perlfoundation.org/parrot/index.cgi?release_schedule_2008>.
=item e
@@ -241,13 +265,13 @@
=back
-=item 10.
+=item 12.
Close any release-related tickets in RT. If they are not yet resolved,
migrate the critical ones to the next milestone release ticket.
Non-critical unresolved tickets can be simply unlinked.
-=item 11.
+=item 13.
You're done! Help yourself to a beer, cola, or other celebratory drink.
@@ -329,3 +353,8 @@
- December 16th, 2008 - Andrew Whitworth
=cut
+
+__END__
+Local Variables:
+ fill-column:78
+End:
