196
196
./tools/check-newsbugs.py doc/en/release-notes/bzr-x.y.txt
198
(As of 2011-03-10, only a few false positives remain. Don't let this slow
198
(As of 2011-12-03, only a few false positives remain. Don't let this slow
199
199
you down too much.)
201
201
#. Commit these changes to the release branch, using a command like::
203
bzr commit -m "Release 2.3.1"
203
bzr commit -m "Release 1.14."
205
205
The diff before you commit will be something like::
207
=== modified file 'bzrlib/__init__.py'
208
--- bzrlib/__init__.py 2011-02-09 06:35:00 +0000
209
+++ bzrlib/__init__.py 2011-03-10 10:24:47 +0000
211
# Python version 2.0 is (2, 0, 0, 'final', 0)." Additionally we use a
212
# releaselevel of 'dev' for unreleased under-development code.
214
-version_info = (2, 3, 1, 'dev', 0)
215
+version_info = (2, 3, 1, 'final', 0)
217
# API compatibility version
218
api_minimum_version = (2, 3, 0)
220
=== modified file 'doc/en/release-notes/bzr-2.3.txt'
221
--- doc/en/release-notes/bzr-2.3.txt 2011-03-09 08:30:16 +0000
222
+++ doc/en/release-notes/bzr-2.3.txt 2011-03-10 10:40:47 +0000
227
-:2.3.1: NOT RELEASED YET
229
-External Compatibility Breaks
230
-*****************************
232
-.. These may require users to change the way they use Bazaar.
237
-.. New commands, options, etc that users may wish to try out.
242
-.. Improvements to existing commands, especially improved performance
243
- or memory usage, or better results.
246
+This is a bugfix release. Upgrading is recommended for all users of earlier
252
=== modified file 'doc/en/whats-new/whats-new-in-2.3.txt'
253
--- doc/en/whats-new/whats-new-in-2.3.txt 2011-02-03 16:29:18 +0000
254
+++ doc/en/whats-new/whats-new-in-2.3.txt 2011-03-10 11:10:36 +0000
256
improvements made to the core product, it highlights enhancements within the
257
broader Bazaar world of potential interest to those upgrading.
259
-Bazaar 2.3.0 is fully compatible both locally and on the network with 2.0 2.1,
260
-and 2.2, and can read and write repositories generated by all previous
261
+Bazaar 2.3.1 includes all the fixes in the un-released 2.0.7, 2.1.4 and 2.2.5
262
+versions that weren't included in 2.3.0 and fixes some bugs on its own.
264
+See the :doc:`../release-notes/index` for details.
266
+Bazaar 2.3 is fully compatible both locally and on the network with 2.0, 2.1,
267
+and 2.2. It can read and write repositories generated by all previous
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
273
244
#. Tag the new release::
277
248
#. Push those changes to a bzr repository that is public and accessible on
278
249
the Internet. PQM will pull from this repository when it attempts to merge
433
405
* New announcement: When doing a release (beta, candidates, final), put the
434
406
summary of the release (you can't embed URLs there, the moderation staff
435
407
remove them). Users can still access the releases notes via the ``Release
436
Notes`` URL in the ``Links`` box in the upper right area of the
437
page. When doing the first stable release in a series, delete the
438
``Unstable installers`` <https://launchpad.net/bzr/x.y/x.ybn> and
439
``Unstable source tarball``
440
<http://launchpad.net/bzr/x.y/x.ybn/+download/bzr-x.ybn.tar.gz>
441
links. Conversely, when creating the first beta in a development series,
442
create these links again. Check all links when doing other kinds of
408
Notes`` URL in the ``Links`` box in the upper right area of the page.
445
410
* Set direct download: When releasing a new stable release, this should
446
411
point to the corresponding launchpad page:
added
removed
doc/developers/releasing.txt
