226
226
For beta releases use::
228
version_info = (2, 1, 0, 'beta', SERIAL)
232
version_info = (2, 1, 0, 'beta', 1)
228
version_info = (2, 5, 0, 'beta', SERIAL)
232
version_info = (2, 5, 0, 'beta', 5)
234
234
For stable releases use::
236
version_info = (2, 1, 2, 'final', 0)
236
version_info = (2, 5, 0, 'final', 0)
238
238
#. Update the ``./doc/en/release-notes/`` section for this release.
240
240
Check that all news entries related to this release have been added in
241
the right section. For example, if you're releasing 2.5b2, the following
242
command should display a a single chuk diff for the 2.5b2 release::
241
the right section. For example, if you're releasing 2.5b5, the following
242
command should display a a single chuk diff for the 2.5b5 release::
244
bzr diff -rbzr-2.5b1.. doc/en/release-notes/bzr-2.5.txt
244
bzr diff -rbzr-2.5b4.. doc/en/release-notes/bzr-2.5.txt
246
246
Fill out the date and a description of the release under the existing
247
247
header (the diff above will help you summarizing). If there isn't one,
248
248
follow the instructions above for using the ``release-template.txt`` file
249
249
and remind people that they should document their changes there ;)
251
See *2.1.1* or similar for an example of what this looks like.
251
See *2.5b5* or similar for an example of what this looks like.
253
253
#. Add or check the summary of the release into the "What's New" document.
271
271
BZR_PLUGIN_PATH=-site make po/bzr.pot
273
This is especially important for the final beta release which is
274
when translations are frozen and translators are requested to make
273
This is especially important for the final beta release which is when
274
translations are frozen and translators are requested (see `The final
275
beta - branching and translations`_) to make the translations.
277
277
#. For stable releases update the translations::
450
450
the *last* beta for a given ``x.y`` series (from trunk aka lp:bzr), you need
451
451
to setup *two* branches for the next cycle:
453
#. ``lp:bzr`` needs to be opened for the next *series* ``x.(y+1)``
453
#. ``lp:bzr`` needs to be opened for the next *series* ``x.(y+1)``.
455
455
#. ``lp:bzr/x.y`` needs to be opened for the next *release* ``x.y.0`` in the
456
456
series. Since this is first real use of ``lp:bzr/x.y``, this is also the
469
#. Create or update the ``x.y`` PQM branch based on whatever
470
revision you want to release
472
469
#. Open ``lp:bzr`` for ``x.(y+1)``
471
#. Create or update the ``x.y`` PQM branch based on whatever revision you
472
want to release. Since it takes time to create the PQM branch for the new
473
series you should plan to get it created a few days before you need it
474
and seed it with the revision from trunk you want to base your release of
475
(ask a LOSA for pulling this revision from trunk and pushing it to the
476
series branch (``lp:bzr/x.y``) when you're ready).
474
478
#. Release ``x.y.0`` from ``lp:bzr/x.y``
476
480
#. Open ``lp:bzr/x.y`` for bug fixes
478
You also need to ensure Launchpad is set up to import/export
479
translations for the new branch and inform translators.
482
You also need to ensure Launchpad is set up to import/export translations
483
for the new branch and inform translators.
485
#. Push the last beta release to a new branch::
483
487
bzr push lp:~bzr-core/bzr/bzr-translations-export-x.y
581
585
Feel free to tweak this to your taste.
583
587
#. Make an announcement through <https://launchpad.net/bzr/+announce>
588
mentioning the milestone URL <https://launchpad.net/bzr/+milestone/x.y.z>
589
so people get an easy access to details.
585
591
#. Announce on http://freecode.com/projects/bazaar-vcs
added
removed
doc/developers/releasing.txt
