26
18
bzr branch lp:bzr-pqm ~/.bazaar/plugins/pqm
32
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.
20
Starting the release phase
21
--------------------------
23
When it's time to make the release candidate:
44
25
#. 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,
26
asking a Canonical sysadmin.
27
This branch means that from the first release candidate onwards,
47
28
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
#. Send mail to the list with the key dates, who will be the release
63
manager, and the main themes or targeted bugs. Ask people to nominate
64
objectives, or point out any high-risk things that are best done early,
65
or that interact with other changes. This is called the metronome mail
66
and is described in `Development cycles <cycle.html>`_.
68
#. Make a local branch for preparing this release. (Only for the first
29
specifically-targetted fixes go into the release.
31
#. Register the branch at <https://launchpad.net/products/bzr/+addbranch>
33
#. Make a release candidate.
36
Preparing the tree for release
37
------------------------------
39
#. Make a local branch for preparing this release. (Only for the first
69
40
release in a series, otherwise you should already have a branch.) ::
71
42
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).
44
#. Configure pqm-submit for this branch, with a section like this in
75
45
``~/.bazaar/locations.conf``::
77
[/home/mbp/bzr/prepare-x.y]
47
[/home/mbp/bzr/prepare-1.14]
78
48
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
49
submit_branch = http://bazaar-vcs.org/bzr/bzr.1.14
50
public_branch = http://bazaar.your-domain.com/bzr
82
51
submit_to = bazaar@lists.canonical.com
83
smtp_server = mail.example.com:25
52
smtp_server = mail.your-domain.com:25
85
Please see <http://doc.bazaar-vcs.org/developers/HACKING.html#an-overview-of-pqm>
54
Please see <http://doc.bazaar-vcs.org/latest/developers/HACKING.html#an-overview-of-pqm>
86
55
for more details on PQM
88
57
#. In the release branch, update ``version_info`` in ``./bzrlib/__init__.py``.
89
Make sure the corresponding milestone exists.
90
58
Double check that ./bzr ``_script_version`` matches ``version_info``. Check
91
the output of ``bzr --version``.
93
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.
59
the output of ``bzr --version``.
109
61
#. 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
63
#. To check that all bugs mentioned in ``./NEWS`` are actually marked as
119
64
closed in Launchpad, you can run ``tools/check-newsbugs.py``::
185
130
-------------------------
187
132
#. Change into the source directory and run ::
136
This also makes a zip file, which is easier to access on Microsoft
191
139
#. Now we'll try expanding this tarball and running the test suite
192
140
to check for packaging problems::
194
142
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
203
Publishing the source tarball
204
-----------------------------
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.
213
Announcing the source freeze
214
----------------------------
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
222
145
Publishing the release
223
146
----------------------
225
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,
227
we have a releasable product. The next step is to make it generally
148
Now you have the releasable product. The next step is making it
228
149
available to the world.
151
#. In <https://launchpad.net/bzr/> click the "Release series" for this
152
series, to take you to e.g. <https://launchpad.net/bzr/1.14>. Then
153
click "Register a release", and add information about this release.
232
155
#. Within that release, upload the source tarball and zipfile and the GPG
233
156
signature. Or, if you prefer, use the
234
157
``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>`_.
245
#. Check that the documentation for this release is available in
246
<http://doc.bazaar-vcs.org>. It should be automatically build when the
159
#. Link from http://bazaar-vcs.org/Download to the tarball and signature.
161
#. Announce on the `Bazaar home page <http://bazaar-vcs.org/>`_.
163
#. Check that the documentation for this release is available in
164
<http://doc.bazaar-vcs.org>. It should be automatically build when the
247
165
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.
252
169
Announcing the release
257
174
#. Make an announcement mail.
259
For release candidates or beta releases, this is sent to the ``bazaar``
260
list only to inform plugin authors and package or installer managers.
262
Once the installers are available, the mail can be sent to the
263
``bazaar-announce`` list too.
265
For final releases, it should also be cc'd to ``info-gnu@gnu.org``,
266
``python-announce-list@python.org``, ``bug-directory@gnu.org``.
268
In all cases, it is good to set ``Reply-To: bazaar@lists.canonical.com``,
269
so that people who reply to the announcement don't spam other lists.
176
For release candidates, this is sent to the ``bazaar-announce`` and
177
``bazaar`` lists. For final releases, it should also be cc'd to
178
``info-gnu@gnu.org``, ``python-announce-list@python.org``,
179
``bug-directory@gnu.org``. In both cases, it is good to set
180
``Reply-To: bazaar@lists.canonical.com``, so that people who reply to
181
the announcement don't spam other lists.
271
183
The announce mail will look something like this::
273
185
Subject: bzr x.yy released!
275
187
<<Summary paragraph from news>>
277
The Bazaar team is happy to announce availability of a new
189
The Bazaar team is happy to announce availability of a new
278
190
release of the bzr adaptive version control system.
279
191
Bazaar is part of the GNU system <http://gnu.org/>.
281
193
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
196
Bazaar is now available for download from
197
http://bazaar-vcs.org/Download as a source tarball; packages
286
198
for various systems will be available soon.
288
200
<<NEWS section from this release back to the last major release>>
290
202
Feel free to tweak this to your taste.
323
235
the version number in ``bzr`` and ``bzrlib/__init__.py``. Submit this
324
236
back into pqm for bzr.dev.
326
As soon as you change the version number in trunk, make sure you have
327
created the corresponding milestone to ensure the continuity in bug
328
targeting or nominating. Depending on the change, you may even have to
329
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.
332
238
You should also merge (not pull) the release branch into
333
239
``lp:~bzr/bzr/current``, so that branch contains the current released code
336
Releases until the final one
337
----------------------------
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.
246
To start a new release cycle:
248
#. Send mail to the list with the key dates, who will be the release
249
manager, and the main themes or targeted bugs. Ask people to nominate
250
objectives, or point out any high-risk things that are best done early,
251
or that interact with other changes.
253
#. Add a new "series" in Launchpad at <https://launchpad.net/bzr/+addseries>.
254
There is one series for every *x.y* release.
256
#. Add milestones to that series for the release candidate and the final
257
release, and their expected dates.
259
#. Deactivate old releases and their milestones.
261
#. Update the version number in the ``bzr`` script, and the
262
``bzrlib/__init__.py`` file.
added
removed
doc/developers/releasing.txt
