4
This document describes the processes for making and announcing a Bazaar
4
This document describes the processes for making and announcing a Breezy
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
<https://www.breezy-vcs.org/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).
24
#. Download the pqm plugin and install it into your ``~/.bazaar/plugins``::
26
bzr branch lp:bzr-pqm ~/.bazaar/plugins/pqm
26
#. Be a member of https://launchpad.net/~brz (or you won't be able to land
32
In this document, we're talking about source releases only, packages and
33
installers are built from this but we won't talk about them here.
35
Every release is part of a series, ``brz-3.0.0`` is part of series ``3.0``.
37
We do two different kind of releases: the betas releases and the stable
38
releases for a given series.
40
For a given series, releases will be done to deliver new versions of brz to
41
different kinds of users:
43
#. beta releases: named ``x.ybn`` where ``x.y`` is the series and ``n``
44
starts at 1 and is incremented. These releases are targeted to beta
45
testers who don't want to run from source but are interested in features
48
#. stable releases: name ``x.y.z`` where ``x.y.`` is the series and ``z``
49
starts at 0 and is incremented. These releases are targeted at people
50
that want bugfixes only and no new features.
53
Differences in the release process between beta and stable release will be
54
mentioned when needed.
59
As of September 2018, we maintain a single series: 3.0.
61
#. as much as possible releases should not disturb development, and
62
ongoing development should not disturb releases,
64
#. the most recent development series should release once a month during
65
the beta period (see `Development cycles <cycle.html>`_ for more
68
#. the most recent stable series should release every other month (based
69
on the amount of bug fixes, this can be shorter or longer depending on
72
#. previous series should release on a regular basis without interfering
73
with the most recent series with a decreasing order of priority (again
74
this should be based on bugs importance and user feedback),
76
#. the death of a series should be planned ahead of time. 6 months should
77
give enough time to our users to migrate to a more recent series. This
78
doesn't mean we will make a release at the end of the series, just that
79
before the end date we *could* possibly put out another release if
80
there was a sufficiently important fix. Beyond that date, we won't
81
even land changes on that branch (unless something causes a miraculous
84
#. there should not be more than 2 releases in the same week (but the
85
Release Manager is free to ignore this (get in touch with packagers
88
At the start of a series cycle
89
==============================
91
To start a new series cycle:
93
#. Create a new series ``x.y`` at <https://launchpad.net/brz/+addseries>.
95
#. Add milestones at <https://launchpad.net/brz/x.y/+addmilestone> to that
96
series for the beta releases and the stable series mentioning their
97
expected dates. Only the milestone associated to the next release in
98
this series should be left active to avoid clutter when targeting bugs.
100
#. If you made a new series, you will need to create a new branch for this
101
release series. This branch will be used only from the first non-beta
102
release onwards. It needs to be created by a https://launchpad.net/~brz
103
member (ask the core devs for instructions or to do it for you).
105
#. Start a new release-notes file::
107
cd doc/en/release-notes
108
cp series-template.txt brz-x.y.txt # e.g. brz-3.1.txt
111
#. Start a new whats-new file::
114
cp template.txt brz-x.y.txt # e.g. brz-3.1.txt
117
#. Update ``doc/en/index.txt`` to point to the new whats-new file.
119
At the start of a release cycle
120
===============================
32
122
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
124
#. Send mail to the list with the key dates, who will be the release
63
125
manager, and the main themes or targeted bugs. Ask people to nominate
64
126
objectives, or point out any high-risk things that are best done early,
65
127
or that interact with other changes. This is called the metronome mail
66
128
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
73
#. Configure pqm-submit for this branch, with a section like this (where
74
x.y is the version to release).
75
``~/.bazaar/locations.conf``::
77
[/home/mbp/bzr/prepare-x.y]
78
pqm_email = Canonical PQM <pqm@bazaar-vcs.org>
79
submit_branch = http://bazaar.launchpad.net/~bzr-pqm/bzr/x.y
80
parent_branch = http://bazaar.launchpad.net/~bzr-pqm/bzr/x.y
81
public_branch = http://bazaar.example.com/prepare-x.y
82
submit_to = bazaar@lists.canonical.com
83
smtp_server = mail.example.com:25
85
Please see <http://doc.bazaar-vcs.org/developers/HACKING.html#an-overview-of-pqm>
86
for more details on PQM
88
#. In the release branch, update ``version_info`` in ``./bzrlib/__init__.py``.
130
#. Make a local branch to prepare the release::
132
brz branch lp:brz/x.y x.y-dev
134
If you're doing your first beta release, branch from trunk::
136
brz branch lp:brz x.y-dev
138
Note that you will generally reuse the same branch for all releases in a
141
#. Add a landing job for the release branch at https://ci.breezy-vcs.org/
143
#. Update the version number in the ``brz`` script, and the
144
``breezy/__init__.py`` file::
146
version_info = (x, y, z, 'dev', 0)
148
#. Add a new section at the top of the current release notes (in
149
``doc/en/release-notes``) about the new release, including its version
150
number and the headings from ``release-template.txt``.
152
#. Update the "What's New" documents in ``doc/en/whats-new``.
154
#. Make sure a milestone exists for your release and that it is active,
155
<https://launchpad.net/brz/x.y> lists the existing milestones,
156
<https://launchpad.net/brz/x.y/x.y.z/+edit> allows you to toggle the
159
#. Commit this and make a proposal against the release branch. Self approve
160
it (you're the release manager).
163
Doing a particular release
164
==========================
169
3.0.0 will start to be released as alpha as integrating plugins and porting
170
to python3 (while maintaining python2 compatiblity) desserve to be testing
171
in the wild by people understanding the risks.
173
That being said, the whole test suite has been preserved and enriched in the
176
Alpha releases will happen as source only (tarballs) and the process is
179
Note that the intent is to come back to beta releases as soon as possible so
180
the alpha releases won't happen again.
182
The process for releasing an alpha release is therefore:
183
- upload a tarball to launchpad,
184
- upload a tarball to pypi,
185
- mail bazaar@lists.canonical.com,
186
- post an announcement on the home page.
188
Uploading tarballs are described below, just use alpha versions (3, 0, 0,
189
'alpha', 1) in ``./breezy/__init__.py``
191
Update the source code
192
----------------------
194
#. Check that there is a milestone for the release you're doing. If there
195
is no milestone it indicates a process problem - make the milestone but
196
also mail the list to raise this issue in our process. Milestones are
197
found at <https://launchpad.net/brz/+milestone/x.y.z>.
199
#. Merge into your branch all previous stable series fixes that haven't been
200
merged yet. For example, if you're releasing 3.2.x, make sure the fixes
201
on 3.1, 3.0 have already been merged up::
205
and commit that merge in its own commit. This should happen only if the
206
devs landing changes in previous releases forgot to merge them up. Since
207
this can slow down the freeze, feel free to gently remind them about
208
their duties ;) If you feel unsafe resolving the conflicts or it's too
209
time consuming, contact the related devs and skip this merge.
211
Alternatively, think about automating these merges.
213
#. In the release branch, update ``version_info`` in ``./breezy/__init__.py``.
89
214
Make sure the corresponding milestone exists.
90
Double check that ./bzr ``_script_version`` matches ``version_info``. Check
91
the output of ``bzr --version``.
215
Double check that ./brz ``_script_version`` matches ``version_info``. Check
216
the output of ``./brz --version``.
93
218
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.
220
version_info = (3, 0, 0, 'beta', SERIAL)
224
version_info = (3, 0, 0, 'beta', 1)
226
For stable releases use::
228
version_info = (3, 0, 0, 'final', 0)
230
#. Update the ``./doc/en/release-notes/`` section for this release.
232
Check that all news entries related to this release have been added in
233
the right section. For example, if you're releasing 3.0b3, the following
234
command should display a a single chuk diff for the 3.0b3 release::
236
brz diff -rbrz-3.0b2.. doc/en/release-notes/brz-3.0.txt
238
Fill out the date and a description of the release under the existing
239
header (the diff above will help you summarizing). If there isn't one,
240
follow the instructions above for using the ``release-template.txt`` file
241
and remind people that they should document their changes there ;)
243
See *3.0b1* or similar for an example of what this looks like.
245
#. Add or check the summary of the release into the "What's New" document.
247
If this is the first release in a new series make sure to update the
248
introduction mentioning:
250
* the date of this first release,
251
* until when the series is expected to be supported.
253
Looking at ``brz annotate`` for previous series should give you the right
254
hints. The ``doc/en/_templates/index.html`` file should also be updated.
256
#. To check that all bugs mentioned in the release notes are actually
257
marked as closed in Launchpad, you can run
258
``tools/check-newsbugs.py``::
260
./tools/check-newsbugs.py doc/en/release-notes/brz-x.y.txt
262
As of 2011-07-18, all bugs mentioned in the output of the script requires
263
some sort of intervention (either changing the status if it's not 'Fix
264
Released' or setting a different milestone if the bug hasn't been
265
fixed). A few false positives may remain in the older series, don't let
266
this slow you down too much. This script accepts options you may find
267
useful, use ``./tools/check-newsbugs.py`` to display its usage (``-w``
268
will open each bug in your browser for example).
270
#. For beta releases update the translation template::
272
BRZ_PLUGIN_PATH=-site make po/brz.pot
274
This is especially important for the final beta release which is when
275
translations are frozen and translators are requested (see `The final
276
beta - branching and translations`_) to make the translations.
278
#. For stable releases update the translations::
280
brz merge lp:~brz-core/brz/brz-translations-export-x.y
129
282
#. Commit these changes to the release branch, using a command like::
131
bzr commit -m "Release 1.14."
284
brz commit -m "Release 3.0.0"
133
286
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.
288
=== modified file 'breezy/__init__.py'
289
--- breezy/__init__.py 2011-02-09 06:35:00 +0000
290
+++ breezy/__init__.py 2011-03-10 10:24:47 +0000
292
# Python version 2.0 is (2, 0, 0, 'final', 0)." Additionally we use a
293
# releaselevel of 'dev' for unreleased under-development code.
295
-version_info = (2, 3, 1, 'dev', 0)
296
+version_info = (2, 3, 1, 'final', 0)
298
# API compatibility version
299
api_minimum_version = (2, 3, 0)
301
=== modified file 'doc/en/release-notes/brz-2.3.txt'
302
--- doc/en/release-notes/brz-2.3.txt 2011-03-09 08:30:16 +0000
303
+++ doc/en/release-notes/brz-2.3.txt 2011-03-10 10:40:47 +0000
308
-:2.3.1: NOT RELEASED YET
310
-External Compatibility Breaks
311
-*****************************
313
-.. These may require users to change the way they use Breezy.
318
-.. New commands, options, etc that users may wish to try out.
323
-.. Improvements to existing commands, especially improved performance
324
- or memory usage, or better results.
327
+This is a bugfix release. Upgrading is recommended for all users of earlier
333
=== modified file 'doc/en/whats-new/whats-new-in-2.3.txt'
334
--- doc/en/whats-new/whats-new-in-2.3.txt 2011-02-03 16:29:18 +0000
335
+++ doc/en/whats-new/whats-new-in-2.3.txt 2011-03-10 11:10:36 +0000
337
improvements made to the core product, it highlights enhancements within the
338
broader Breezy world of potential interest to those upgrading.
340
-Breezy 2.3.0 is fully compatible both locally and on the network with 2.0 2.1,
341
-and 2.2, and can read and write repositories generated by all previous
342
+Breezy 2.3.1 includes all the fixes in the un-released 2.0.7, 2.1.4 and 2.2.5
343
+versions that weren't included in 2.3.0 and fixes some bugs on its own.
345
+See the :doc:`../release-notes/index` for details.
347
+Breezy 2.3 is fully compatible both locally and on the network with 2.0, 2.1,
348
+and 2.2. It can read and write repositories generated by all previous
169
354
#. 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::
179
bzr pqm-submit -m "(mbp) prepare 1.14"
181
#. When PQM succeeds, pull down the master release branch.
358
#. Push those changes to a brz branch and make a merge proposal::
362
Use a commit message formatted like::
366
Note that ``brz push`` should mention updating one tag (which you just
367
created). If it doesn't, double-check that you created (and pushed) this
370
#. Once the merge proposal has landed, pull down the master release branch.
184
373
Making the source tarball
191
380
#. Now we'll try expanding this tarball and running the test suite
192
381
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
383
make check-dist-tarball | subunit2pyunit
385
You may encounter failures while running the test suite caused by your
386
locally installed plugins. Use your own judgment to decide if you can
387
release with these failures. When in doubt, disable the faulty plugins
388
one by one until you get no more failures. Alternatively, you can use
389
``BRZ_DISABLE_PLUGINS`` or ``BRZ_PLUGIN_PATH=-site`` to disable one or
392
Remember that this branch has already been tested on
393
https://ci.breezy-vcs.org, this step is particularly testing that the
394
cython extensions, which are updated by your local cython version when
395
you run make dist, are in good shape.
203
398
Publishing the source tarball
204
399
-----------------------------
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.
401
#. Go to the relevant <https://launchpad.net/brz/x.y> series page in Launchpad.
403
#. Create a release of the milestone, and upload the source tarball and
404
the GPG signature. Or, if you prefer, use the
405
``tools/packaging/lp-upload-release`` script to do this. Note that
406
this changes what the download widget on the Launchpad brz home
407
page shows, so don't stop the release process yet, or platform binary
408
installers won't be made and the download list will stay very small!
409
<https://bugs.launchpad.net/launchpad/+bug/586445>
412
Kick off the next cycle
413
-----------------------
415
From that point, there is no possible return, the tarball has been uploaded
416
so you can relax a bit.
418
You're still holding a "social" lock on the launchpad branch though. Until
419
your start the next cycle, nobody should land anything on this branch. If
420
they do, they either targeted the wrong branch or didn't update the news
421
file correctly, so the sooner the branch is opened again, the better.
423
This matters more for ``lp:brz`` than for ``lp:brz/x.y``, ``lp:brz`` should
424
always be open for landing, so you should do `At the start of a release
425
cycle`_ as soon as possible (i.e. update the version number in ``brz`` and
426
``breezy/__init__``, create/update the news files and create/update the
427
milestone for the next relase).
429
You may also need to do `At the start of a series cycle`_ if you're starting
432
The final beta - branching and translations
433
-------------------------------------------
435
A word of caution: the instructions above works well for all releases but
436
there is one special case that requires a bit more care: when you release
437
the *last* beta for a given ``x.y`` series (from trunk aka lp:brz), you need
438
to setup *two* branches for the next cycle:
440
#. ``lp:brz`` needs to be opened for the next *series* ``x.(y+1)``.
442
#. ``lp:brz/x.y`` needs to be opened for the next *release* ``x.y.0`` in the
443
series. Since this is first real use of ``lp:brz/x.y``, this is also the
444
deadline for the https://ci.breezy-vcs.org/ landing job to be created.
446
Both are important as ``lp:brz`` should remain open so any change can be
447
landed, ``lp:brz/x.y`` on the other hand should be ready to receive bug
450
``lp:brz`` is generally more important as the bug fixes on ``lp:brz/x.y``
451
won't be released sooner than a month from now whereas people may already
452
been waiting to land on ``lp:brz``.
456
#. Open ``lp:brz`` for ``x.(y+1)``
458
#. Create https://ci.breezy-vcs.org/ landing job and/or update the
459
``lp:brz/x.y`` branch based on whatever revision you want to release.
461
#. Release ``x.y.0`` from ``lp:brz/x.y``
463
#. Open ``lp:brz/x.y`` for bug fixes
465
You also need to ensure Launchpad is set up to import/export translations
466
for the new branch and inform translators.
468
#. Push the last beta release to a new branch::
470
brz push lp:~brz-core/brz/brz-translations-export-x.y
472
#. On the translations series synchronization settings page
473
<https://translations.launchpad.net/brz/x.y/+translations-settings>
474
turn on ``Import template files`` then for exports click ``Choose a
475
target branch`` and point it at the branch you just pushed.
477
#. E-mail translators to announce that the forthcoming stable release of brz
478
is ready for translations. Send to
479
``launchpad-translators@lists.launchpad.net`` and
480
``ubuntu-translators@lists.ubuntu.com``.
482
#. The series is now frozen for strings and API, see below for adding
483
that to the announcement.
213
485
Announcing the source freeze
214
486
----------------------------
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
488
#. Post to the ``bazaar@lists.canonical.com`` list, saying that the source
489
has been frozen. Be extra clear that this is only a *source* release
490
targeted at packagers and installer builders (see
491
<https://bugs.launchpad.net/launchpad/+bug/645084>). This is the cue for
492
platform maintainers and plugin authors to update their code. This is
493
done before the general public announcement of the release.
495
The freeze announcement generally guess the date of the official public
496
announcement, for the most recent stable series (the one supported by the
497
installers and most of the distributions) it's generally a few days after
498
the freeze. For older series supported only via SRUs for Ubuntu, we don't
499
control the process as tightly so guessing the date is not appropriate.
501
For the final beta release include in your announcement a notice of
502
API and translation freezes noting that public methods should not
503
be removed or changed and strings should not be added or changed.
505
#. Pause for a few days.
222
508
Publishing the release
223
509
----------------------
225
511
There is normally a delay of a few days after the source freeze to allow
226
for binaries to be built on various platforms. Once they have been built,
512
for binaries to be built for various platforms. Once they have been built,
227
513
we have a releasable product. The next step is to make it generally
228
514
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/>`_.
240
This page is edited via the lp:bzr-website branch. (Changes
241
pushed to this branch are refreshed by a cron job on escudero.)
243
#. Announce on the `Bazaar wiki <http://bazaar-vcs.org/Welcome>`_.
516
#. Go to the release web page at <https://launchpad.net/brz/x.y/x.y.z>
518
#. Announce on the Breezy website.
245
520
#. Check that the documentation for this release is available in
246
<http://doc.bazaar-vcs.org>. It should be automatically build when the
247
branch is created, by a cron script ``update-bzr-docs`` on
248
``escudero``. As of today (2009-08-27) ``igc`` manually updates the
249
pretty version of it.
521
<https://www.breezy-vcs.org/doc/en/>. It should be automatically build when
522
the branch is created, by a cron script ``update-brz-docs`` on
523
``escudero``. When the first release is created in a new series, a branch
524
needs to be created on ``escudero``::
526
ssh escudero.canonical.com
528
cd /srv/doc.bazaar.canonical.com/
529
brz branch lp:brz/2.7 brz/brz.2.7
531
And the ``brz/bin/update-brz-docs`` script needs to refer to it.
533
The ``lp:brz-alldocs`` branch also needs to be updated when a new series
534
is introduced, see the ``README`` file there for more instructions
535
(looking at the branch history is also a good way to understand what
536
needs to be done and to document any policy changes).
252
538
Announcing the release
253
539
----------------------
271
555
The announce mail will look something like this::
273
Subject: bzr x.yy released!
557
Subject: brz x.y.z released!
559
The Breezy team is happy to announce availability of a new
560
release of the brz adaptive version control system.
562
Breezy is a fork of the Bazaar version control system.
275
564
<<Summary paragraph from news>>
277
The Bazaar team is happy to announce availability of a new
278
release of the bzr adaptive version control system.
279
Bazaar is part of the GNU system <http://gnu.org/>.
281
566
Thanks to everyone who contributed patches, suggestions, and
284
Bazaar is now available for download from
285
http://bazaar-vcs.org/Download as a source tarball; packages
569
Breezy is now available for download from
570
https://launchpad.net/brz/x.y/x.y.z/ as a source tarball; packages
286
571
for various systems will be available soon.
288
<<NEWS section from this release back to the last major release>>
573
<<release notes from this release back to the last major release>>
290
575
Feel free to tweak this to your taste.
292
#. Make an announcement through <https://launchpad.net/bzr/+announce>
294
#. Update the IRC channel topic. Use the ``/topic`` command to do this,
295
ensuring the new topic text keeps the project name, web site link, etc.
297
#. Announce on http://freshmeat.net/projects/bzr/
299
This should be done for beta releases, release candidates and final
300
releases. If you do not have a Freshmeat account yet, ask one of the
303
#. Update `<http://en.wikipedia.org/wiki/Bazaar_(software)>`_ -- this should
304
be done for final releases but not for beta releases or Release Candidates.
306
#. Update the python package index: <http://pypi.python.org/pypi/bzr> - best
309
python setup.py register
311
Remember to check the results afterwards.
313
To be able to register the release you must create an account on
314
<http://pypi.python.org/pypi> and have one of the existing owners of
315
the project add you to the group.
577
#. Make an announcement through <https://launchpad.net/brz/+announce>
578
mentioning the milestone URL <https://launchpad.net/brz/+milestone/x.y.z>
579
so people get an easy access to details.
581
#. Update `<http://en.wikipedia.org/wiki/Breezy_(software)>`_ -- this should
582
be done for the stable and beta releases.
584
#. Update the python package index: <http://pypi.python.org/pypi/breezy>
586
From the tarball created and tested earlier ::
588
twine upload ../breezy-3.0.0.tar.gz ../breezy-3.0.0.tar.gz.asc
590
Remember to check the results afterward -- this should be done for
591
stable releases but not for beta releases nor SRUs.
593
The ``twine`` command is provided by the ``twine`` package on Debian and
594
Ubuntu. Beware that you need at least ``twine-1.10``.
596
If in doubt, you can test with <https://testpypi.python.org/pypi> where
597
you can register yourself, register the brz project and upload (and then
598
remove the upload and delete the project so a new release manager can
599
enjoy the same facilities). If the project already exists, have one of
600
the existing owners of the project add you to the group.
602
To use the pypi test site, you need to record your credentials for an
603
existing user (the registration process is manual and starts at
604
<https://testpypi.python.org/pypi?%3Aaction=register_form>.
606
Once registered, you can record your crdentials in your ``~/pypirc`` file
610
username:<login on testpypi>
611
password:<password on testpypi>
612
repository = https://testpypi.python.org/pypi
614
Registering the breezy project if doesn't exist is achieved with::
616
python setup.py -r https://testpypi.python.org/pypi register
618
Uploading is done with::
620
twine upload -r testpypi ../breezy-3.0.0.tar.gz ../breezy-3.0.0.tar.gz.asc
622
To be able to upload the release you must create an account on
623
<http://pypi.python.org/pypi> and have one of the existing owners of the
624
project add you to the group and update your ``[pypi]`` section in your
318
628
Merging the released code back to trunk
319
629
---------------------------------------
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.
631
Merge the release branch back into the trunk. The ``doc/en/release-notes``
632
changes should be merged into the right place because each release series
633
has its own release-notes file, but double-check.
635
If it's not already done, advance the version number in ``brz`` and
636
``breezy/__init__.py``. File a merge proposal against ``lp:brz``.
326
638
As soon as you change the version number in trunk, make sure you have
327
639
created the corresponding milestone to ensure the continuity in bug
328
640
targeting or nominating. Depending on the change, you may even have to
329
641
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.
642
that case go to `At the start of a series cycle`_ and follow the
643
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
646
Releases until the final one
337
647
----------------------------
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.
649
Congratulations - you have made your first release. Have a beer or fruit
650
juice - it's on the house! If it was a beta, you're not finished
651
yet. Another beta or hopefully a stable release is still to come.
653
The process is the same as for the first release. Goto `Doing a particular
654
release`_ and follow the instructions again. Some details change between
655
beta and stable releases, but they should be documented. If the instructions
656
aren't clear enough, please fix them.
659
Getting the release into Ubuntu
660
-------------------------------
662
/!\ Nothing in this section has been validated for breezy yet.
664
(Feel free to propose or add new sections here about what we should do to
665
get brz into other places.)
667
For the currently-under-development release of Ubuntu, no special action
668
is needed: the release should be picked by Debian and synced from there into
671
Releases off stable brz branches should go in to the ``-updates`` of the
672
Ubuntu release that originally contained that branch. (Ubuntu Lucid had
673
brz 2.2.0, so should get every 2.2.x update.) This means going through
674
the `SRU (Stable Release Updates)
675
<https://wiki.ubuntu.com/StableReleaseUpdates>`__ process.
677
Since September 2010, brz has received approval by the technical
678
board for the `MicroReleaseExceptions
679
<https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions>`__
680
category so that whole bugfix releases can more easily be
683
Progress on these realeases is tracked on the `SRU wiki
684
<http://wiki.bazaar.canonical.com/UbuntuStableReleaseUpdates>`_
687
**After making a brz stable-release release, nominate the most serious bug
688
for the appropriate Ubuntu release and subscribe the `ubuntu-sru` team.**
690
This requires a couple of tricks (please reconsider and tweak as things
691
evolves from one release to the other):
693
* create a distro task with the ``Also affects distribution`` button and
694
select ``brz (Ubuntu)``.
696
* change the *URL* to point to ``ubuntu/+source/brz`` instead of ``brz``
697
(this is needed if you create the distro task but not if it exists
698
already). You should now be able to click the ``Nominate for release``
699
button and select the right Ubuntu release. As of September 2010, this
702
* ``quantal`` for the 2.6 series,
703
* ``precise`` for the 2.5 series,
704
* ``oneiric`` for the 2.4 series,
705
* ``natty`` for the 2.3 series,
706
* ``maverick`` for the 2.2 series,
707
* ``lucid`` for the 2.1 series,
709
* Subscribe the ``~ubuntu-sru`` team to the bug.
711
* Add a comment targeted to ``~ubuntu-sru`` explaining the expectations
712
(we are targeting running the test suite during the build which, as of
713
September 2010, fails for known reasons that are currently addressed).
714
Search for bugs tagged with ``sru`` for examples and don't forget to tag
715
the bug you selected.
353
* `Packaging into the bzr PPA <ppa.html>`_ to make and publish Ubuntu
721
* `Packaging into the brz PPA <ppa.html>`_ to make and publish Ubuntu
355
* `Bazaar Developer Document Catalog <index.html>`_
723
* `Breezy Developer Document Catalog <index.html>`_
356
724
* `Development cycles <cycle.html>`_: things that happen during the cycle
357
725
before the actual release.
added
removed
doc/developers/releasing.txt
