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 <cycle.html>`_, but it's the most complex part.
7
This document gives a checklist you can follow from start to end in one
16
#. Download the pqm plugin and install it into your ``~/.bazaar/plugins``::
18
bzr branch lp:bzr-pqm ~/.bazaar/plugins/pqm
24
To start a new release cycle:
26
#. Create a new series at <https://launchpad.net/bzr/+addseries>. There is one
27
series for every *x.y* release.
29
#. Go to the series web page at <https://launchpad.net/bzr/2.0>
31
#. Create a new release at
32
<https://launchpad.net/bzr/2.0/+addrelease> and add
33
information about this release. We will not use it yet, but it
34
will be available for targeting or nominating bugs.
36
#. We create a new pqm-controlled branch for this release series, by
37
asking a Canonical sysadmin.
38
This branch means that from the first release beta or candidate onwards,
39
general development continues on the trunk, and only
40
specifically-targeted fixes go into the release branch.
42
#. Add milestones at <https://edge.launchpad.net/bzr/2.0/+addmilestone> to
43
that series for the beta release, release candidate and the final release,
44
and their expected dates.
46
#. Update the version number in the ``bzr`` script, and the
47
``bzrlib/__init__.py`` file.
49
#. Send mail to the list with the key dates, who will be the release
50
manager, and the main themes or targeted bugs. Ask people to nominate
51
objectives, or point out any high-risk things that are best done early,
52
or that interact with other changes. This is called the metronome mail
53
and as RM you're supposed to send other metronome mails at your rythm.
56
Starting the release phase
57
--------------------------
59
When it's time to make the first beta release or release candidate:
61
#. Create a new milestone at <https://launchpad.net/bzr/2.0/+addmilestone>
62
for the beta release or release candidate.
64
#. Make a beta release or release candidate.
66
Preparing the tree for release
67
------------------------------
69
#. Make a local branch for preparing this release. (Only for the first
70
release in a series, otherwise you should already have a branch.) ::
72
bzr branch trunk prepare-1.14
74
#. Configure pqm-submit for this branch, with a section like this in
75
``~/.bazaar/locations.conf``::
77
[/home/mbp/bzr/prepare-1.14]
78
pqm_email = Canonical PQM <pqm@bazaar-vcs.org>
79
submit_branch = lp:bzr/2.0
80
public_branch = http://bazaar.example.com/prepare-2.0
81
submit_to = bazaar@lists.canonical.com
82
smtp_server = mail.example.com:25
84
Please see <http://doc.bazaar-vcs.org/latest/developers/HACKING.html#an-overview-of-pqm>
85
for more details on PQM
87
#. In the release branch, update ``version_info`` in ``./bzrlib/__init__.py``.
88
Double check that ./bzr ``_script_version`` matches ``version_info``. Check
89
the output of ``bzr --version``.
91
For beta releases use::
93
version_info = (2, 1, 0, 'beta', 1)
96
For release candidates use::
98
version_info = (2, 0, 1, 'candidate', 1)
101
#. Add the date and release number to ``./NEWS``
103
#. To check that all bugs mentioned in ``./NEWS`` are actually marked as
104
closed in Launchpad, you can run ``tools/check-newsbugs.py``::
106
./tools/check-newsbugs.py NEWS
108
(But note there can be some false positives, and this script may be
109
flaky <https://bugs.edge.launchpad.net/bzr/+bug/354985>. Don't let
110
this slow you down too much.)
112
#. Summarize into one or two paragraphs what's new in this release.
114
#. Commit these changes to the release branch, using a command like::
116
bzr commit -m "Release 1.14."
118
The diff before you commit will be something like::
120
=== modified file 'NEWS'
121
--- NEWS 2008-09-17 23:09:18 +0000
122
+++ NEWS 2008-09-23 16:14:54 +0000
130
+This release includes many bug fixes and a few performance and feature
131
+improvements. ``bzr rm`` will now scan for missing files and remove them,
132
+like how ``bzr add`` scans for unknown files and adds them. A bit more
133
+polish has been applied to the stacking code. The b-tree indexing code has
134
+been brought in, with an eye on using it in a future repository format.
135
+There are only minor installer changes since bzr-1.7rc2.
137
bzr 1.7rc2 2008-09-17
138
---------------------
141
=== modified file 'bzrlib/__init__.py'
142
--- bzrlib/__init__.py 2008-09-16 21:39:28 +0000
143
+++ bzrlib/__init__.py 2008-09-23 16:14:54 +0000
145
# Python version 2.0 is (2, 0, 0, 'final', 0)." Additionally we use a
146
# releaselevel of 'dev' for unreleased under-development code.
148
-version_info = (1, 7, 0, 'candidate', 2)
149
+version_info = (1, 7, 0, 'final', 0)
152
# API compatibility version: bzrlib is currently API compatible with 1.7.
154
#. Tag the new release::
158
#. Push those changes to a bzr reposistory that is public and accessible on
159
the Internet. PQM will pull from this repository when it attempts to merge
160
your changes. Then submit those changes to PQM for merge into the
161
appropriate release branch::
164
bzr pqm-submit -m "(mbp) prepare 1.14"
166
#. When PQM succeeds, pull down the master release branch.
169
Making the source tarball
170
-------------------------
172
#. Change into the source directory and run ::
176
This also makes a zip file, which is easier to access on Microsoft
179
#. Now we'll try expanding this tarball and running the test suite
180
to check for packaging problems::
182
make check-dist-tarball
184
You may encounter failures while running the test suite caused
185
by your locally installed plugins. Use your own judgment to
186
decide if you can release with these failures. When in doubt,
187
disable the faulty plugins one by one until you get no more
191
Publishing the release
192
----------------------
194
Now you have the beta or releasable product. The next step is making it
195
available to the world.
199
#. Within that release, upload the source tarball and zipfile and the GPG
200
signature. Or, if you prefer, use the
201
``tools/packaging/lp-upload-release`` script to do this.
203
#. Link from http://bazaar-vcs.org/Download to the tarball and signature.
205
#. Announce on the `Bazaar home page <http://bazaar-vcs.org/>`_.
207
#. Check that the documentation for this release is available in
208
<http://doc.bazaar-vcs.org>. It should be automatically build when the
209
branch is created, by a cron script ``update-bzr-docs`` on
210
``escudero``. As of today (2009-08-27) ``igc`` manually updates the
211
pretty version of it.
214
Announcing the release
215
----------------------
217
Now that the release is publicly available, tell people about it.
219
#. Make an announcement mail.
221
For release candidates or beta releases, this is sent to the ``bazaar``
222
list only to inform plugin authors and package or installer managers.
224
Once the installers are available, the mail can be sent to the
225
``bazaar-announce`` list too.
227
For final releases, it should also be cc'd to ``info-gnu@gnu.org``,
228
``python-announce-list@python.org``, ``bug-directory@gnu.org``.
230
In all cases, it is good to set ``Reply-To: bazaar@lists.canonical.com``,
231
so that people who reply to the announcement don't spam other lists.
233
The announce mail will look something like this::
235
Subject: bzr x.yy released!
237
<<Summary paragraph from news>>
239
The Bazaar team is happy to announce availability of a new
240
release of the bzr adaptive version control system.
241
Bazaar is part of the GNU system <http://gnu.org/>.
243
Thanks to everyone who contributed patches, suggestions, and
246
Bazaar is now available for download from
247
http://bazaar-vcs.org/Download as a source tarball; packages
248
for various systems will be available soon.
250
<<NEWS section from this release back to the last major release>>
252
Feel free to tweak this to your taste.
254
#. Make an announcement through <https://launchpad.net/bzr/+announce>
256
#. Update the IRC channel topic. Use the ``/topic`` command to do this,
257
ensuring the new topic text keeps the project name, web site link, etc.
259
#. Announce on http://freshmeat.net/projects/bzr/
261
This should be done for beta releases, release candidates and final
262
releases. If you do not have a Freshmeat account yet, ask one of the
265
#. Update `<http://en.wikipedia.org/wiki/Bazaar_(software)>`_ -- this should
266
be done for final releases but not for beta releases or Release Candidates.
268
#. Update the python package index: <http://pypi.python.org/pypi/bzr> - best
271
python setup.py register
273
Remember to check the results afterwards.
275
To be able to register the release you must create an account on
276
<http://pypi.python.org/pypi> and have one of the existing owners of
277
the project add you to the group.
280
Merging the released code back to trunk
281
---------------------------------------
283
Merge the release branch back into the trunk. Check that changes in NEWS
284
were merged into the right sections. If it's not already done, advance
285
the version number in ``bzr`` and ``bzrlib/__init__.py``. Submit this
286
back into pqm for bzr.dev.
288
You should also merge (not pull) the release branch into
289
``lp:~bzr/bzr/current``, so that branch contains the current released code
296
* `Packaging into the bzr PPA <ppa.html>`_ to make and publish Ubuntu
298
* `Bazaar Developer Document Catalog <index.html>`_
299
* `Development cycles <cycle.html>`_: things that happen during the cycle
300
before the actual release.
303
vim: filetype=rst textwidth=74 ai shiftwidth=4
added
removed
doc/developers/releasing.txt
