Rev 4642: Feedback on the 2.0rc1 release. in file:///home/vila/src/bzr/bugs/releasing-clarified/
Vincent Ladeuil
v.ladeuil+lp at free.fr
Thu Aug 27 08:49:53 BST 2009
At file:///home/vila/src/bzr/bugs/releasing-clarified/
------------------------------------------------------------
revno: 4642
revision-id: v.ladeuil+lp at free.fr-20090827074953-awkgedabyzhj4vul
parent: pqm at pqm.ubuntu.com-20090826181204-7tnwrg25c2zi1x51
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: releasing-clarified
timestamp: Thu 2009-08-27 09:49:53 +0200
message:
Feedback on the 2.0rc1 release.
* doc/developers/releasing.txt:
Try clarifying the points that were unclear for me when cutting
2.0rc1 instead of 2.0beta1/
* bzrlib/__init__.py:
(_format_version_tuple): Add a beta example.
-------------- next part --------------
=== modified file 'bzrlib/__init__.py'
--- a/bzrlib/__init__.py 2009-08-26 10:26:54 +0000
+++ b/bzrlib/__init__.py 2009-08-27 07:49:53 +0000
@@ -70,6 +70,8 @@
1.2dev
>>> print _format_version_tuple((1, 1, 1, 'candidate', 2))
1.1.1rc2
+ >>> print bzrlib._format_version_tuple((2, 1, 0, 'beta', 1))
+ 2.1b1
>>> print _format_version_tuple((1, 4, 0))
1.4
>>> print _format_version_tuple((1, 4))
=== modified file 'doc/developers/releasing.txt'
--- a/doc/developers/releasing.txt 2009-08-26 03:20:32 +0000
+++ b/doc/developers/releasing.txt 2009-08-27 07:49:53 +0000
@@ -17,21 +17,50 @@
bzr branch lp:bzr-pqm ~/.bazaar/plugins/pqm
+
+Starting a cycle
+----------------
+
+To start a new release cycle:
+
+#. Create a new series at <https://launchpad.net/bzr/+addseries>. There is one
+ series for every *x.y* release.
+
+#. Enter that series at <https://launchpad.net/bzr/2.0>
+
+#. Create a new release at
+ <https://launchpad.net/bzr/2.0/+addrelease> and add
+ information about this release. We will not use it yet, but it
+ will be available for targeting or nominating bugs.
+
+#. Add milestones to that series for the beta release, release candidate and
+ the final release, and their expected dates.
+
+#. Update the version number in the ``bzr`` script, and the
+ ``bzrlib/__init__.py`` file.
+
+#. Send mail to the list with the key dates, who will be the release
+ manager, and the main themes or targeted bugs. Ask people to nominate
+ objectives, or point out any high-risk things that are best done early,
+ or that interact with other changes.
+
+
Starting the release phase
--------------------------
-When it's time to make the release candidate:
+When it's time to make the first beta release or release candidate:
+
+#. Create a new milestone at
+ <https://launchpad.net/bzr/2.0/+addmilestone> for the beta
+ release or release candidate.
#. We create a new pqm-controlled branch for this release series, by
asking a Canonical sysadmin.
- This branch means that from the first release candidate onwards,
+ This branch means that from the first release beat or candidate onwards,
general development continues on the trunk, and only
specifically-targetted fixes go into the release.
-#. Register the branch at <https://launchpad.net/products/bzr/+addbranch>
-
-#. Make a release candidate.
-
+#. Make a beta release or release candidate.
Preparing the tree for release
------------------------------
@@ -46,8 +75,8 @@
[/home/mbp/bzr/prepare-1.14]
pqm_email = Canonical PQM <pqm at bazaar-vcs.org>
- submit_branch = http://bazaar-vcs.org/bzr/bzr.1.14
- public_branch = http://bazaar.your-domain.com/bzr
+ submit_branch = lp:bzr/2.0
+ public_branch = lp:bzr/2.0
submit_to = bazaar at lists.canonical.com
smtp_server = mail.your-domain.com:25
@@ -56,7 +85,17 @@
#. In the release branch, update ``version_info`` in ``./bzrlib/__init__.py``.
Double check that ./bzr ``_script_version`` matches ``version_info``. Check
- the output of ``bzr --version``.
+ the output of ``bzr --version``.
+
+ For beta releases use::
+
+ version_info = (2, 1, 0, 'beta', 1)
+
+
+ For release candidates use::
+
+ version_info = (2, 0, 1, 'candidate', 1)
+
#. Add the date and release number to ``./NEWS``
@@ -111,7 +150,7 @@
# API compatibility version: bzrlib is currently API compatible with 1.7.
-#. Tag the new release::
+#. Tag the new release (only for final releases)::
bzr tag bzr-1.14
@@ -141,16 +180,20 @@
make check-dist-tarball
+ You may encounter failures while running the test suite caused
+ by your locally installed plugins. Use your own judgement to
+ decide if you can release with these failures. When in doubt,
+ disable the faulty plugins one by one until you get no more
+ failures.
+
Publishing the release
----------------------
-Now you have the releasable product. The next step is making it
+Now you have the beta or releasable product. The next step is making it
available to the world.
-#. In <https://launchpad.net/bzr/> click the "Release series" for this
- series, to take you to e.g. <https://launchpad.net/bzr/1.14>. Then
- click "Register a release", and add information about this release.
+go to the release
#. Within that release, upload the source tarball and zipfile and the GPG
signature. Or, if you prefer, use the
@@ -160,10 +203,11 @@
#. Announce on the `Bazaar home page <http://bazaar-vcs.org/>`_.
-#. Check that the documentation for this release is available in
- <http://doc.bazaar-vcs.org>. It should be automatically build when the
+#. Check that the documentation for this release is available in
+ <http://doc.bazaar-vcs.org>. It should be automatically build when the
branch is created, by a cron script ``update-bzr-docs`` on
- ``escudero``.
+ ``escudero``. As of today (2009-08-27, the cron script can be contacted
+ on IRC under the ``igc`` nick.
Announcing the release
@@ -173,12 +217,17 @@
#. Make an announcement mail.
- For release candidates, this is sent to the ``bazaar-announce`` and
- ``bazaar`` lists. For final releases, it should also be cc'd to
- ``info-gnu at gnu.org``, ``python-announce-list at python.org``,
- ``bug-directory at gnu.org``. In both cases, it is good to set
- ``Reply-To: bazaar at lists.canonical.com``, so that people who reply to
- the announcement don't spam other lists.
+ For release candidates or beta releases, this is sent to the ``bazaar``
+ list only to inform plugin authors and package or installer managers.
+
+ Once the installers are available, the mail can be sent to the
+ ``bazaar-announce`` list too.
+
+ For final releases, it should also be cc'd to ``info-gnu at gnu.org``,
+ ``python-announce-list at python.org``, ``bug-directory at gnu.org``.
+
+ In all cases, it is good to set ``Reply-To: bazaar at lists.canonical.com``,
+ so that people who reply to the announcement don't spam other lists.
The announce mail will look something like this::
@@ -208,12 +257,12 @@
#. Announce on http://freshmeat.net/projects/bzr/
- This should be done for both release candidates and final releases. If
- you do not have a Freshmeat account yet, ask one of the existing
- admins.
+ This should be done for beta releases, release candidates and final
+ releases. If you do not have a Freshmeat account yet, ask one of the
+ existing admins.
-#. Update `<http://en.wikipedia.org/wiki/Bazaar_(software)>`_ -- this should be done
-for final releases but not for Release Candidates.
+#. Update `<http://en.wikipedia.org/wiki/Bazaar_(software)>`_ -- this should
+ be done for final releases but not for beta releases or Release Candidates.
#. Update the python package index: <http://pypi.python.org/pypi/bzr> - best
done by running ::
@@ -240,28 +289,6 @@
at any time.
-Starting a cycle
-----------------
-
-To start a new release cycle:
-
-#. Send mail to the list with the key dates, who will be the release
- manager, and the main themes or targeted bugs. Ask people to nominate
- objectives, or point out any high-risk things that are best done early,
- or that interact with other changes.
-
-#. Add a new "series" in Launchpad at <https://launchpad.net/bzr/+addseries>.
- There is one series for every *x.y* release.
-
-#. Add milestones to that series for the release candidate and the final
- release, and their expected dates.
-
-#. Deactivate old releases and their milestones.
-
-#. Update the version number in the ``bzr`` script, and the
- ``bzrlib/__init__.py`` file.
-
-
See also
--------
More information about the bazaar-commits
mailing list