17
17
#. Make a local branch for preparing this release. (Only for the first
18
18
release in a series, otherwise you should already have a branch.) ::
20
bzr branch trunk prepare-1.14
22
#. Download the pqm plugin and install it into your ``~/.bazaar/plugins``::
24
bzr branch lp:bzr-pqm ~/.bazaar/plugins/pqm
20
bzr branch trunk prepare-1.6
26
22
#. Configure pqm-submit for this branch, with a section like this in
27
23
``~/.bazaar/locations.conf``::
29
[/home/mbp/bzr/prepare-1.14]
25
[/home/mbp/bzr/prepare-1.4]
30
26
pqm_email = Canonical PQM <pqm@bazaar-vcs.org>
31
submit_branch = http://bazaar-vcs.org/bzr/bzr.1.14
32
public_branch = http://bazaar.your-domain.com/bzr
27
submit_branch = http://bazaar-vcs.org/bzr/bzr.1.4
33
28
submit_to = bazaar@lists.canonical.com
34
smtp_server = mail.your-domain.com:25
36
Please see <http://doc.bazaar-vcs.org/latest/developers/HACKING.html#an-overview-of-pqm>
37
for more details on PQM
39
#. In the release branch, update ``version_info`` in ``./bzrlib/__init__.py``.
40
Double check that ./bzr ``_script_version`` matches ``version_info``. Check
41
the output of ``bzr --version``.
30
#. In the release branch, update ``version_info`` in
31
``./bzrlib/__init__.py``. Check the output of ``bzr --version``.
43
33
#. Add the date and release number to ``./NEWS``
45
#. To check that all bugs mentioned in ``./NEWS`` are actually marked as
46
closed in Launchpad, you can run ``tools/check-newsbugs.py``::
48
./tools/check-newsbugs.py NEWS
50
35
#. Summarize into one or two paragraphs what's new in this release.
52
37
#. Commit these changes to the release branch, using a command like::
54
bzr commit -m "Release 1.14."
39
bzr commit -m "Release 0.12rc1."
56
41
The diff before you commit will be something like::
92
77
#. Tag the new release::
96
#. Push those changes to a bzr reposistory that is public and accessible on
97
the Internet. PQM will pull from this repository when it attempts to merge
98
your changes. Then submit those changes to PQM for merge into the
99
appropriate release branch::
81
#. Submit those changes to PQM for merge into the appropriate release
102
bzr pqm-submit -m "(mbp) prepare 1.14"
85
bzr pqm-submit -m "(mbp) prepare 1.6"
104
87
#. When PQM succeeds, pull down the master release branch.
127
110
available to the world.
129
112
#. In <https://launchpad.net/bzr/> click the "Release series" for this
130
series, to take you to e.g. <https://launchpad.net/bzr/1.14>. Then
113
series, to take you to e.g. <https://launchpad.net/bzr/1.1>. Then
131
114
click "Register a release", and add information about this release.
133
116
#. Within that release, upload the source tarball and zipfile and the GPG
187
170
you do not have a Freshmeat account yet, ask one of the existing
190
#. Update `<http://en.wikipedia.org/wiki/Bazaar_(software)>`_ -- this should be done
191
for final releases but not for Release Candidates.
173
#. Update http://en.wikipedia.org/wiki/Bzr -- this should be done for
174
final releases but not for Release Candidates.
193
176
#. Update the python package index: <http://pypi.python.org/pypi/bzr> - best
194
177
done by running ::
210
193
the version number in ``bzr`` and ``bzrlib/__init__.py``. Submit this
211
194
back into pqm for bzr.dev.
213
You should also merge (not pull) the release branch into
214
``lp:~bzr/bzr/current``, so that branch contains the current released code
221
* `Packaging into the bzr PPA <ppa.html>`_ to make and publish Ubuntu
223
* `Bazaar Developer Document Catalog <index.html>`_
224
* `Development cycles <cycle.html>`_: things that happen during the cycle
225
before the actual release.
200
* `Packaging into the bzr PPA <ppa.html>`_ to make and publish Ubuntu
202
* `Bazaar Developer Document Catalog <index.html>`_
203
* `Development cycles <cycle.html>`_: things that happen during the cycle
204
before the actual release.
228
208
vim: filetype=rst textwidth=74 ai shiftwidth=4
added
removed
doc/developers/releasing.txt
