← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/developers/releasing.txt

  • Committer: Canonical.com Patch Queue Manager
  • Date: 2010-09-21 08:17:16 UTC
  • mfrom: (5430.5.1 doc)
  • Revision ID: pqm@pqm.ubuntu.com-20100921081716-phuyp6i3ull8eng1
(spiv) Add a brief explanation/reminder to do SRUs after we do a
 stable-series release. (Martin Pool)

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/releasing.txt
378
378
documented. If the instructions aren't clear enough, please fix them.
379
379
 
380
380
 
 
381
Getting the release into Ubuntu
 
382
-------------------------------
 
383
 
 
384
(Feel free to propose or add new sections here about what we should do to
 
385
get bzr into other places.)
 
386
 
 
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
 
389
Ubuntu.
 
390
 
 
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.   
 
396
 
 
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.
 
401
 
 
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.**
 
404
 
 
405
 
381
406
See also
382
407
--------
383
408