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
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
5
release, and managing the release process. This is just one phase of the
6
`overall development cycle
7
<http://doc.bazaar.canonical.com/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
12
16
If you're helping the Release Manager (RM) for one reason or another, you
13
17
may notice that he didn't follow that document scrupulously. He may have
14
18
good reasons to do that but he may also have missed some parts.
16
Follow the document yourself and don't hesitate to create the missing
17
milestones for example (we tend to forget these ones a lot).
26
#. PQM access rights (or you won't be able to land any change)
25
28
#. Download the pqm plugin and install it into your ``~/.bazaar/plugins``::
27
30
bzr branch lp:bzr-pqm ~/.bazaar/plugins/pqm
32
#. Alternatively, you can download and install ``lp:hydrazine`` (the main
33
difference is that hydrazine requires the branch to land to be hosted on
39
In this document, we're talking about source releases only, packages and
40
installers are built from this but we won't talk about them here.
42
Every release is part of a series, ``bzr-2.4.1`` is part of series ``2.4``.
44
We do two different kind of releases: the betas releases and the stable
45
releases for a given series.
47
For a given series, releases will be done to deliver new versions of bzr to
48
different kinds of users:
50
#. beta releases: named ``x.ybn`` where ``x.y`` is the series and ``n``
51
starts at 1 and is incremented. These releases are targeted to beta
52
testers who don't want to run from source but are interested in features
55
#. stable releases: name ``x.y.z`` where ``x.y.`` is the series and ``z``
56
starts at 0 and is incremented. These releases are targeted at people
57
that want bugfixes only and no new features.
60
Differences in the release process between beta and stable release will be
61
mentioned when needed.
30
63
When do we relase ?
31
64
===================
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
66
As of July 2011, we maintain four series (and one that is about to be EOLed).
67
Concurrently releasing them all at the same time makes it harder to shorten
68
the delay between the source availability and the package building longer
69
than necessary (we delay the official announcement until most of our users
70
can install the new release).
39
72
In order to continue to do time-based releases, we need to plan the
40
73
releases by series to minimize the collisions. In the end, it's the Release
41
74
Manager call to decide whether he prefers to do all releases at once
42
75
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.
77
We want to respect the following rules:
79
#. as much as possible releases should not disturb development, and
80
ongoing development should not disturb releases,
82
#. the most recent development series should release once a month during
83
the beta period (see `Development cycles <cycle.html>`_ for more
86
#. the most recent stable series should release every other month (based
87
on the amount of bug fixes, this can be shorter or longer depending on
90
#. previous series should release on a regular basis without interfering
91
with the most recent series with a decreasing order of priority (again
92
this should be based on bugs importance and user feedback),
94
#. the death of a series should be planned ahead of time. 6 months should
95
give enough time to our users to migrate to a more recent series. This
96
doesn't mean we will make a release at the end of the series, just that
97
before the end date we *could* possibly put out another release if
98
there was a sufficiently important fix. Beyond that date, we won't
99
even land changes on that branch (unless something causes a miraculous
102
#. there should not be more than 2 releases in the same week (but the
103
Release Manager is free to ignore this (get in touch with packagers
106
#. the series are aligned with Ubuntu releases for convenience since we
107
create a new series every 6 months. This means that we support the
108
stable series for 18 months. Note that we also propose the most recent
109
stable series via the stable PPA but that the SRU processs allow us to
110
reach a wider audience.
112
At the start of a series cycle
113
==============================
115
To start a new series cycle:
117
#. Create a new series ``x.y`` at <https://launchpad.net/bzr/+addseries>.
119
#. Add milestones at <https://launchpad.net/bzr/x.y/+addmilestone> to that
120
series for the beta releases and the stable series mentioning their
121
expected dates. Only the milestone associated to the next release in
122
this series should be left active to avoid clutter when targeting bugs.
124
#. If you made a new series, you will need to create a new pqm-controlled
125
branch for this release series. This branch will be used only from the
126
first non-beta release onwards. It needs to be created by a Canonical
127
sysadmin (ask the core devs for instructions or to do it for you).
129
#. Start a new release-notes file::
131
cd doc/en/release-notes
132
cp series-template.txt bzr-x.y.txt # e.g. bzr-2.3.txt
135
#. Start a new whats-new file::
138
cp template.txt bzr-x.y.txt # e.g. bzr-2.6.txt
141
#. Update ``doc/en/index.txt`` to point to the new whats-new file.
80
143
At the start of a release cycle
81
144
===============================
83
146
To start a new release cycle:
85
#. If this is the first release for a given *x.y* then create a new
86
series at <https://launchpad.net/bzr/+addseries>. There is one series
87
for every *x.y* release.
89
#. If you made a new series, create a new pqm-controlled branch for this
90
release series, by asking a Canonical sysadmin. This branch means that
91
from the first release beta or candidate onwards, general development
92
continues on the trunk, and only specifically-targeted fixes go into
95
#. If you made a new series, add milestones at
96
<https://launchpad.net/bzr/x.y/+addmilestone> to that series for
97
the beta release, release candidate and the final release, and their
100
#. Create a new milestone <https://launchpad.net/bzr/x.y/+addmilestone>
101
and add information about this release. We will not use it yet, but it
102
will be available for targeting or nominating bugs.
104
148
#. Send mail to the list with the key dates, who will be the release
105
149
manager, and the main themes or targeted bugs. Ask people to nominate
106
150
objectives, or point out any high-risk things that are best done early,
107
151
or that interact with other changes. This is called the metronome mail
108
152
and is described in `Development cycles <cycle.html>`_.
110
#. Make a local branch for preparing this release. (Only for the first
111
release in a series, otherwise you should already have a branch.) ::
113
bzr branch trunk prepare-1.14
154
#. Make a local branch to prepare the release::
156
bzr branch lp:bzr/x.y x.y-dev
158
If you're doing your first beta release, branch from trunk::
160
bzr branch lp:bzr x.y-dev
162
Note that you will generally reuse the same branch for all releases in a
115
165
#. Configure pqm-submit for this branch, with a section like this (where
116
x.y is the version to release). **Or use hydrazine for easy use**
117
``~/.bazaar/locations.conf``::
166
``x.y`` is the series for your release). **Or use hydrazine for easier
167
setup** ``~/.bazaar/locations.conf``::
119
[/home/mbp/bzr/prepare-x.y]
169
[/home/mbp/bzr/x.y-dev]
120
170
pqm_email = Canonical PQM <pqm@bazaar-vcs.org>
121
171
submit_branch = http://bazaar.launchpad.net/~bzr-pqm/bzr/x.y
122
172
parent_branch = http://bazaar.launchpad.net/~bzr-pqm/bzr/x.y
123
public_branch = http://bazaar.example.com/prepare-x.y
173
public_branch = http://bazaar.example.com/x.y-dev
124
174
submit_to = bazaar@lists.canonical.com
125
175
smtp_server = mail.example.com:25
158
207
also mail the list to raise this issue in our process. Milestones are
159
208
found at <https://launchpad.net/bzr/+milestone/x.y.z>.
210
#. Merge into your branch all previous stable series fixes that haven't been
211
merged yet. For example, if you're releasing 2.6.x, make sure the fixes
212
on 2.5, 2.4, 2.3, etc have already been merged up::
216
and commit that merge in its own commit. This should happen only if the
217
devs landing changes in previous releases forgot to merge them up. Since
218
this can slow down the freeze, feel free to gently remind them about
219
their duties ;) If you feel unsafe resolving the conflicts or it's too
220
time consuming, contact the related devs and skip this merge.
161
222
#. In the release branch, update ``version_info`` in ``./bzrlib/__init__.py``.
162
223
Make sure the corresponding milestone exists.
163
224
Double check that ./bzr ``_script_version`` matches ``version_info``. Check
164
the output of ``bzr --version``.
225
the output of ``./bzr --version``.
166
227
For beta releases use::
168
version_info = (2, 1, 0, 'beta', SERIAL)
172
version_info = (2, 1, 0, 'beta', 1)
174
For release candidates use::
176
version_info = (2, 0, 1, 'candidate', SERIAL)
229
version_info = (2, 6, 0, 'beta', SERIAL)
233
version_info = (2, 6, 0, 'beta', 1)
178
235
For stable releases use::
180
version_info = (2, 1, 2, 'final', 0)
237
version_info = (2, 6, 0, 'final', 0)
182
239
#. Update the ``./doc/en/release-notes/`` section for this release.
241
Check that all news entries related to this release have been added in
242
the right section. For example, if you're releasing 2.6b2, the following
243
command should display a a single chuk diff for the 2.6b2 release::
245
bzr diff -rbzr-2.6b2.. doc/en/release-notes/bzr-2.6.txt
184
247
Fill out the date and a description of the release under the existing
185
header. If there isn't one, follow the instructions above for using the
186
``release-template.txt`` file.
188
See *2.1.1* or similar for an example of what this looks like.
190
#. Add a summary of the release into the "What's New" document.
248
header (the diff above will help you summarizing). If there isn't one,
249
follow the instructions above for using the ``release-template.txt`` file
250
and remind people that they should document their changes there ;)
252
See *2.6b1* or similar for an example of what this looks like.
254
#. Add or check the summary of the release into the "What's New" document.
256
If this is the first release in a new series make sure to update the
257
introduction mentioning:
259
* the date of this first release,
260
* until when the series is expected to be supported.
262
Looking at ``bzr annotate`` for previous series should give you the right
263
hints. The ``doc/en/_templates/index.html`` file should also be updated.
192
265
#. To check that all bugs mentioned in the release notes are actually
193
266
marked as closed in Launchpad, you can run
196
269
./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
271
As of 2011-07-18, all bugs mentioned in the output of the script requires
272
some sort of intervention (either changing the status if it's not 'Fix
273
Released' or setting a different milestone if the bug hasn't been
274
fixed). A few false positives may remain in the older series, don't let
275
this slow you down too much. This script accepts options you may find
276
useful, use ``./tools/check-newsbugs.py`` to display its usage (``-w``
277
will open each bug in your browser for example).
279
#. For beta releases update the translation template::
281
BZR_PLUGIN_PATH=-site make po/bzr.pot
283
This is especially important for the final beta release which is when
284
translations are frozen and translators are requested (see `The final
285
beta - branching and translations`_) to make the translations.
287
#. For stable releases update the translations::
289
bzr merge lp:~bzr-core/bzr/bzr-translations-export-x.y
201
291
#. Commit these changes to the release branch, using a command like::
203
bzr commit -m "Release 1.14."
293
bzr commit -m "Release 2.3.1"
205
295
The diff before you commit will be something like::
207
=== modified file 'NEWS'
208
--- NEWS 2008-09-17 23:09:18 +0000
209
+++ NEWS 2008-09-23 16:14:54 +0000
217
+This release includes many bug fixes and a few performance and feature
218
+improvements. ``bzr rm`` will now scan for missing files and remove them,
219
+like how ``bzr add`` scans for unknown files and adds them. A bit more
220
+polish has been applied to the stacking code. The b-tree indexing code has
221
+been brought in, with an eye on using it in a future repository format.
222
+There are only minor installer changes since bzr-1.7rc2.
224
bzr 1.7rc2 2008-09-17
225
---------------------
228
=== modified file 'bzrlib/__init__.py'
229
--- bzrlib/__init__.py 2008-09-16 21:39:28 +0000
230
+++ bzrlib/__init__.py 2008-09-23 16:14:54 +0000
232
# Python version 2.0 is (2, 0, 0, 'final', 0)." Additionally we use a
233
# releaselevel of 'dev' for unreleased under-development code.
235
-version_info = (1, 7, 0, 'candidate', 2)
236
+version_info = (1, 7, 0, 'final', 0)
239
# API compatibility version: bzrlib is currently API compatible with 1.7.
241
Note that the NEWS file formatting has evolved, this example needs to
297
=== modified file 'bzrlib/__init__.py'
298
--- bzrlib/__init__.py 2011-02-09 06:35:00 +0000
299
+++ bzrlib/__init__.py 2011-03-10 10:24:47 +0000
301
# Python version 2.0 is (2, 0, 0, 'final', 0)." Additionally we use a
302
# releaselevel of 'dev' for unreleased under-development code.
304
-version_info = (2, 3, 1, 'dev', 0)
305
+version_info = (2, 3, 1, 'final', 0)
307
# API compatibility version
308
api_minimum_version = (2, 3, 0)
310
=== modified file 'doc/en/release-notes/bzr-2.3.txt'
311
--- doc/en/release-notes/bzr-2.3.txt 2011-03-09 08:30:16 +0000
312
+++ doc/en/release-notes/bzr-2.3.txt 2011-03-10 10:40:47 +0000
317
-:2.3.1: NOT RELEASED YET
319
-External Compatibility Breaks
320
-*****************************
322
-.. These may require users to change the way they use Bazaar.
327
-.. New commands, options, etc that users may wish to try out.
332
-.. Improvements to existing commands, especially improved performance
333
- or memory usage, or better results.
336
+This is a bugfix release. Upgrading is recommended for all users of earlier
342
=== modified file 'doc/en/whats-new/whats-new-in-2.3.txt'
343
--- doc/en/whats-new/whats-new-in-2.3.txt 2011-02-03 16:29:18 +0000
344
+++ doc/en/whats-new/whats-new-in-2.3.txt 2011-03-10 11:10:36 +0000
346
improvements made to the core product, it highlights enhancements within the
347
broader Bazaar world of potential interest to those upgrading.
349
-Bazaar 2.3.0 is fully compatible both locally and on the network with 2.0 2.1,
350
-and 2.2, and can read and write repositories generated by all previous
351
+Bazaar 2.3.1 includes all the fixes in the un-released 2.0.7, 2.1.4 and 2.2.5
352
+versions that weren't included in 2.3.0 and fixes some bugs on its own.
354
+See the :doc:`../release-notes/index` for details.
356
+Bazaar 2.3 is fully compatible both locally and on the network with 2.0, 2.1,
357
+and 2.2. It can read and write repositories generated by all previous
244
363
#. Tag the new release::
248
#. Push those changes to a bzr repository that is public and accessible on
249
the Internet. PQM will pull from this repository when it attempts to merge
250
your changes. Then submit those changes to PQM for merge into the
251
appropriate release branch::
367
#. Push those changes to a bzr branch that is public and accessible on the
368
Internet. PQM will pull from this branch when it attempts to merge your
369
changes. Then submit those changes to PQM for merge into the appropriate
254
bzr pqm-submit -m "(mbp) Release 1.14 (Martin Pool)"
373
bzr pqm-submit -m "(vila) Release 2.6.0 (Vincent Ladeuil)"
375
Note that ``bzr push`` should mention updating one tag (which you just
376
created). If it doesn't, double-check that you created (and pushed) this
256
379
Or with hydrazine::
300
432
<https://bugs.launchpad.net/launchpad/+bug/586445>
303
Announcing the source freeze
304
----------------------------
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.
314
435
Kick off the next cycle
315
436
-----------------------
317
#. To let developers work on the next release, do
318
`At the start of a release cycle` now.
320
#. Pause for a few days.
438
From that point, there is no possible return, the tarball has been uploaded
439
so you can relax a bit.
441
You're still holding a "social" lock on the launchpad branch though. Until
442
your start the next cycle, nobody should land anything on this branch. If
443
they do, they either targeted the wrong branch or didn't update the news
444
file correctly, so the sooner the branch is opened again, the better.
446
This matters more for ``lp:bzr`` than for ``lp:bzr/x.y``, ``lp:bzr`` should
447
always be open for landing, so you should do `At the start of a release
448
cycle`_ as soon as possible (i.e. update the version number in ``bzr`` and
449
``bzrlib/__init__``, create/update the news files and create/update the
450
milestone for the next relase).
452
You may also need to do `At the start of a series cycle`_ if you're starting
455
The final beta - branching and translations
456
-------------------------------------------
458
A word of caution: the instructions above works well for all releases but
459
there is one special case that requires a bit more care: when you release
460
the *last* beta for a given ``x.y`` series (from trunk aka lp:bzr), you need
461
to setup *two* branches for the next cycle:
463
#. ``lp:bzr`` needs to be opened for the next *series* ``x.(y+1)``.
465
#. ``lp:bzr/x.y`` needs to be opened for the next *release* ``x.y.0`` in the
466
series. Since this is first real use of ``lp:bzr/x.y``, this is also the
467
deadline for the PQM branch to be created.
469
Both are important as ``lp:bzr`` should remain open so any change can be
470
landed, ``lp:bzr/x.y`` on the other hand should be ready to receive bug
473
``lp:bzr`` is generally more important as the bug fixes on ``lp:bzr/x.y``
474
won't be released sooner than a month from now whereas people may already
475
been waiting to land on ``lp:bzr``.
479
#. Open ``lp:bzr`` for ``x.(y+1)``
481
#. Create or update the ``x.y`` PQM branch based on whatever revision you
482
want to release. Since it takes time to create the PQM branch for the new
483
series you should plan to get it created a few days before you need it
484
and seed it with the revision from trunk you want to base your release of
485
(ask a LOSA for pulling this revision from trunk and pushing it to the
486
series branch (``lp:bzr/x.y``) when you're ready).
488
#. Release ``x.y.0`` from ``lp:bzr/x.y``
490
#. Open ``lp:bzr/x.y`` for bug fixes
492
You also need to ensure Launchpad is set up to import/export translations
493
for the new branch and inform translators.
495
#. Push the last beta release to a new branch::
497
bzr push lp:~bzr-core/bzr/bzr-translations-export-x.y
499
#. On the translations series synchronization settings page
500
<https://translations.launchpad.net/bzr/x.y/+translations-settings>
501
turn on ``Import template files`` then for exports click ``Choose a
502
target branch`` and point it at the branch you just pushed.
504
#. E-mail translators to announce that the forthcoming stable release of bzr
505
is ready for translations. Send to
506
``launchpad-translators@lists.launchpad.net`` and
507
``ubuntu-translators@lists.ubuntu.com``.
509
#. The series is now frozen for strings and API, see below for adding
510
that to the announcement.
512
Announcing the source freeze
513
----------------------------
515
#. Post to the ``bazaar@lists.canonical.com`` and
516
``bzr-packagers@lists.launchpad.net`` lists, saying that the source has
517
been frozen. Be extra clear that this is only a *source* release targeted
518
at packagers and installer builders (see
519
<https://bugs.launchpad.net/launchpad/+bug/645084>). This is the cue for
520
platform maintainers and plugin authors to update their code. This is
521
done before the general public announcement of the release.
523
The freeze announcement generally guess the date of the official public
524
announcement, for the most recent stable series (the one supported by the
525
installers and most of the distributions) it's generally a few days after
526
the freeze. For older series supported only via SRUs for Ubuntu, we don't
527
control the process as tightly so guessing the date is not appropriate.
529
For the final beta release include in your announcement a notice of
530
API and translation freezes noting that public methods should not
531
be removed or changed and strings should not be added or changed.
533
#. Pause for a few days.
323
536
Publishing the release
324
537
----------------------
326
539
There is normally a delay of a few days after the source freeze to allow
327
for binaries to be built on various platforms. Once they have been built,
540
for binaries to be built for various platforms. Once they have been built,
328
541
we have a releasable product. The next step is to make it generally
329
542
available to the world.
331
544
#. Go to the release web page at <https://launchpad.net/bzr/x.y/x.y.z>
333
#. Announce on the `Bazaar website <http://bazaar.canonical.com/>`_.
334
This page is edited via the lp:bzr-website branch. (Changes
546
#. Announce on the `Bazaar website <http://bazaar.canonical.com/>`_. This
547
page is edited in ``build.py`` in the lp:bzr-website branch. (Changes
335
548
pushed to this branch are refreshed by a cron job on escudero.)
337
550
#. Check that the documentation for this release is available in
338
<http://doc.bazaar.canonical.com>. It should be automatically build when the
339
branch is created, by a cron script ``update-bzr-docs`` on
340
``escudero``. As of today (2009-08-27) ``igc`` manually updates the
341
pretty version of it.
551
<http://doc.bazaar.canonical.com>. It should be automatically build when
552
the branch is created, by a cron script ``update-bzr-docs`` on
553
``escudero``. When the first release is created in a new series, a branch
554
needs to be created on ``escudero``::
556
ssh escudero.canonical.com
558
cd /srv/doc.bazaar.canonical.com/
559
bzr branch lp:bzr/2.7 bzr/bzr.2.7
561
And the ``bzr/bin/update-bzr-docs`` script needs to refer to it.
563
The ``lp:bzr-alldocs`` branch also needs to be updated when a new series
564
is introduced, see the ``README`` file there for more instructions
565
(looking at the branch history is also a good way to understand what
566
needs to be done and to document any policy changes).
344
568
Announcing the release
345
569
----------------------
402
626
``Links`` box are edited. This should rarely change except for the URLs
403
627
related to the latest stable release.
405
* New announcement: When doing a release (beta, candidates, final), put the
406
summary of the release (you can't embed URLs there, the moderation staff
407
remove them). Users can still access the releases notes via the ``Release
408
Notes`` URL in the ``Links`` box in the upper right area of the page.
410
* Set direct download: When releasing a new stable release, this should
411
point to the corresponding launchpad page:
412
<https://launchpad.net/bzr/x.y/x.y.z/>
629
* New announcement: When doing a release, put the summary of the release
630
(you can't embed URLs there, the moderation staff remove them). Users
631
can still access the releases notes via the ``Release Notes`` URL in
632
the ``Links`` box in the upper right area of the page. When doing the
633
first stable release in a series, delete the ``Unstable installers``
634
<https://launchpad.net/bzr/x.y/x.ybn> and ``Unstable source tarball``
635
<http://launchpad.net/bzr/x.y/x.ybn/+download/bzr-x.ybn.tar.gz>
636
links. Conversely, when creating the first beta in a development
637
series, create these links again. Check all links when doing other
414
640
#. Update `<http://en.wikipedia.org/wiki/Bazaar_(software)>`_ -- this should
415
be done for final releases but not for beta releases or Release Candidates.
417
#. Update the python package index: <http://pypi.python.org/pypi/bzr> - best
420
python setup.py register
422
Remember to check the results afterwards -- this should be done for
423
final releases but not for beta releases or Release Candidates.
425
To be able to register the release you must create an account on
426
<http://pypi.python.org/pypi> and have one of the existing owners of
427
the project add you to the group.
641
be done for the stable and beta releases.
643
#. Update the python package index: <http://pypi.python.org/pypi/bzr>
645
From the tarball created and tested earlier ::
647
twine upload -s ../bzr-2.7.0.tar.gz
649
Remember to check the results afterward -- this should be done for
650
stable releases but not for beta releases nor SRUs.
652
The ``twine`` command is provided by the ``twine`` package on Debian and
655
If in doubt, you can test with <https://testpypi.python.org/pypi> where
656
you can register yourself, register the bzr project and upload (and then
657
remove the upload and delete the project so a new release manager can
658
enjoy the same facilities). If the project already exists, have one of
659
the existing owners of the project add you to the group.
661
To use the pypi test site, you need to record your credentials for an
662
existing user (the registration process is manual and starts at
663
<https://testpypi.python.org/pypi?%3Aaction=register_form>.
665
Once registered, you can record your crdentials in your ``~/pypirc`` file
669
username:<login on testpypi>
670
password:<password on testpypi>
671
repository = https://testpypi.python.org/pypi
673
Registering the bzr project if doesn't exist is achieved with::
675
python setup.py -r https://testpypi.python.org/pypi register
677
Uploading is done with::
679
twine upload -r testpypi -s ../bzr-2.7.0.tar.gz
681
To be able to upload the release you must create an account on
682
<http://pypi.python.org/pypi> and have one of the existing owners of the
683
project add you to the group and update your ``[pypi]`` section in your
430
687
Merging the released code back to trunk
431
688
---------------------------------------
433
Merge the release branch back into the trunk. The
434
``doc/en/release-notes`` changes should be merged into the right place
435
because each release series has its own release-notes file, but
690
Merge the release branch back into the trunk. The ``doc/en/release-notes``
691
changes should be merged into the right place because each release series
692
has its own release-notes file, but double-check.
438
694
If it's not already done, advance the version number in ``bzr`` and
439
695
``bzrlib/__init__.py``. Submit this back into pqm for bzr.dev.
added
removed
doc/developers/releasing.txt
