Rev 4646: Mention creating the news series when changing the major or minor part of in file:///home/vila/src/bzr/bugs/releasing-clarified/

[Vincent Ladeuil]

At file:///home/vila/src/bzr/bugs/releasing-clarified/

------------------------------------------------------------
revno: 4646
revision-id: v.ladeuil+lp at free.fr-20090828160345-6jygi3z5q4g24ra3
parent: v.ladeuil+lp at free.fr-20090828150047-su0w9kdfv9z0hx0q
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: releasing-clarified
timestamp: Fri 2009-08-28 18:03:45 +0200
message:
  Mention creating the news series when changing the major or minor part of
  the release in the version number.
-------------- next part --------------
=== modified file 'doc/developers/releasing.txt'
--- a/doc/developers/releasing.txt	2009-08-28 15:00:47 +0000
+++ b/doc/developers/releasing.txt	2009-08-28 16:03:45 +0000
@@ -296,7 +296,9 @@
 
 As soon as you change the version number in trunk, make sure you have
 created the corresponding milestone to ensure the continuity in bug
-targeting or nominating.
+targeting or nominating. Depending on the change, you may even have to
+create a new series (if your change the major or minor release number), in
+that case go to `Starting a cycle` and follow the instructions from there.
 
 You should also merge (not pull) the release branch into
 ``lp:~bzr/bzr/current``, so that branch contains the current released code
@@ -312,7 +314,7 @@
 candidate, you're not finished, another beta or candidate or hopefully a
 final release is still to come.
 
-The process is the same as for the first release, goto `Starting the
+The process is the same as for the first release, go to `Starting the
 release phase`_ and follow the instructions again. Some details changed
 between beta, candidate and final releases, but they should be
 documented. If they aren't clear enough to your taste, fix them.