378
378
documented. If the instructions aren't clear enough, please fix them.
381
Getting the release into Ubuntu
382
-------------------------------
384
(Feel free to propose or add new sections here about what we should do to
385
get bzr into other places.)
387
For the currently-under-development release of Ubuntu, no special action
388
is needed: the release should be picked by Debian and synced from there into
391
Releases off stable bzr branches should go in to the ``-updates`` of the
392
Ubuntu release that originally contained that branch. (Ubuntu Lucid had
393
bzr 2.2.0, so should get every 2.2.x update.) This means going through
394
the `SRU (Stable Release Updates)
395
<https://wiki.ubuntu.com/StableReleaseUpdates>`__ process.
397
As of September 2010, bzr has applied to the technical board to be added
398
to the `MicroReleaseExceptions
399
<https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions>`__
400
category so that whole bugfix releases can more easily be approved.
402
**After making a bzr stable-release release, nominate the most serious bug
403
for the appropriate Ubuntu release and subscribe the `ubuntu-sru` team.**
405
This requires a couple of tricks (please reconsider and tweak as things
406
evolves from one release to the other):
408
* create a distro task with the ``Also affects distribution`` button and
409
select ``bzr (Ubuntu)``.
411
* change the *URL* to point to ``ubuntu/+source/bzr`` instead of ``bzr``
412
(this is needed if you create the distro task but not if it exists
413
already). You should now be able to click the ``Nominate for release``
414
button and select the right Ubuntu release. As of September 2010, this
417
* ``maverick`` for the 2.2 series,
418
* ``lucid`` for the 2.1 series,
419
* ``karmic`` for the 2.0 series.
421
* Subscribe the ``~ubuntu-sru`` team to the bug.
423
* Add a comment targeted to ``~ubuntu-sru`` explaining the expectations
424
(we are targeting running the test suite during the build which, as of
425
September 2010, fails for known reasons that are currently addressed).
426
Search for bugs tagged with ``sru`` for examples and don't forget to tag
427
the bug you selected.