25
25
bzr branch lp:bzr-pqm ~/.bazaar/plugins/pqm
27
Release provisional planning
28
============================
30
We currently maintain four series. Concurrently releasing them all at the
31
same time makes it harder to shorten the delay between the source
32
availability and the package building longer than necessary (we delay the
33
official announcement until most of our users can install the new release).
35
In order to continue to do time-based releases, we need to plan the
36
releases by series to minimize the collisions.
38
We want to respect the following rules::
40
* the most recent series should release once a month,
42
* the most recent stable series should release every other month (based
43
on the amount of bug fixes, this can be shorter or longer depending
44
on the bugs importance),
46
* previous series should relesase on a a regular basis without
47
interfering with the most recent series with a decreasing order of
48
priority (again this should be based on bugs importance and user
51
* the death of a series should be planned ahead of time. 6 months
52
should give enough time to our users to migrate to a more recent
55
* there should not be more than 2 releases in the same week (but the
56
Release Manager is free to ignore this (get in touch with packagers
59
* the series are aligned with Ubuntu releases for convenience since we
60
create a new series every 6 months. This means that we support the
61
stable series for 2 years. Note that we also propose the most recent
62
stable series via the ppa, so whether we keep supporting LTS directly
63
or via the ppa is still an open question.
69
The 2.3 series has entered the beta phase and 2.3.0 should be released soon
70
enough to be included into Natty Narwhal. This gives the following expected
88
The 2.2 series is the current stable release and is included in Maverick
89
Meerkat. The planned releases are::
103
The 2.1 series is the stable release included in Lucid Lynx. The planned
124
The 2.0 series is the stable release included in Karmic Koala. The planned
127
* 2.0.7: 2011-03 will be the last release for the 2.0 series.
28
144
At the start of a release cycle
29
145
===============================
235
354
this changes what the download widget on the Launchpad bzr home
236
355
page shows, so don't stop the release process yet, or platform binary
237
356
installers won't be made and the download list will stay very small!
238
<https://bugs.edge.launchpad.net/launchpad/+bug/586445>
357
<https://bugs.launchpad.net/launchpad/+bug/586445>
241
360
Announcing the source freeze
242
361
----------------------------
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
363
#. Post to the ``bazaar`` list, saying that the source has been frozen
364
(gone gold). Be extra clear that this is only a *source* release
365
targeted at packagers and installer builders (see
366
<https://bugs.launchpad.net/launchpad/+bug/645084>). This is the cue
367
for platform maintainers and plugin authors to update their code. This
368
is done before the general public announcement of the release.
250
371
Kick off the next cycle
301
422
Subject: bzr x.y.z released!
303
<<Summary paragraph from news>>
305
424
The Bazaar team is happy to announce availability of a new
306
425
release of the bzr adaptive version control system.
307
426
Bazaar is part of the GNU system <http://gnu.org/>.
428
<<Summary paragraph from news>>
309
430
Thanks to everyone who contributed patches, suggestions, and
402
523
**After making a bzr stable-release release, nominate the most serious bug
403
524
for the appropriate Ubuntu release and subscribe the `ubuntu-sru` team.**
526
This requires a couple of tricks (please reconsider and tweak as things
527
evolves from one release to the other):
529
* create a distro task with the ``Also affects distribution`` button and
530
select ``bzr (Ubuntu)``.
532
* change the *URL* to point to ``ubuntu/+source/bzr`` instead of ``bzr``
533
(this is needed if you create the distro task but not if it exists
534
already). You should now be able to click the ``Nominate for release``
535
button and select the right Ubuntu release. As of September 2010, this
538
* ``maverick`` for the 2.2 series,
539
* ``lucid`` for the 2.1 series,
540
* ``karmic`` for the 2.0 series.
542
* Subscribe the ``~ubuntu-sru`` team to the bug.
544
* Add a comment targeted to ``~ubuntu-sru`` explaining the expectations
545
(we are targeting running the test suite during the build which, as of
546
September 2010, fails for known reasons that are currently addressed).
547
Search for bugs tagged with ``sru`` for examples and don't forget to tag
548
the bug you selected.
added
removed
doc/developers/releasing.txt
