[svn:parrot] r42546 - trunk/docs/project

barney at svn.parrot.org barney at svn.parrot.org
Tue Nov 17 10:19:37 UTC 2009


Author: barney
Date: Tue Nov 17 10:19:34 2009
New Revision: 42546
URL: https://trac.parrot.org/parrot/changeset/42546

Log:
Moved an announcement to committers into item 0.

Modified:
   trunk/docs/project/release_manager_guide.pod

Modified: trunk/docs/project/release_manager_guide.pod
==============================================================================
--- trunk/docs/project/release_manager_guide.pod	Tue Nov 17 08:52:58 2009	(r42545)
+++ trunk/docs/project/release_manager_guide.pod	Tue Nov 17 10:19:34 2009	(r42546)
@@ -38,6 +38,13 @@
 F<PLATFORMS>, F<RESPONSIBLE_PARTIES>, F<DEPRECATED.pod> and
 L<https://trac.parrot.org/parrot/wiki/Languages>.
 
+On the Saturday before a release you should notify other developers to stop
+committing non-release related code to trunk.  This will help avoid
+complications. They are of course free to commit to branches as much as
+they like. You might also set the topic in #parrot, announcing the 
+time when you plan on starting the release procedure. This will help
+the committers with timing their last minute commits.
+
 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>.
@@ -48,11 +55,6 @@
 
  $ svn update
 
-You should notify other developers the Saturday before a release to stop
-committing non-release related code to trunk.  This will help avoid
-complications. They are of course free to commit to branches as much as
-they like.
-
 =item 2.
 
 Update files with version-specific information:


More information about the parrot-commits mailing list