4
4
This document describes the processes for making and announcing a Bazaar
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
5
release, and managing the release process. This is just one phase of
6
the `overall development cycle
7
<http://doc.bazaar.canonical.com/developers/cycle.html>`_, (go re-read
8
this document to ensure it hasn't been updated) but it's the most
9
complex part. This document gives a checklist you can follow from start
11
12
If you're helping the Release Manager (RM) for one reason or another, you
12
13
may notice that he didn't follow that document scrupulously. He may have
24
25
#. Download the pqm plugin and install it into your ``~/.bazaar/plugins``::
26
27
bzr branch lp:bzr-pqm ~/.bazaar/plugins/pqm
33
As of October 2010, we mantain four series. Concurrently releasing them
34
all at the same time makes it harder to shorten the delay between the
35
source availability and the package building longer than necessary (we
36
delay the official announcement until most of our users can install the new
39
In order to continue to do time-based releases, we need to plan the
40
releases by series to minimize the collisions. In the end, it's the Release
41
Manager call to decide whether he prefers to do all releases at once
42
though, so the rules presented here are a conservative approach.
44
We want to respect the following rules::
46
#. as much as possible releases should not disturb development, and
47
ongoing development should not disturb releases,
49
#. the most recent development series should release once a month during
50
the beta period (see `Development cycles <cycle.html>`_ for more
53
#. the most recent stable series should release every other month (based
54
on the amount of bug fixes, this can be shorter or longer depending on
57
#. previous series should relesase on a regular basis without interfering
58
with the most recent series with a decreasing order of priority (again
59
this should be based on bugs importance and user feedback),
61
#. the death of a series should be planned ahead of time. 6 months should
62
give enough time to our users to migrate to a more recent series. This
63
doesn't mean we will make a release at the end of the series, just that
64
before the end date we _could_ possibly put out another release if
65
there was a sufficiently important fix. Beyond that date, we won't
66
even land changes on that branch (unless something causes a miraculous
69
#. there should not be more than 2 releases in the same week (but the
70
Release Manager is free to ignore this (get in touch with packagers
73
#. the series are aligned with Ubuntu releases for convenience since we
74
create a new series every 6 months. This means that we support the
75
stable series for 18 months. Note that we also propose the most recent
76
stable series via the ppa, so whether we keep supporting LTS directly
77
or via the ppa is still an open question.
80
At the start of a release cycle
81
===============================
32
83
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
85
#. If this is the first release for a given *x.y* then create a new
86
series at <https://launchpad.net/bzr/+addseries>. There is one series
87
for every *x.y* release.
89
#. If you made a new series, create a new pqm-controlled branch for this
90
release series, by asking a Canonical sysadmin. This branch means that
91
from the first release beta or candidate onwards, general development
92
continues on the trunk, and only specifically-targeted fixes go into
95
#. If you made a new series, add milestones at
96
<https://launchpad.net/bzr/x.y/+addmilestone> to that series for
97
the beta release, release candidate and the final release, and their
100
#. Create a new milestone <https://launchpad.net/bzr/x.y/+addmilestone>
101
and add information about this release. We will not use it yet, but it
42
102
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
104
#. Send mail to the list with the key dates, who will be the release
63
105
manager, and the main themes or targeted bugs. Ask people to nominate
64
106
objectives, or point out any high-risk things that are best done early,
82
124
submit_to = bazaar@lists.canonical.com
83
125
smtp_server = mail.example.com:25
85
Please see <http://doc.bazaar-vcs.org/developers/HACKING.html#an-overview-of-pqm>
127
Please see <http://doc.bazaar.canonical.com/developers/HACKING.html#an-overview-of-pqm>
86
128
for more details on PQM
130
#. Update the version number in the ``bzr`` script, and the
131
``bzrlib/__init__.py`` file::
133
version_info = (x, y, z, 'dev', 0)
135
#. If you made a new series, then start a new release-notes file::
137
cd doc/en/release-notes
138
cp series-template.txt bzr-x.y.txt # e.g. bzr-2.3.txt
141
#. Add a new section at the top of the current release notes (in
142
``doc/en/release-notes``) about the new release, including its version
143
number and the headings from ``release-template.txt``.
145
#. Update the "What's New" documents in ``doc/en/whats-new``.
147
#. Commit this and send it to PQM.
150
Doing a particular release
151
==========================
153
Update the source code
154
----------------------
156
#. Check that there is a milestone for the release you're doing. If there
157
is no milestone it indicates a process problem - make the milestone but
158
also mail the list to raise this issue in our process. Milestones are
159
found at <https://launchpad.net/bzr/+milestone/x.y.z>.
88
161
#. In the release branch, update ``version_info`` in ``./bzrlib/__init__.py``.
89
162
Make sure the corresponding milestone exists.
90
163
Double check that ./bzr ``_script_version`` matches ``version_info``. Check
91
164
the output of ``bzr --version``.
93
For beta releases use::
166
For betahttps://code.edge.launchpad.net/~knittl/bzr/fix-inventory-r0/+merge/354985 releases use::
168
version_info = (2, 1, 0, 'beta', SERIAL)
95
172
version_info = (2, 1, 0, 'beta', 1)
98
174
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.
176
version_info = (2, 0, 1, 'candidate', SERIAL)
178
For stable releases use::
180
version_info = (2, 1, 2, 'final', 0)
182
#. Update the ``./doc/en/release-notes/`` section for this release.
184
Fill out the date and a description of the release under the existing
185
header. If there isn't one, follow the instructions above for using the
186
``release-template.txt`` file.
188
See *2.1.1* or similar for an example of what this looks like.
190
#. Add a summary of the release into the "What's New" document.
192
#. To check that all bugs mentioned in the release notes are actually
193
marked as closed in Launchpad, you can run
194
``tools/check-newsbugs.py``::
196
./tools/check-newsbugs.py doc/en/release-notes/bzr-x.y.txt
198
(As of 2011-12-03, only a few false positives remain. Don't let this slow
129
201
#. Commit these changes to the release branch, using a command like::
199
279
disable the faulty plugins one by one until you get no more
282
Remember that PQM has just tested everything too, this step is
283
particularly testing that the pyrex extensions, which are updated
284
by your local pyrex version when you run make dist, are in good
203
288
Publishing the source tarball
204
289
-----------------------------
206
291
#. 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.
293
#. Create a release of the milestone, and upload the source tarball and
294
the GPG signature. Or, if you prefer, use the
295
``tools/packaging/lp-upload-release`` script to do this. Note that
296
this changes what the download widget on the Launchpad bzr home
297
page shows, so don't stop the release process yet, or platform binary
298
installers won't be made and the download list will stay very small!
299
<https://bugs.launchpad.net/launchpad/+bug/586445>
213
302
Announcing the source freeze
214
303
----------------------------
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
305
#. Post to the ``bazaar`` list, saying that the source has been frozen
306
(gone gold). Be extra clear that this is only a *source* release
307
targeted at packagers and installer builders (see
308
<https://bugs.launchpad.net/launchpad/+bug/645084>). This is the cue
309
for platform maintainers and plugin authors to update their code. This
310
is done before the general public announcement of the release.
313
Kick off the next cycle
314
-----------------------
316
#. To let developers work on the next release, do
317
`At the start of a release cycle` now.
319
#. Pause for a few days.
222
322
Publishing the release
227
327
we have a releasable product. The next step is to make it generally
228
328
available to the world.
232
#. Within that release, upload the source tarball and zipfile and the GPG
233
signature. Or, if you prefer, use the
234
``tools/packaging/lp-upload-release`` script to do this.
236
#. Link from http://bazaar-vcs.org/SourceDownloads to the tarball and
239
#. Announce on the `Bazaar website <http://bazaar-vcs.org/>`_.
330
#. Go to the release web page at <https://launchpad.net/bzr/x.y/x.y.z>
332
#. Announce on the `Bazaar website <http://bazaar.canonical.com/>`_.
240
333
This page is edited via the lp:bzr-website branch. (Changes
241
334
pushed to this branch are refreshed by a cron job on escudero.)
243
#. Announce on the `Bazaar wiki <http://bazaar-vcs.org/Welcome>`_.
245
336
#. Check that the documentation for this release is available in
246
<http://doc.bazaar-vcs.org>. It should be automatically build when the
337
<http://doc.bazaar.canonical.com>. It should be automatically build when the
247
338
branch is created, by a cron script ``update-bzr-docs`` on
248
339
``escudero``. As of today (2009-08-27) ``igc`` manually updates the
249
340
pretty version of it.
271
362
The announce mail will look something like this::
273
Subject: bzr x.yy released!
275
<<Summary paragraph from news>>
364
Subject: bzr x.y.z released!
277
366
The Bazaar team is happy to announce availability of a new
278
367
release of the bzr adaptive version control system.
279
368
Bazaar is part of the GNU system <http://gnu.org/>.
370
<<Summary paragraph from news>>
281
372
Thanks to everyone who contributed patches, suggestions, and
284
375
Bazaar is now available for download from
285
http://bazaar-vcs.org/Download as a source tarball; packages
376
https://launchpad.net/bzr/2.x/2.x/ as a source tarball; packages
286
377
for various systems will be available soon.
288
<<NEWS section from this release back to the last major release>>
379
<<release notes from this release back to the last major release>>
290
381
Feel free to tweak this to your taste.
318
410
Merging the released code back to trunk
319
411
---------------------------------------
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.
413
Merge the release branch back into the trunk. The
414
``doc/en/release-notes`` changes should be merged into the right place
415
because each release series has its own release-notes file, but
418
If it's not already done, advance the version number in ``bzr`` and
419
``bzrlib/__init__.py``. Submit this back into pqm for bzr.dev.
326
421
As soon as you change the version number in trunk, make sure you have
327
422
created the corresponding milestone to ensure the continuity in bug
328
423
targeting or nominating. Depending on the change, you may even have to
329
424
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.
425
that case go to `At the start of a release cycle` and follow the instructions from there.
332
427
You should also merge (not pull) the release branch into
333
428
``lp:~bzr/bzr/current``, so that branch contains the current released code
341
436
candidate, you're not finished yet. Another beta or candidate or
342
437
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
439
The process is the same as for the first release. Goto `Doing a
440
particular release`_ and follow the instructions again. Some details change
346
441
between beta, candidate and final releases, but they should be
347
442
documented. If the instructions aren't clear enough, please fix them.
445
Getting the release into Ubuntu
446
-------------------------------
448
(Feel free to propose or add new sections here about what we should do to
449
get bzr into other places.)
451
For the currently-under-development release of Ubuntu, no special action
452
is needed: the release should be picked by Debian and synced from there into
455
Releases off stable bzr branches should go in to the ``-updates`` of the
456
Ubuntu release that originally contained that branch. (Ubuntu Lucid had
457
bzr 2.2.0, so should get every 2.2.x update.) This means going through
458
the `SRU (Stable Release Updates)
459
<https://wiki.ubuntu.com/StableReleaseUpdates>`__ process.
461
As of September 2010, bzr has applied to the technical board to be added
462
to the `MicroReleaseExceptions
463
<https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions>`__
464
category so that whole bugfix releases can more easily be approved.
466
**After making a bzr stable-release release, nominate the most serious bug
467
for the appropriate Ubuntu release and subscribe the `ubuntu-sru` team.**
469
This requires a couple of tricks (please reconsider and tweak as things
470
evolves from one release to the other):
472
* create a distro task with the ``Also affects distribution`` button and
473
select ``bzr (Ubuntu)``.
475
* change the *URL* to point to ``ubuntu/+source/bzr`` instead of ``bzr``
476
(this is needed if you create the distro task but not if it exists
477
already). You should now be able to click the ``Nominate for release``
478
button and select the right Ubuntu release. As of September 2010, this
481
* ``maverick`` for the 2.2 series,
482
* ``lucid`` for the 2.1 series,
483
* ``karmic`` for the 2.0 series.
485
* Subscribe the ``~ubuntu-sru`` team to the bug.
487
* Add a comment targeted to ``~ubuntu-sru`` explaining the expectations
488
(we are targeting running the test suite during the build which, as of
489
September 2010, fails for known reasons that are currently addressed).
490
Search for bugs tagged with ``sru`` for examples and don't forget to tag
491
the bug you selected.
added
removed
doc/developers/releasing.txt
