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.canonical.com/developers/cycle.html>`_,
7
but it's the most complex part. This document gives a checklist you can
8
follow from start to end in one go.
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
10
12
If you're helping the Release Manager (RM) for one reason or another, you
11
13
may notice that he didn't follow that document scrupulously. He may have
25
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.
28
80
At the start of a release cycle
29
81
===============================
41
93
the release branch.
43
95
#. If you made a new series, add milestones at
44
<https://edge.launchpad.net/bzr/x.y/+addmilestone> to that series for
96
<https://launchpad.net/bzr/x.y/+addmilestone> to that series for
45
97
the beta release, release candidate and the final release, and their
48
#. Create a new milestone <https://edge.launchpad.net/bzr/x.y/+addmilestone>
100
#. Create a new milestone <https://launchpad.net/bzr/x.y/+addmilestone>
49
101
and add information about this release. We will not use it yet, but it
50
102
will be available for targeting or nominating bugs.
81
133
version_info = (x, y, z, 'dev', 0)
83
#. Add a new section at the top of ``NEWS`` about the new release,
84
including its version number and the headings from
85
``NEWS-template.txt``.
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``.
87
145
#. Update the "What's New" documents in ``doc/en/whats-new``.
105
163
Double check that ./bzr ``_script_version`` matches ``version_info``. Check
106
164
the output of ``bzr --version``.
108
For beta releases use::
166
For betahttps://code.edge.launchpad.net/~knittl/bzr/fix-inventory-r0/+merge/354985 releases use::
110
168
version_info = (2, 1, 0, 'beta', SERIAL)
122
180
version_info = (2, 1, 2, 'final', 0)
124
#. Update the ``./NEWS`` section for this release.
182
#. Update the ``./doc/en/release-notes/`` section for this release.
126
184
Fill out the date and a description of the release under the existing
127
header. If there isn't one, follow the above for using the NEWS
185
header. If there isn't one, follow the instructions above for using the
186
``release-template.txt`` file.
130
188
See *2.1.1* or similar for an example of what this looks like.
132
190
#. Add a summary of the release into the "What's New" document.
134
#. To check that all bugs mentioned in ``./NEWS`` are actually marked as
135
closed in Launchpad, you can run ``tools/check-newsbugs.py``::
137
./tools/check-newsbugs.py NEWS
139
(But note there will be many false positives, and this script may be
140
flaky <https://bugs.edge.launchpad.net/bzr/+bug/354985>. Don't let
141
this slow you down too much.)
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
143
201
#. Commit these changes to the release branch, using a command like::
210
271
#. Now we'll try expanding this tarball and running the test suite
211
272
to check for packaging problems::
213
make check-dist-tarball
274
make check-dist-tarball | subunit2pyunit
215
You may encounter failures while running the test suite caused
216
by your locally installed plugins. Use your own judgment to
217
decide if you can release with these failures. When in doubt,
218
disable the faulty plugins one by one until you get no more
276
You may encounter failures while running the test suite caused by your
277
locally installed plugins. Use your own judgment to decide if you can
278
release with these failures. When in doubt, disable the faulty plugins
279
one by one until you get no more failures. Alternatively, you can use
280
``BZR_DISABLE_PLUGINS`` or ``BZR_PLUGIN_PATH=-site`` to disable one or
221
283
Remember that PQM has just tested everything too, this step is
222
284
particularly testing that the pyrex extensions, which are updated
235
297
this changes what the download widget on the Launchpad bzr home
236
298
page shows, so don't stop the release process yet, or platform binary
237
299
installers won't be made and the download list will stay very small!
238
<https://bugs.edge.launchpad.net/launchpad/+bug/586445>
300
<https://bugs.launchpad.net/launchpad/+bug/586445>
241
303
Announcing the source freeze
242
304
----------------------------
244
#. Post to the ``bazaar`` list, saying that the source has been frozen.
245
This is the cue for platform maintainers and plugin authors to update
246
their code. This is done before the general public announcement of the
306
#. Post to the ``bazaar`` list, saying that the source has been frozen
307
(gone gold). Be extra clear that this is only a *source* release
308
targeted at packagers and installer builders (see
309
<https://bugs.launchpad.net/launchpad/+bug/645084>). This is the cue
310
for platform maintainers and plugin authors to update their code. This
311
is done before the general public announcement of the release.
250
314
Kick off the next cycle
301
365
Subject: bzr x.y.z released!
303
<<Summary paragraph from news>>
305
367
The Bazaar team is happy to announce availability of a new
306
368
release of the bzr adaptive version control system.
307
369
Bazaar is part of the GNU system <http://gnu.org/>.
371
<<Summary paragraph from news>>
309
373
Thanks to everyone who contributed patches, suggestions, and
313
377
https://launchpad.net/bzr/2.x/2.x/ as a source tarball; packages
314
378
for various systems will be available soon.
316
<<NEWS section from this release back to the last major release>>
380
<<release notes from this release back to the last major release>>
318
382
Feel free to tweak this to your taste.
337
401
python setup.py register
339
Remember to check the results afterwards.
403
Remember to check the results afterwards -- this should be done for
404
final releases but not for beta releases or Release Candidates.
341
406
To be able to register the release you must create an account on
342
407
<http://pypi.python.org/pypi> and have one of the existing owners of
346
411
Merging the released code back to trunk
347
412
---------------------------------------
349
The rule is to keep ``NEWS`` sections sorted by date. You'll need to
350
review the merge and make sure that that is respected.
414
Merge the release branch back into the trunk. The
415
``doc/en/release-notes`` changes should be merged into the right place
416
because each release series has its own release-notes file, but
352
Merge the release branch back into the trunk. Check that changes in NEWS
353
were merged into the right sections. If it's not already done, advance
354
the version number in ``bzr`` and ``bzrlib/__init__.py``. Submit this
355
back into pqm for bzr.dev.
419
If it's not already done, advance the version number in ``bzr`` and
420
``bzrlib/__init__.py``. Submit this back into pqm for bzr.dev.
357
422
As soon as you change the version number in trunk, make sure you have
358
423
created the corresponding milestone to ensure the continuity in bug
added
removed
doc/developers/releasing.txt
