4
4
This document describes the processes for making and announcing a Bazaar
5
5
release, and managing the release process. This is just one phase of the
6
`overall development cycle <http://doc.bazaar-vcs.org/developers/cycle.html>`_,
7
but it's the most complex part.
8
This document gives a checklist you can follow from start to end in one
6
`overall development cycle
7
<http://doc.bazaar.canonical.com/developers/cycle.html>`_, (go re-read this
8
document to ensure it hasn't been updated since you last read it) but it's
11
If you're doing your first release you can follow this document and read
12
each step explanation. It's also a good practice to read it for any release
13
to ensure you don't miss a step and to update it as the release process
11
16
If you're helping the Release Manager (RM) for one reason or another, you
12
17
may notice that he didn't follow that document scrupulously. He may have
13
18
good reasons to do that but he may also have missed some parts.
15
Follow the document yourself and don't hesitate to create the missing
16
milestones for example (we tend to forget these ones a lot).
26
#. PQM access rights (or you won't be able to land any change)
24
28
#. Download the pqm plugin and install it into your ``~/.bazaar/plugins``::
26
30
bzr branch lp:bzr-pqm ~/.bazaar/plugins/pqm
32
#. Alternatively, you can download and install ``lp:hydrazine`` (the main
33
difference is that hydrazine requires the branch to land to be hosted on
39
In this document, we're talking about source releases only, packages and
40
installers are built from this but we won't talk about them here.
42
Every release is part of a series, ``bzr-2.4.1`` is part of series ``2.4``.
44
We do two different kind of releases: the betas releases and the stable
45
releases for a given series.
47
For a given series, releases will be done to deliver new versions of bzr to
48
different kinds of users:
50
#. beta releases: named ``x.ybn`` where ``x.y`` is the series and ``n``
51
starts at 1 and is incremented. These releases are targeted to beta
52
testers who don't want to run from source but are interested in features
55
#. stable releases: name ``x.y.z`` where ``x.y.`` is the series and ``z``
56
starts at 1 and is incremented. These releases are targeted at people
57
that want bugfixes only and no new features.
60
Differences in the release process between beta and stable release will be
61
mentioned when needed.
66
As of July 2011, we maintain four series (and one that is about to be EOLed).
67
Concurrently releasing them all at the same time makes it harder to shorten
68
the delay between the source availability and the package building longer
69
than necessary (we delay the official announcement until most of our users
70
can install the new release).
72
In order to continue to do time-based releases, we need to plan the
73
releases by series to minimize the collisions. In the end, it's the Release
74
Manager call to decide whether he prefers to do all releases at once
75
though, so the rules presented here are a conservative approach.
77
We want to respect the following rules:
79
#. as much as possible releases should not disturb development, and
80
ongoing development should not disturb releases,
82
#. the most recent development series should release once a month during
83
the beta period (see `Development cycles <cycle.html>`_ for more
86
#. the most recent stable series should release every other month (based
87
on the amount of bug fixes, this can be shorter or longer depending on
90
#. previous series should release on a regular basis without interfering
91
with the most recent series with a decreasing order of priority (again
92
this should be based on bugs importance and user feedback),
94
#. the death of a series should be planned ahead of time. 6 months should
95
give enough time to our users to migrate to a more recent series. This
96
doesn't mean we will make a release at the end of the series, just that
97
before the end date we *could* possibly put out another release if
98
there was a sufficiently important fix. Beyond that date, we won't
99
even land changes on that branch (unless something causes a miraculous
102
#. there should not be more than 2 releases in the same week (but the
103
Release Manager is free to ignore this (get in touch with packagers
106
#. the series are aligned with Ubuntu releases for convenience since we
107
create a new series every 6 months. This means that we support the
108
stable series for 18 months. Note that we also propose the most recent
109
stable series via the stable PPA but that the SRU processs allow us to
110
reach a wider audience.
112
At the start of a series cycle
113
==============================
115
To start a new series cycle:
117
#. Create a new series ``x.y`` at <https://launchpad.net/bzr/+addseries>.
119
#. Add milestones at <https://launchpad.net/bzr/x.y/+addmilestone> to that
120
series for the beta releases and the stable series mentioning their
121
expected dates. Only the milestone associated to the next release in
122
this series should be left active to avoid clutter when targeting bugs.
124
#. If you made a new series, you will need to create a new pqm-controlled
125
branch for this release series. This branch will be used only from the
126
first non-beta release onwards. It needs to be created by a Canonical
127
sysadmin (ask the core devs for instructions or to do it for you).
129
#. Start a new release-notes file::
131
cd doc/en/release-notes
132
cp series-template.txt bzr-x.y.txt # e.g. bzr-2.3.txt
135
#. Start a new whats-new file::
138
cp template.txt bzr-x.y.txt # e.g. bzr-2.6.txt
142
At the start of a release cycle
143
===============================
32
145
To start a new release cycle:
34
#. Create a new series at <https://launchpad.net/bzr/+addseries>. There is one
35
series for every *x.y* release.
37
#. Go to the series web page at <https://launchpad.net/bzr/x.y>
39
#. Create a new release at
40
<https://launchpad.net/bzr/x.y/+addrelease> and add
41
information about this release. We will not use it yet, but it
42
will be available for targeting or nominating bugs.
44
#. We create a new pqm-controlled branch for this release series, by
45
asking a Canonical sysadmin.
46
This branch means that from the first release beta or candidate onwards,
47
general development continues on the trunk, and only
48
specifically-targeted fixes go into the release branch.
50
#. Add milestones at <https://edge.launchpad.net/bzr/x.y/+addmilestone> to
51
that series for the beta release, release candidate and the final release,
52
and their expected dates.
54
#. Update the version number in the ``bzr`` script, and the
55
``bzrlib/__init__.py`` file. Make sure there is always a corresponding
56
milestone when you change that version number.
58
#. Add a new section at the top of ``NEWS`` about the new release,
59
including its version number and the headings from
60
``NEWS-template.txt``.
62
147
#. Send mail to the list with the key dates, who will be the release
63
148
manager, and the main themes or targeted bugs. Ask people to nominate
64
149
objectives, or point out any high-risk things that are best done early,
65
150
or that interact with other changes. This is called the metronome mail
66
151
and is described in `Development cycles <cycle.html>`_.
68
#. Make a local branch for preparing this release. (Only for the first
69
release in a series, otherwise you should already have a branch.) ::
71
bzr branch trunk prepare-1.14
153
#. Make a local branch to prepare the release::
155
bzr branch lp:bzr/x.y x.y-dev
157
If you're doing your first beta release, branch from trunk::
159
bzr branch lp:bzr x.y-dev
161
Note that you will generally reuse the same branch for all releases in a
73
164
#. Configure pqm-submit for this branch, with a section like this (where
74
x.y is the version to release).
75
``~/.bazaar/locations.conf``::
165
``x.y`` is the series for your release). **Or use hydrazine for easier
166
setup** ``~/.bazaar/locations.conf``::
77
[/home/mbp/bzr/prepare-x.y]
168
[/home/mbp/bzr/x.y-dev]
78
169
pqm_email = Canonical PQM <pqm@bazaar-vcs.org>
79
170
submit_branch = http://bazaar.launchpad.net/~bzr-pqm/bzr/x.y
80
171
parent_branch = http://bazaar.launchpad.net/~bzr-pqm/bzr/x.y
81
public_branch = http://bazaar.example.com/prepare-x.y
172
public_branch = http://bazaar.example.com/x.y-dev
82
173
submit_to = bazaar@lists.canonical.com
83
174
smtp_server = mail.example.com:25
85
Please see <http://doc.bazaar-vcs.org/developers/HACKING.html#an-overview-of-pqm>
176
Please see <http://doc.bazaar.canonical.com/developers/HACKING.html#an-overview-of-pqm>
86
177
for more details on PQM
179
#. Update the version number in the ``bzr`` script, and the
180
``bzrlib/__init__.py`` file::
182
version_info = (x, y, z, 'dev', 0)
184
#. Add a new section at the top of the current release notes (in
185
``doc/en/release-notes``) about the new release, including its version
186
number and the headings from ``release-template.txt``.
188
#. Update the "What's New" documents in ``doc/en/whats-new``.
190
#. Make sure a milestone exists for your release and that it is active,
191
<https://launchpad.net/bzr/x.y> lists the existing milestones,
192
<https://launchpad.net/bzr/x.y/x.y.z/+edit> allows you to toggle the
195
#. Commit this and send it to PQM.
198
Doing a particular release
199
==========================
201
Update the source code
202
----------------------
204
#. Check that there is a milestone for the release you're doing. If there
205
is no milestone it indicates a process problem - make the milestone but
206
also mail the list to raise this issue in our process. Milestones are
207
found at <https://launchpad.net/bzr/+milestone/x.y.z>.
209
#. Merge into your branch all previous stable series fixes that haven't been
210
merged yet. For example, if you're releasing 2.5.x, make sure the fixes
211
on 2.4, 2.3, etc have already been merged up::
215
and commit that merge in its own commit. This should happen only if the
216
devs landing changes in previous releases forgot to merge them up. Since
217
this can slow down the freeze, feel free to gently remind them about
218
their duties ;) If you feel unsafe resolving the conflicts or it's too
219
time consuming, contact the related devs and skip this merge.
88
221
#. In the release branch, update ``version_info`` in ``./bzrlib/__init__.py``.
89
222
Make sure the corresponding milestone exists.
90
223
Double check that ./bzr ``_script_version`` matches ``version_info``. Check
91
the output of ``bzr --version``.
224
the output of ``./bzr --version``.
93
226
For beta releases use::
95
version_info = (2, 1, 0, 'beta', 1)
98
For release candidates use::
100
version_info = (2, 0, 1, 'candidate', 1)
103
Starting the release phase
104
--------------------------
106
#. Create a new milestone at <https://launchpad.net/bzr/x.y/+addmilestone>
107
for the beta release or release candidate if you haven't already.
109
#. Add the date and release number to ``./NEWS``
111
Depending on whether you're doing a beta or a bugfix release, you'll
112
have to create a NEWS section for your release in the right
113
place. Most of the time, the new section is at the top of the file
114
(look what have been done for the various 2.0x and 2.1.0bx releases).
115
The rule is to keep the sections sorted by date. You'll need to be
116
cautious when merging back to trunk to respect that.
118
#. To check that all bugs mentioned in ``./NEWS`` are actually marked as
119
closed in Launchpad, you can run ``tools/check-newsbugs.py``::
121
./tools/check-newsbugs.py NEWS
123
(But note there can be some false positives, and this script may be
124
flaky <https://bugs.edge.launchpad.net/bzr/+bug/354985>. Don't let
125
this slow you down too much.)
127
#. Summarize into one or two paragraphs what's new in this release.
228
version_info = (2, 5, 0, 'beta', SERIAL)
232
version_info = (2, 5, 0, 'beta', 5)
234
For stable releases use::
236
version_info = (2, 5, 0, 'final', 0)
238
#. Update the ``./doc/en/release-notes/`` section for this release.
240
Check that all news entries related to this release have been added in
241
the right section. For example, if you're releasing 2.5b5, the following
242
command should display a a single chuk diff for the 2.5b5 release::
244
bzr diff -rbzr-2.5b4.. doc/en/release-notes/bzr-2.5.txt
246
Fill out the date and a description of the release under the existing
247
header (the diff above will help you summarizing). If there isn't one,
248
follow the instructions above for using the ``release-template.txt`` file
249
and remind people that they should document their changes there ;)
251
See *2.5b5* or similar for an example of what this looks like.
253
#. Add or check the summary of the release into the "What's New" document.
255
#. To check that all bugs mentioned in the release notes are actually
256
marked as closed in Launchpad, you can run
257
``tools/check-newsbugs.py``::
259
./tools/check-newsbugs.py doc/en/release-notes/bzr-x.y.txt
261
As of 2011-07-18, all bugs mentioned in the output of the script requires
262
some sort of intervention (either changing the status if it's not 'Fix
263
Released' or setting a different milestone if the bug hasn't been
264
fixed). A few false positives may remain in the older series, don't let
265
this slow you down too much. This script accepts options you may find
266
useful, use ``./tools/check-newsbugs.py`` to display its usage (``-w``
267
will open each bug in your browser for example).
269
#. For beta releases update the translation template::
271
BZR_PLUGIN_PATH=-site make po/bzr.pot
273
This is especially important for the final beta release which is when
274
translations are frozen and translators are requested (see `The final
275
beta - branching and translations`_) to make the translations.
277
#. For stable releases update the translations::
279
bzr merge lp:~bzr-core/bzr/bzr-translations-export-x.y
129
281
#. Commit these changes to the release branch, using a command like::
131
bzr commit -m "Release 1.14."
283
bzr commit -m "Release 2.3.1"
133
285
The diff before you commit will be something like::
135
=== modified file 'NEWS'
136
--- NEWS 2008-09-17 23:09:18 +0000
137
+++ NEWS 2008-09-23 16:14:54 +0000
145
+This release includes many bug fixes and a few performance and feature
146
+improvements. ``bzr rm`` will now scan for missing files and remove them,
147
+like how ``bzr add`` scans for unknown files and adds them. A bit more
148
+polish has been applied to the stacking code. The b-tree indexing code has
149
+been brought in, with an eye on using it in a future repository format.
150
+There are only minor installer changes since bzr-1.7rc2.
152
bzr 1.7rc2 2008-09-17
153
---------------------
156
=== modified file 'bzrlib/__init__.py'
157
--- bzrlib/__init__.py 2008-09-16 21:39:28 +0000
158
+++ bzrlib/__init__.py 2008-09-23 16:14:54 +0000
160
# Python version 2.0 is (2, 0, 0, 'final', 0)." Additionally we use a
161
# releaselevel of 'dev' for unreleased under-development code.
163
-version_info = (1, 7, 0, 'candidate', 2)
164
+version_info = (1, 7, 0, 'final', 0)
167
# API compatibility version: bzrlib is currently API compatible with 1.7.
287
=== modified file 'bzrlib/__init__.py'
288
--- bzrlib/__init__.py 2011-02-09 06:35:00 +0000
289
+++ bzrlib/__init__.py 2011-03-10 10:24:47 +0000
291
# Python version 2.0 is (2, 0, 0, 'final', 0)." Additionally we use a
292
# releaselevel of 'dev' for unreleased under-development code.
294
-version_info = (2, 3, 1, 'dev', 0)
295
+version_info = (2, 3, 1, 'final', 0)
297
# API compatibility version
298
api_minimum_version = (2, 3, 0)
300
=== modified file 'doc/en/release-notes/bzr-2.3.txt'
301
--- doc/en/release-notes/bzr-2.3.txt 2011-03-09 08:30:16 +0000
302
+++ doc/en/release-notes/bzr-2.3.txt 2011-03-10 10:40:47 +0000
307
-:2.3.1: NOT RELEASED YET
309
-External Compatibility Breaks
310
-*****************************
312
-.. These may require users to change the way they use Bazaar.
317
-.. New commands, options, etc that users may wish to try out.
322
-.. Improvements to existing commands, especially improved performance
323
- or memory usage, or better results.
326
+This is a bugfix release. Upgrading is recommended for all users of earlier
332
=== modified file 'doc/en/whats-new/whats-new-in-2.3.txt'
333
--- doc/en/whats-new/whats-new-in-2.3.txt 2011-02-03 16:29:18 +0000
334
+++ doc/en/whats-new/whats-new-in-2.3.txt 2011-03-10 11:10:36 +0000
336
improvements made to the core product, it highlights enhancements within the
337
broader Bazaar world of potential interest to those upgrading.
339
-Bazaar 2.3.0 is fully compatible both locally and on the network with 2.0 2.1,
340
-and 2.2, and can read and write repositories generated by all previous
341
+Bazaar 2.3.1 includes all the fixes in the un-released 2.0.7, 2.1.4 and 2.2.5
342
+versions that weren't included in 2.3.0 and fixes some bugs on its own.
344
+See the :doc:`../release-notes/index` for details.
346
+Bazaar 2.3 is fully compatible both locally and on the network with 2.0, 2.1,
347
+and 2.2. It can read and write repositories generated by all previous
169
353
#. Tag the new release::
173
#. Push those changes to a bzr reposistory that is public and accessible on
174
the Internet. PQM will pull from this repository when it attempts to merge
175
your changes. Then submit those changes to PQM for merge into the
176
appropriate release branch::
357
#. Push those changes to a bzr branch that is public and accessible on the
358
Internet. PQM will pull from this branch when it attempts to merge your
359
changes. Then submit those changes to PQM for merge into the appropriate
179
bzr pqm-submit -m "(mbp) prepare 1.14"
363
bzr pqm-submit -m "(vila) Release 2.3.1 (Vincent Ladeuil)"
365
Note that ``bzr push`` should mention updating one tag (which you just
366
created). If it doesn't, double-check that you created (and pushed) this
371
bzr lp-propose -m "Release 1.14" --approve lp:bzr/1.14
181
374
#. When PQM succeeds, pull down the master release branch.
191
384
#. Now we'll try expanding this tarball and running the test suite
192
385
to check for packaging problems::
194
make check-dist-tarball
196
You may encounter failures while running the test suite caused
197
by your locally installed plugins. Use your own judgment to
198
decide if you can release with these failures. When in doubt,
199
disable the faulty plugins one by one until you get no more
387
make check-dist-tarball | subunit2pyunit
389
You may encounter failures while running the test suite caused by your
390
locally installed plugins. Use your own judgment to decide if you can
391
release with these failures. When in doubt, disable the faulty plugins
392
one by one until you get no more failures. Alternatively, you can use
393
``BZR_DISABLE_PLUGINS`` or ``BZR_PLUGIN_PATH=-site`` to disable one or
396
Until <http://pad.lv/839461> is fixed, you may encounter issues if you
397
cut a release for old stable branches (<= 2.2) and use a more recent
398
OS/distro. If that's the case, check the bug status and use the following
399
workaround if no fix is available::
401
export TTPATH=<local branch of lp:testtools -r 0.9.2>
402
export SUPATH=<local branch of lp:subunit -r 0.0.6>
403
PYTHONPATH=$TTPATH:$SUPATH/python PATH=$SUPATH/filters:${PATH} BZR_PLUGIN_PATH=-site make check-dist-tarball PYTHON=python2.6 | subunit2pyunit
405
Remember that PQM has just tested everything too, this step is
406
particularly testing that the pyrex extensions, which are updated
407
by your local pyrex version when you run make dist, are in good
203
411
Publishing the source tarball
204
412
-----------------------------
206
#. Go to the relevant milestone page in Launchpad.
208
#. Within that release, upload the source tarball and the GPG
209
signature. Or, if you prefer, use the
210
``tools/packaging/lp-upload-release`` script to do this.
414
#. Go to the relevant <https://launchpad.net/bzr/x.y> series page in Launchpad.
416
#. Create a release of the milestone, and upload the source tarball and
417
the GPG signature. Or, if you prefer, use the
418
``tools/packaging/lp-upload-release`` script to do this. Note that
419
this changes what the download widget on the Launchpad bzr home
420
page shows, so don't stop the release process yet, or platform binary
421
installers won't be made and the download list will stay very small!
422
<https://bugs.launchpad.net/launchpad/+bug/586445>
425
Kick off the next cycle
426
-----------------------
428
From that point, there is no possible return, the tarball has been uploaded
429
so you can relax a bit.
431
You're still holding a "social" lock on the launchpad branch though. Until
432
your start the next cycle, nobody should land anything on this branch. If
433
they do, they either targeted the wrong branch or didn't update the news
434
file correctly, so the sooner the branch is opened again, the better.
436
This matters more for ``lp:bzr`` than for ``lp:bzr/x.y``, ``lp:bzr`` should
437
always be open for landing, so you should do `At the start of a release
438
cycle`_ as soon as possible (i.e. update the version number in ``bzr`` and
439
``bzrlib/__init__``, create/update the news files and create/update the
440
milestone for the next relase).
442
You may also need to do `At the start of a series cycle`_ if you're starting
445
The final beta - branching and translations
446
-------------------------------------------
448
A word of caution: the instructions above works well for all releases but
449
there is one special case that requires a bit more care: when you release
450
the *last* beta for a given ``x.y`` series (from trunk aka lp:bzr), you need
451
to setup *two* branches for the next cycle:
453
#. ``lp:bzr`` needs to be opened for the next *series* ``x.(y+1)``.
455
#. ``lp:bzr/x.y`` needs to be opened for the next *release* ``x.y.0`` in the
456
series. Since this is first real use of ``lp:bzr/x.y``, this is also the
457
deadline for the PQM branch to be created.
459
Both are important as ``lp:bzr`` should remain open so any change can be
460
landed, ``lp:bzr/x.y`` on the other hand should be ready to receive bug
463
``lp:bzr`` is generally more important as the bug fixes on ``lp:bzr/x.y``
464
won't be released sooner than a month from now whereas people may already
465
been waiting to land on ``lp:bzr``.
469
#. Open ``lp:bzr`` for ``x.(y+1)``
471
#. Create or update the ``x.y`` PQM branch based on whatever revision you
472
want to release. Since it takes time to create the PQM branch for the new
473
series you should plan to get it created a few days before you need it
474
and seed it with the revision from trunk you want to base your release of
475
(ask a LOSA for pulling this revision from trunk and pushing it to the
476
series branch (``lp:bzr/x.y``) when you're ready).
478
#. Release ``x.y.0`` from ``lp:bzr/x.y``
480
#. Open ``lp:bzr/x.y`` for bug fixes
482
You also need to ensure Launchpad is set up to import/export translations
483
for the new branch and inform translators.
485
#. Push the last beta release to a new branch::
487
bzr push lp:~bzr-core/bzr/bzr-translations-export-x.y
489
#. On the translations series synchronization settings page
490
<https://translations.launchpad.net/bzr/x.y/+translations-settings>
491
turn on ``Import template files`` then for exports click ``Choose a
492
target branch`` and point it at the branch you just pushed.
494
#. E-mail translators to announce that the forthcoming stable release of bzr
495
is ready for translations. Send to
496
``launchpad-translators@lists.launchpad.net`` and
497
``ubuntu-translators@lists.ubuntu.com``.
499
#. The series is now frozen for strings and API, see below for adding
500
that to the announcement.
213
502
Announcing the source freeze
214
503
----------------------------
216
#. Post to the ``bazaar`` list, saying that the source has been frozen.
217
This is the cue for platform maintainers and plugin authors to update
218
their code. This is done before the general public announcement of the
505
#. Post to the ``bazaar@lists.canonical.com`` and
506
``bzr-packagers@list.launchpad.net`` lists, saying that the source has
507
been frozen. Be extra clear that this is only a *source* release targeted
508
at packagers and installer builders (see
509
<https://bugs.launchpad.net/launchpad/+bug/645084>). This is the cue for
510
platform maintainers and plugin authors to update their code. This is
511
done before the general public announcement of the release.
513
The freeze announcement generally guess the date of the official public
514
announcement, for the most recent stable series (the one supported by the
515
installers and most of the distributions) it's generally a few days after
516
the freeze. For older series supported only via SRUs for Ubuntu, we don't
517
control the process as tightly so guessing the date is not appropriate.
519
For the final beta release include in your announcement a notice of
520
API and translation freezes nothing that public methods should not
521
be removed or changed and strings should not be added or changed.
523
#. Pause for a few days.
222
526
Publishing the release
318
638
Merging the released code back to trunk
319
639
---------------------------------------
321
Merge the release branch back into the trunk. Check that changes in NEWS
322
were merged into the right sections. If it's not already done, advance
323
the version number in ``bzr`` and ``bzrlib/__init__.py``. Submit this
324
back into pqm for bzr.dev.
641
Merge the release branch back into the trunk. The ``doc/en/release-notes``
642
changes should be merged into the right place because each release series
643
has its own release-notes file, but double-check.
645
If it's not already done, advance the version number in ``bzr`` and
646
``bzrlib/__init__.py``. Submit this back into pqm for bzr.dev.
326
648
As soon as you change the version number in trunk, make sure you have
327
649
created the corresponding milestone to ensure the continuity in bug
328
650
targeting or nominating. Depending on the change, you may even have to
329
651
create a new series (if your change the major or minor release number), in
330
that case go to `Starting a cycle` and follow the instructions from there.
652
that case go to `At the start of a series cycle`_ and follow the
653
instructions from there.
332
You should also merge (not pull) the release branch into
333
``lp:~bzr/bzr/current``, so that branch contains the current released code
336
656
Releases until the final one
337
657
----------------------------
339
Congratulations - you have made your first release. Have a beer
340
or fruit juice - it's on the house! If it was a beta, or
341
candidate, you're not finished yet. Another beta or candidate or
342
hopefully a final release is still to come.
344
The process is the same as for the first release. Goto `Starting the
345
release phase`_ and follow the instructions again. Some details change
346
between beta, candidate and final releases, but they should be
347
documented. If the instructions aren't clear enough, please fix them.
659
Congratulations - you have made your first release. Have a beer or fruit
660
juice - it's on the house! If it was a beta, you're not finished
661
yet. Another beta or hopefully a stable release is still to come.
663
The process is the same as for the first release. Goto `Doing a particular
664
release`_ and follow the instructions again. Some details change between
665
beta and stable releases, but they should be documented. If the instructions
666
aren't clear enough, please fix them.
669
Getting the release into Ubuntu
670
-------------------------------
672
(Feel free to propose or add new sections here about what we should do to
673
get bzr into other places.)
675
For the currently-under-development release of Ubuntu, no special action
676
is needed: the release should be picked by Debian and synced from there into
679
Releases off stable bzr branches should go in to the ``-updates`` of the
680
Ubuntu release that originally contained that branch. (Ubuntu Lucid had
681
bzr 2.2.0, so should get every 2.2.x update.) This means going through
682
the `SRU (Stable Release Updates)
683
<https://wiki.ubuntu.com/StableReleaseUpdates>`__ process.
685
Since September 2010, bzr has received approval by the technical
686
board for the `MicroReleaseExceptions
687
<https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions>`__
688
category so that whole bugfix releases can more easily be
691
Progress on these realeases is tracked on the `SRU wiki
692
<http://wiki.bazaar.canonical.com/UbuntuStableReleaseUpdates>`_
695
**After making a bzr stable-release release, nominate the most serious bug
696
for the appropriate Ubuntu release and subscribe the `ubuntu-sru` team.**
698
This requires a couple of tricks (please reconsider and tweak as things
699
evolves from one release to the other):
701
* create a distro task with the ``Also affects distribution`` button and
702
select ``bzr (Ubuntu)``.
704
* change the *URL* to point to ``ubuntu/+source/bzr`` instead of ``bzr``
705
(this is needed if you create the distro task but not if it exists
706
already). You should now be able to click the ``Nominate for release``
707
button and select the right Ubuntu release. As of September 2010, this
710
* ``oneiric`` for the 2.4 series,
711
* ``natty`` for the 2.3 series,
712
* ``maverick`` for the 2.2 series,
713
* ``lucid`` for the 2.1 series,
715
* Subscribe the ``~ubuntu-sru`` team to the bug.
717
* Add a comment targeted to ``~ubuntu-sru`` explaining the expectations
718
(we are targeting running the test suite during the build which, as of
719
September 2010, fails for known reasons that are currently addressed).
720
Search for bugs tagged with ``sru`` for examples and don't forget to tag
721
the bug you selected.
added
removed
doc/developers/releasing.txt
