Rev 5435: Clarify SRU bug nomination. in file:///home/vila/src/bzr/releases/work/
Vincent Ladeuil
v.ladeuil+lp at free.fr
Fri Sep 24 10:56:50 BST 2010
At file:///home/vila/src/bzr/releases/work/
------------------------------------------------------------
revno: 5435
revision-id: v.ladeuil+lp at free.fr-20100924095650-okd49n2o18q9zkmb
parent: v.ladeuil+lp at free.fr-20100924084344-58h3mujpdbyuobp3
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: work
timestamp: Fri 2010-09-24 11:56:50 +0200
message:
Clarify SRU bug nomination.
-------------- next part --------------
=== modified file 'doc/developers/releasing.txt'
--- a/doc/developers/releasing.txt 2010-09-17 08:05:11 +0000
+++ b/doc/developers/releasing.txt 2010-09-24 09:56:50 +0000
@@ -402,6 +402,30 @@
**After making a bzr stable-release release, nominate the most serious bug
for the appropriate Ubuntu release and subscribe the `ubuntu-sru` team.**
+This requires a couple of tricks (please reconsider and tweak as things
+evolves from one release to the other):
+
+ * create a distro task with the ``Also affects distribution`` button and
+ select ``bzr (Ubuntu)``.
+
+ * change the *URL* to point to ``ubuntu/+source/bzr`` instead of ``bzr``
+ (this is needed if you create the distro task but not if it exists
+ already). You should now be able to click the ``Nominate for release``
+ button and select the right Ubuntu release. As of September 2010, this
+ means:
+
+ * ``maverick`` for the 2.2 series,
+ * ``lucid`` for the 2.1 series,
+ * ``karmic`` for the 2.0 series.
+
+ * Subscribe the ``~ubuntu-sru`` team to the bug.
+
+ * Add a comment targeted to ``~ubuntu-sru`` explaining the expectations
+ (we are targeting running the test suite during the build which, as of
+ September 2010, fails for known reasons that are currently addressed).
+ Search for bugs tagged with ``sru`` for examples and don't forget to tag
+ the bug you selected.
+
See also
--------
More information about the bazaar-commits
mailing list