Rev 6062: Clarify SRUs handling for the RM. in file:///home/vila/src/bzr/releases/work/

[Vincent Ladeuil]

At file:///home/vila/src/bzr/releases/work/

------------------------------------------------------------
revno: 6062
revision-id: v.ladeuil+lp at free.fr-20110905100814-n6f863hsgflczcuu
parent: v.ladeuil+lp at free.fr-20110905095507-tzkmvneustrx7kru
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: work
timestamp: Mon 2011-09-05 12:08:14 +0200
message:
  Clarify SRUs handling for the RM.
-------------- next part --------------
=== modified file 'doc/developers/releasing.txt'
--- a/doc/developers/releasing.txt	2011-09-05 09:55:07 +0000
+++ b/doc/developers/releasing.txt	2011-09-05 10:08:14 +0000
@@ -444,9 +444,15 @@
    targeted at packagers and installer builders (see
    <https://bugs.launchpad.net/launchpad/+bug/645084>).  This is the cue
    for platform maintainers and plugin authors to update their code.  This
-   is done before the general public announcement of the release.
-
-#. Pause for a few days.
+   is done before the general public announcement of the release. 
+
+   The freeze announcement generally guess the date of the official public
+   announcement, for the most recent stable series (the one supported by the
+   installers and most of the distributions) it's generally a few days after
+   the freeze. For older series supported only via SRUs for Ubuntu, we don't
+   control the process as tightly so guessing the date is not appropriate.
+
+#. Pause for a few days. 
 
 
 Publishing the release
@@ -483,7 +489,8 @@
    Once the installers are available, the mail can be sent to the
    ``bazaar-announce`` list too.
 
-   For stable releases, it should also be cc'd to ``info-gnu at gnu.org``,
+   For stable releases (excluding SRUs which are for older stable releases),
+   it should also be cc'd to ``info-gnu at gnu.org``,
    ``python-announce-list at python.org``, ``bug-directory at gnu.org``.
 
    In all cases, it is good to set ``Reply-To: bazaar at lists.canonical.com``,
@@ -519,8 +526,9 @@
    This should be done for beta releases and stable releases. If you do not
    have a Freshmeat account yet, ask one of the existing admins.
 
-   The purpose here is to point users to the latest stable release while still
-   publishing announcements for beta releases.
+   The purpose here is to point users to the latest stable release
+   (i.e. SRUs are excluded) while still publishing announcements for beta
+   releases.
 
    There are several kinds of modifications that could be done there via the
    ``Administration`` box in the lower right area of the page:
@@ -553,7 +561,7 @@
        python setup.py register
 
    Remember to check the results afterward -- this should be done for
-   stable releases but not for beta releases.
+   stable releases but not for beta releases nor SRUs.
 
    To be able to register the release you must create an account on
    <http://pypi.python.org/pypi> and have one of the existing owners of