3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
1 |
Releasing Bazaar |
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
2 |
################ |
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
3 |
|
4 |
This document describes the processes for making and announcing a Bazaar |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
5 |
release, and managing the release process. This is just one phase of the |
5370.1.2
by John Arbash Meinel
Small tweaks to releasing urls. |
6 |
`overall development cycle <http://doc.bazaar.canonical.com/developers/cycle.html>`_, |
7 |
but it's the most complex part. This document gives a checklist you can |
|
8 |
follow from start to end in one go. |
|
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
9 |
|
4634.13.4
by Vincent Ladeuil
More tweaks. |
10 |
If you're helping the Release Manager (RM) for one reason or another, you |
11 |
may notice that he didn't follow that document scrupulously. He may have |
|
4634.13.6
by Vincent Ladeuil
Fixed as per Ian's review. |
12 |
good reasons to do that but he may also have missed some parts. |
4634.13.4
by Vincent Ladeuil
More tweaks. |
13 |
|
14 |
Follow the document yourself and don't hesitate to create the missing |
|
15 |
milestones for example (we tend to forget these ones a lot). |
|
16 |
||
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
17 |
.. contents:: |
18 |
||
4584.2.1
by Martin Pool
Update release cycle doc for 6m cycles |
19 |
|
4632.2.1
by Martin Pool
Release docs: bzr-pqm is a precondition not part of the every-release process |
20 |
Preconditions |
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
21 |
============= |
4632.2.1
by Martin Pool
Release docs: bzr-pqm is a precondition not part of the every-release process |
22 |
|
23 |
#. Download the pqm plugin and install it into your ``~/.bazaar/plugins``:: |
|
24 |
||
25 |
bzr branch lp:bzr-pqm ~/.bazaar/plugins/pqm |
|
26 |
||
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
27 |
|
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
28 |
At the start of a release cycle |
29 |
=============================== |
|
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
30 |
|
31 |
To start a new release cycle: |
|
32 |
||
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
33 |
#. If this is the first release for a given *x.y* then create a new |
34 |
series at <https://launchpad.net/bzr/+addseries>. There is one series |
|
35 |
for every *x.y* release. |
|
36 |
||
37 |
#. If you made a new series, create a new pqm-controlled branch for this |
|
38 |
release series, by asking a Canonical sysadmin. This branch means that |
|
39 |
from the first release beta or candidate onwards, general development |
|
40 |
continues on the trunk, and only specifically-targeted fixes go into |
|
41 |
the release branch. |
|
42 |
||
43 |
#. If you made a new series, add milestones at |
|
44 |
<https://edge.launchpad.net/bzr/x.y/+addmilestone> to that series for |
|
45 |
the beta release, release candidate and the final release, and their |
|
46 |
expected dates. |
|
47 |
||
48 |
#. Create a new milestone <https://edge.launchpad.net/bzr/x.y/+addmilestone> |
|
49 |
and add information about this release. We will not use it yet, but it |
|
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
50 |
will be available for targeting or nominating bugs. |
51 |
||
52 |
#. Send mail to the list with the key dates, who will be the release |
|
53 |
manager, and the main themes or targeted bugs. Ask people to nominate |
|
54 |
objectives, or point out any high-risk things that are best done early, |
|
4634.13.2
by Vincent Ladeuil
Fixed as per Martin's review. |
55 |
or that interact with other changes. This is called the metronome mail |
4634.13.4
by Vincent Ladeuil
More tweaks. |
56 |
and is described in `Development cycles <cycle.html>`_. |
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
57 |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
58 |
#. Make a local branch for preparing this release. (Only for the first |
3464.3.6
by Martin Pool
Release process updates |
59 |
release in a series, otherwise you should already have a branch.) :: |
60 |
||
4104.7.1
by Robert J. Tanner
Updated the releasing.html document, adding some documentation on things I had |
61 |
bzr branch trunk prepare-1.14 |
62 |
||
4675.2.2
by Robert Collins
Replace bazaar-vcs.org/bzr/ references with launchpad hosting urls in developer docs. |
63 |
#. Configure pqm-submit for this branch, with a section like this (where |
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
64 |
x.y is the version to release). **Or use hydrazine for easy use** |
3464.3.6
by Martin Pool
Release process updates |
65 |
``~/.bazaar/locations.conf``:: |
66 |
||
4675.2.2
by Robert Collins
Replace bazaar-vcs.org/bzr/ references with launchpad hosting urls in developer docs. |
67 |
[/home/mbp/bzr/prepare-x.y] |
3464.3.6
by Martin Pool
Release process updates |
68 |
pqm_email = Canonical PQM <pqm@bazaar-vcs.org> |
4675.2.2
by Robert Collins
Replace bazaar-vcs.org/bzr/ references with launchpad hosting urls in developer docs. |
69 |
submit_branch = http://bazaar.launchpad.net/~bzr-pqm/bzr/x.y |
4820.1.1
by Vincent Ladeuil
Further clarifications on building releases |
70 |
parent_branch = http://bazaar.launchpad.net/~bzr-pqm/bzr/x.y |
4675.2.2
by Robert Collins
Replace bazaar-vcs.org/bzr/ references with launchpad hosting urls in developer docs. |
71 |
public_branch = http://bazaar.example.com/prepare-x.y |
3464.3.6
by Martin Pool
Release process updates |
72 |
submit_to = bazaar@lists.canonical.com |
4634.13.2
by Vincent Ladeuil
Fixed as per Martin's review. |
73 |
smtp_server = mail.example.com:25 |
4104.7.1
by Robert J. Tanner
Updated the releasing.html document, adding some documentation on things I had |
74 |
|
5370.1.2
by John Arbash Meinel
Small tweaks to releasing urls. |
75 |
Please see <http://doc.bazaar.canonical.com/developers/HACKING.html#an-overview-of-pqm> |
4070.10.13
by Martin Pool
Remove or correct broken links |
76 |
for more details on PQM |
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
77 |
|
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
78 |
#. Update the version number in the ``bzr`` script, and the |
79 |
``bzrlib/__init__.py`` file:: |
|
80 |
||
81 |
version_info = (x, y, z, 'dev', 0) |
|
82 |
||
83 |
#. Add a new section at the top of ``NEWS`` about the new release, |
|
84 |
including its version number and the headings from |
|
85 |
``NEWS-template.txt``. |
|
86 |
||
5050.19.1
by Martin Pool
Mention the need to maintain the 'what's new' document |
87 |
#. Update the "What's New" documents in ``doc/en/whats-new``. |
88 |
||
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
89 |
#. Commit this and send it to PQM. |
90 |
||
91 |
||
92 |
Doing a particular release |
|
93 |
========================== |
|
94 |
||
95 |
Update the source code |
|
96 |
---------------------- |
|
97 |
||
98 |
#. Check that there is a milestone for the release you're doing. If there |
|
99 |
is no milestone it indicates a process problem - make the milestone but |
|
100 |
also mail the list to raise this issue in our process. Milestones are |
|
101 |
found at <https://launchpad.net/bzr/+milestone/x.y.z>. |
|
102 |
||
4152.2.7
by Robert J. Tanner
Added explicit instructions to check ./bzr _script_version ./bzrlib/__init__.py |
103 |
#. In the release branch, update ``version_info`` in ``./bzrlib/__init__.py``. |
4634.13.4
by Vincent Ladeuil
More tweaks. |
104 |
Make sure the corresponding milestone exists. |
4152.2.7
by Robert J. Tanner
Added explicit instructions to check ./bzr _script_version ./bzrlib/__init__.py |
105 |
Double check that ./bzr ``_script_version`` matches ``version_info``. Check |
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
106 |
the output of ``bzr --version``. |
107 |
||
108 |
For beta releases use:: |
|
109 |
||
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
110 |
version_info = (2, 1, 0, 'beta', SERIAL) |
111 |
||
112 |
For instance 2.1b1:: |
|
113 |
||
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
114 |
version_info = (2, 1, 0, 'beta', 1) |
115 |
||
116 |
For release candidates use:: |
|
117 |
||
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
118 |
version_info = (2, 0, 1, 'candidate', SERIAL) |
119 |
||
120 |
For stable releases use:: |
|
121 |
||
122 |
version_info = (2, 1, 2, 'final', 0) |
|
123 |
||
5050.19.1
by Martin Pool
Mention the need to maintain the 'what's new' document |
124 |
#. Update the ``./NEWS`` section for this release. |
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
125 |
|
126 |
Fill out the date and a description of the release under the existing |
|
127 |
header. If there isn't one, follow the above for using the NEWS |
|
128 |
template. |
|
129 |
||
130 |
See *2.1.1* or similar for an example of what this looks like. |
|
4634.13.4
by Vincent Ladeuil
More tweaks. |
131 |
|
5050.19.1
by Martin Pool
Mention the need to maintain the 'what's new' document |
132 |
#. Add a summary of the release into the "What's New" document. |
133 |
||
3966.2.6
by Jelmer Vernooij
Mention check-newsbugs.py in the release document. |
134 |
#. To check that all bugs mentioned in ``./NEWS`` are actually marked as |
135 |
closed in Launchpad, you can run ``tools/check-newsbugs.py``:: |
|
136 |
||
137 |
./tools/check-newsbugs.py NEWS |
|
138 |
||
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
139 |
(But note there will be many false positives, and this script may be |
4632.2.2
by Martin Pool
Minor ReST tweak |
140 |
flaky <https://bugs.edge.launchpad.net/bzr/+bug/354985>. Don't let |
141 |
this slow you down too much.) |
|
4595.6.2
by Martin Pool
Guidance on using check-newsbugs when releasing |
142 |
|
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
143 |
#. Commit these changes to the release branch, using a command like:: |
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
144 |
|
145 |
bzr commit -m "Release 1.14." |
|
146 |
||
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
147 |
The diff before you commit will be something like:: |
148 |
||
3778.2.2
by John Arbash Meinel
Rewrap some doc text, update the diff hunk to be accurate for current NEWS. |
149 |
=== modified file 'NEWS' |
150 |
--- NEWS 2008-09-17 23:09:18 +0000 |
|
151 |
+++ NEWS 2008-09-23 16:14:54 +0000 |
|
152 |
@@ -4,6 +4,23 @@ |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
153 |
|
3778.2.2
by John Arbash Meinel
Rewrap some doc text, update the diff hunk to be accurate for current NEWS. |
154 |
.. contents:: |
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
155 |
|
3778.2.2
by John Arbash Meinel
Rewrap some doc text, update the diff hunk to be accurate for current NEWS. |
156 |
+bzr 1.7 2008-09-23 |
157 |
+------------------ |
|
158 |
+ |
|
159 |
+This release includes many bug fixes and a few performance and feature |
|
160 |
+improvements. ``bzr rm`` will now scan for missing files and remove them, |
|
161 |
+like how ``bzr add`` scans for unknown files and adds them. A bit more |
|
162 |
+polish has been applied to the stacking code. The b-tree indexing code has |
|
163 |
+been brought in, with an eye on using it in a future repository format. |
|
164 |
+There are only minor installer changes since bzr-1.7rc2. |
|
165 |
+ |
|
166 |
bzr 1.7rc2 2008-09-17 |
|
167 |
--------------------- |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
168 |
|
169 |
||
3778.2.2
by John Arbash Meinel
Rewrap some doc text, update the diff hunk to be accurate for current NEWS. |
170 |
=== modified file 'bzrlib/__init__.py' |
171 |
--- bzrlib/__init__.py 2008-09-16 21:39:28 +0000 |
|
172 |
+++ bzrlib/__init__.py 2008-09-23 16:14:54 +0000 |
|
173 |
@@ -41,7 +41,7 @@ |
|
174 |
# Python version 2.0 is (2, 0, 0, 'final', 0)." Additionally we use a |
|
175 |
# releaselevel of 'dev' for unreleased under-development code. |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
176 |
|
3778.2.2
by John Arbash Meinel
Rewrap some doc text, update the diff hunk to be accurate for current NEWS. |
177 |
-version_info = (1, 7, 0, 'candidate', 2) |
178 |
+version_info = (1, 7, 0, 'final', 0) |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
179 |
|
180 |
||
3778.2.2
by John Arbash Meinel
Rewrap some doc text, update the diff hunk to be accurate for current NEWS. |
181 |
# API compatibility version: bzrlib is currently API compatible with 1.7. |
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
182 |
|
4634.13.3
by Vincent Ladeuil
Fix rst formatting issues. |
183 |
#. Tag the new release:: |
3997.2.1
by Jelmer Vernooij
Add tagging to the release process. |
184 |
|
4104.7.1
by Robert J. Tanner
Updated the releasing.html document, adding some documentation on things I had |
185 |
bzr tag bzr-1.14 |
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
186 |
|
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
187 |
#. Push those changes to a bzr repository that is public and accessible on |
4152.2.2
by Robert J. Tanner
Updated to releasing.txt based on my experiences as the release manager for |
188 |
the Internet. PQM will pull from this repository when it attempts to merge |
189 |
your changes. Then submit those changes to PQM for merge into the |
|
190 |
appropriate release branch:: |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
191 |
|
3464.3.6
by Martin Pool
Release process updates |
192 |
bzr push |
4104.7.1
by Robert J. Tanner
Updated the releasing.html document, adding some documentation on things I had |
193 |
bzr pqm-submit -m "(mbp) prepare 1.14" |
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
194 |
|
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
195 |
Or with hydrazine:: |
196 |
||
197 |
bzr lp-propose -m "Release 1.14" --approve lp:bzr/1.14 |
|
198 |
feed-pqm bzr |
|
199 |
||
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
200 |
#. When PQM succeeds, pull down the master release branch. |
201 |
||
3464.3.6
by Martin Pool
Release process updates |
202 |
|
3383.2.4
by Martin Pool
Trim from the release instructions things that are now automated or unnecessary |
203 |
Making the source tarball |
204 |
------------------------- |
|
205 |
||
3408.1.3
by Martin Pool
More release process updates |
206 |
#. Change into the source directory and run :: |
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
207 |
|
3383.2.4
by Martin Pool
Trim from the release instructions things that are now automated or unnecessary |
208 |
make dist |
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
209 |
|
3408.1.3
by Martin Pool
More release process updates |
210 |
#. Now we'll try expanding this tarball and running the test suite |
211 |
to check for packaging problems:: |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
212 |
|
3408.1.3
by Martin Pool
More release process updates |
213 |
make check-dist-tarball |
3383.2.5
by Martin Pool
merge trunk |
214 |
|
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
215 |
You may encounter failures while running the test suite caused |
4634.13.2
by Vincent Ladeuil
Fixed as per Martin's review. |
216 |
by your locally installed plugins. Use your own judgment to |
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
217 |
decide if you can release with these failures. When in doubt, |
218 |
disable the faulty plugins one by one until you get no more |
|
219 |
failures. |
|
220 |
||
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
221 |
Remember that PQM has just tested everything too, this step is |
222 |
particularly testing that the pyrex extensions, which are updated |
|
223 |
by your local pyrex version when you run make dist, are in good |
|
224 |
shape. |
|
225 |
||
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
226 |
|
4676.6.1
by mbp at sourcefrog
Updates to release process docs. |
227 |
Publishing the source tarball |
228 |
----------------------------- |
|
229 |
||
230 |
#. Go to the relevant milestone page in Launchpad. |
|
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
231 |
|
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
232 |
#. Create a release of the milestone, and upload the source tarball and |
233 |
the GPG signature. Or, if you prefer, use the |
|
234 |
``tools/packaging/lp-upload-release`` script to do this. Note that |
|
235 |
this changes what the download widget on the Launchpad bzr home |
|
236 |
page shows, so don't stop the release process yet, or platform binary |
|
237 |
installers won't be made and the download list will stay very small! |
|
238 |
<https://bugs.edge.launchpad.net/launchpad/+bug/586445> |
|
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
239 |
|
4676.6.1
by mbp at sourcefrog
Updates to release process docs. |
240 |
|
241 |
Announcing the source freeze |
|
242 |
---------------------------- |
|
243 |
||
244 |
#. Post to the ``bazaar`` list, saying that the source has been frozen. |
|
245 |
This is the cue for platform maintainers and plugin authors to update |
|
246 |
their code. This is done before the general public announcement of the |
|
247 |
release. |
|
248 |
||
249 |
||
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
250 |
Kick off the next cycle |
251 |
----------------------- |
|
252 |
||
253 |
#. To let developers work on the next release, do |
|
254 |
`At the start of a release cycle` now. |
|
255 |
||
256 |
#. Pause for a few days. |
|
257 |
||
258 |
||
4676.6.1
by mbp at sourcefrog
Updates to release process docs. |
259 |
Publishing the release |
260 |
---------------------- |
|
261 |
||
262 |
There is normally a delay of a few days after the source freeze to allow |
|
263 |
for binaries to be built on various platforms. Once they have been built, |
|
264 |
we have a releasable product. The next step is to make it generally |
|
265 |
available to the world. |
|
266 |
||
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
267 |
#. Go to the release web page at <https://launchpad.net/bzr/x.y/x.y.z> |
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
268 |
|
5370.1.2
by John Arbash Meinel
Small tweaks to releasing urls. |
269 |
#. Announce on the `Bazaar website <http://bazaar.canonical.com/>`_. |
4634.67.1
by Ian Clatworthy
update release documentation to mention the new website |
270 |
This page is edited via the lp:bzr-website branch. (Changes |
271 |
pushed to this branch are refreshed by a cron job on escudero.) |
|
272 |
||
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
273 |
#. Check that the documentation for this release is available in |
5370.1.2
by John Arbash Meinel
Small tweaks to releasing urls. |
274 |
<http://doc.bazaar.canonical.com>. It should be automatically build when the |
3778.2.1
by Martin Pool
Updated release process documentation. |
275 |
branch is created, by a cron script ``update-bzr-docs`` on |
4634.13.2
by Vincent Ladeuil
Fixed as per Martin's review. |
276 |
``escudero``. As of today (2009-08-27) ``igc`` manually updates the |
277 |
pretty version of it. |
|
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
278 |
|
279 |
||
280 |
Announcing the release |
|
281 |
---------------------- |
|
282 |
||
283 |
Now that the release is publicly available, tell people about it. |
|
284 |
||
3778.2.1
by Martin Pool
Updated release process documentation. |
285 |
#. Make an announcement mail. |
286 |
||
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
287 |
For release candidates or beta releases, this is sent to the ``bazaar`` |
288 |
list only to inform plugin authors and package or installer managers. |
|
289 |
||
290 |
Once the installers are available, the mail can be sent to the |
|
291 |
``bazaar-announce`` list too. |
|
292 |
||
293 |
For final releases, it should also be cc'd to ``info-gnu@gnu.org``, |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
294 |
``python-announce-list@python.org``, ``bug-directory@gnu.org``. |
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
295 |
|
296 |
In all cases, it is good to set ``Reply-To: bazaar@lists.canonical.com``, |
|
297 |
so that people who reply to the announcement don't spam other lists. |
|
3778.2.1
by Martin Pool
Updated release process documentation. |
298 |
|
4439.1.2
by Martin Pool
Change release message template to a preformatted block so you can more easily copy and paste it into a mail. |
299 |
The announce mail will look something like this:: |
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
300 |
|
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
301 |
Subject: bzr x.y.z released! |
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
302 |
|
4439.1.2
by Martin Pool
Change release message template to a preformatted block so you can more easily copy and paste it into a mail. |
303 |
<<Summary paragraph from news>> |
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
304 |
|
305 |
The Bazaar team is happy to announce availability of a new |
|
4439.1.2
by Martin Pool
Change release message template to a preformatted block so you can more easily copy and paste it into a mail. |
306 |
release of the bzr adaptive version control system. |
4439.1.6
by Martin Pool
Tweak text about GNU in release template |
307 |
Bazaar is part of the GNU system <http://gnu.org/>. |
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
308 |
|
4439.1.2
by Martin Pool
Change release message template to a preformatted block so you can more easily copy and paste it into a mail. |
309 |
Thanks to everyone who contributed patches, suggestions, and |
310 |
feedback. |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
311 |
|
312 |
Bazaar is now available for download from |
|
5370.1.2
by John Arbash Meinel
Small tweaks to releasing urls. |
313 |
https://launchpad.net/bzr/2.x/2.x/ as a source tarball; packages |
4439.1.2
by Martin Pool
Change release message template to a preformatted block so you can more easily copy and paste it into a mail. |
314 |
for various systems will be available soon. |
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
315 |
|
4439.1.2
by Martin Pool
Change release message template to a preformatted block so you can more easily copy and paste it into a mail. |
316 |
<<NEWS section from this release back to the last major release>> |
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
317 |
|
4439.1.1
by Martin Pool
Release mails should mention bzr's a GNU project |
318 |
Feel free to tweak this to your taste. |
319 |
||
3815.1.1
by Martin Pool
Add Launchpad announcement to the release process |
320 |
#. Make an announcement through <https://launchpad.net/bzr/+announce> |
321 |
||
3778.2.2
by John Arbash Meinel
Rewrap some doc text, update the diff hunk to be accurate for current NEWS. |
322 |
#. Update the IRC channel topic. Use the ``/topic`` command to do this, |
323 |
ensuring the new topic text keeps the project name, web site link, etc. |
|
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
324 |
|
325 |
#. Announce on http://freshmeat.net/projects/bzr/ |
|
4853.1.1
by Patrick Regan
Removed trailing whitespace from files in doc directory |
326 |
|
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
327 |
This should be done for beta releases, release candidates and final |
328 |
releases. If you do not have a Freshmeat account yet, ask one of the |
|
329 |
existing admins. |
|
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
330 |
|
4634.13.1
by Vincent Ladeuil
Feedback on the 2.0rc1 release. |
331 |
#. Update `<http://en.wikipedia.org/wiki/Bazaar_(software)>`_ -- this should |
332 |
be done for final releases but not for beta releases or Release Candidates. |
|
3497.3.1
by Martin Pool
Add note to update GNU directory |
333 |
|
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
334 |
#. Update the python package index: <http://pypi.python.org/pypi/bzr> - best |
335 |
done by running :: |
|
336 |
||
337 |
python setup.py register |
|
338 |
||
339 |
Remember to check the results afterwards. |
|
340 |
||
3408.1.3
by Martin Pool
More release process updates |
341 |
To be able to register the release you must create an account on |
342 |
<http://pypi.python.org/pypi> and have one of the existing owners of |
|
343 |
the project add you to the group. |
|
344 |
||
3383.2.3
by Martin Pool
Separate out and update the release manager instructions |
345 |
|
3383.2.5
by Martin Pool
merge trunk |
346 |
Merging the released code back to trunk |
347 |
--------------------------------------- |
|
348 |
||
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
349 |
The rule is to keep ``NEWS`` sections sorted by date. You'll need to |
350 |
review the merge and make sure that that is respected. |
|
351 |
||
3383.2.5
by Martin Pool
merge trunk |
352 |
Merge the release branch back into the trunk. Check that changes in NEWS |
353 |
were merged into the right sections. If it's not already done, advance |
|
354 |
the version number in ``bzr`` and ``bzrlib/__init__.py``. Submit this |
|
355 |
back into pqm for bzr.dev. |
|
356 |
||
4634.13.4
by Vincent Ladeuil
More tweaks. |
357 |
As soon as you change the version number in trunk, make sure you have |
358 |
created the corresponding milestone to ensure the continuity in bug |
|
4634.13.5
by Vincent Ladeuil
Mention creating the news series when changing the major or minor part of |
359 |
targeting or nominating. Depending on the change, you may even have to |
360 |
create a new series (if your change the major or minor release number), in |
|
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
361 |
that case go to `At the start of a release cycle` and follow the instructions from there. |
4634.13.4
by Vincent Ladeuil
More tweaks. |
362 |
|
4070.10.2
by Martin Pool
doc to maintain bzr/current branch |
363 |
You should also merge (not pull) the release branch into |
364 |
``lp:~bzr/bzr/current``, so that branch contains the current released code |
|
365 |
at any time. |
|
366 |
||
4634.13.4
by Vincent Ladeuil
More tweaks. |
367 |
Releases until the final one |
368 |
---------------------------- |
|
369 |
||
4634.13.6
by Vincent Ladeuil
Fixed as per Ian's review. |
370 |
Congratulations - you have made your first release. Have a beer |
371 |
or fruit juice - it's on the house! If it was a beta, or |
|
372 |
candidate, you're not finished yet. Another beta or candidate or |
|
373 |
hopefully a final release is still to come. |
|
374 |
||
5264.2.1
by Robert Collins
Improved our release checklist to have a bit less churn and leave things |
375 |
The process is the same as for the first release. Goto `Doing a |
376 |
particular release`_ and follow the instructions again. Some details change |
|
4634.13.4
by Vincent Ladeuil
More tweaks. |
377 |
between beta, candidate and final releases, but they should be |
4634.13.6
by Vincent Ladeuil
Fixed as per Ian's review. |
378 |
documented. If the instructions aren't clear enough, please fix them. |
4634.13.4
by Vincent Ladeuil
More tweaks. |
379 |
|
3383.2.5
by Martin Pool
merge trunk |
380 |
|
5430.5.1
by Martin Pool
Developer docs about SRUs of stable releases |
381 |
Getting the release into Ubuntu |
382 |
------------------------------- |
|
383 |
||
384 |
(Feel free to propose or add new sections here about what we should do to |
|
385 |
get bzr into other places.) |
|
386 |
||
387 |
For the currently-under-development release of Ubuntu, no special action |
|
388 |
is needed: the release should be picked by Debian and synced from there into |
|
389 |
Ubuntu. |
|
390 |
||
391 |
Releases off stable bzr branches should go in to the ``-updates`` of the |
|
392 |
Ubuntu release that originally contained that branch. (Ubuntu Lucid had |
|
393 |
bzr 2.2.0, so should get every 2.2.x update.) This means going through |
|
394 |
the `SRU (Stable Release Updates) |
|
395 |
<https://wiki.ubuntu.com/StableReleaseUpdates>`__ process. |
|
396 |
||
397 |
As of September 2010, bzr has applied to the technical board to be added |
|
398 |
to the `MicroReleaseExceptions |
|
399 |
<https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions>`__ |
|
400 |
category so that whole bugfix releases can more easily be approved. |
|
401 |
||
402 |
**After making a bzr stable-release release, nominate the most serious bug |
|
403 |
for the appropriate Ubuntu release and subscribe the `ubuntu-sru` team.** |
|
404 |
||
5430.4.5
by Vincent Ladeuil
Clarify SRU bug nomination. |
405 |
This requires a couple of tricks (please reconsider and tweak as things |
406 |
evolves from one release to the other): |
|
407 |
||
408 |
* create a distro task with the ``Also affects distribution`` button and |
|
409 |
select ``bzr (Ubuntu)``. |
|
410 |
||
411 |
* change the *URL* to point to ``ubuntu/+source/bzr`` instead of ``bzr`` |
|
412 |
(this is needed if you create the distro task but not if it exists |
|
413 |
already). You should now be able to click the ``Nominate for release`` |
|
414 |
button and select the right Ubuntu release. As of September 2010, this |
|
415 |
means: |
|
416 |
||
417 |
* ``maverick`` for the 2.2 series, |
|
418 |
* ``lucid`` for the 2.1 series, |
|
419 |
* ``karmic`` for the 2.0 series. |
|
420 |
||
421 |
* Subscribe the ``~ubuntu-sru`` team to the bug. |
|
422 |
||
423 |
* Add a comment targeted to ``~ubuntu-sru`` explaining the expectations |
|
424 |
(we are targeting running the test suite during the build which, as of |
|
425 |
September 2010, fails for known reasons that are currently addressed). |
|
426 |
Search for bugs tagged with ``sru`` for examples and don't forget to tag |
|
427 |
the bug you selected. |
|
428 |
||
5430.5.1
by Martin Pool
Developer docs about SRUs of stable releases |
429 |
|
3549.3.1
by Martin Pool
Updated instructions in packaging into the PPA |
430 |
See also |
431 |
-------- |
|
432 |
||
4070.10.3
by Martin Pool
Small ReST syntax fix |
433 |
* `Packaging into the bzr PPA <ppa.html>`_ to make and publish Ubuntu |
434 |
packages. |
|
435 |
* `Bazaar Developer Document Catalog <index.html>`_ |
|
436 |
* `Development cycles <cycle.html>`_: things that happen during the cycle |
|
437 |
before the actual release. |
|
3464.3.6
by Martin Pool
Release process updates |
438 |
|
439 |
.. |
|
3464.3.8
by Martin Pool
Doc updates re PPAs |
440 |
vim: filetype=rst textwidth=74 ai shiftwidth=4 |