196
196
./tools/check-newsbugs.py doc/en/release-notes/bzr-x.y.txt
198
As of 2011-05-26, only a few false positives remain in the older
199
series. Don't let this slow you down too much. This script accepts
200
options you may find useful, use ``./tools/check-newsbugs.py`` to display
198
(As of 2011-12-03, only a few false positives remain. Don't let this slow
203
201
#. Commit these changes to the release branch, using a command like::
205
bzr commit -m "Release 2.3.1"
203
bzr commit -m "Release 1.14."
207
205
The diff before you commit will be something like::
209
=== modified file 'bzrlib/__init__.py'
210
--- bzrlib/__init__.py 2011-02-09 06:35:00 +0000
211
+++ bzrlib/__init__.py 2011-03-10 10:24:47 +0000
213
# Python version 2.0 is (2, 0, 0, 'final', 0)." Additionally we use a
214
# releaselevel of 'dev' for unreleased under-development code.
216
-version_info = (2, 3, 1, 'dev', 0)
217
+version_info = (2, 3, 1, 'final', 0)
219
# API compatibility version
220
api_minimum_version = (2, 3, 0)
222
=== modified file 'doc/en/release-notes/bzr-2.3.txt'
223
--- doc/en/release-notes/bzr-2.3.txt 2011-03-09 08:30:16 +0000
224
+++ doc/en/release-notes/bzr-2.3.txt 2011-03-10 10:40:47 +0000
229
-:2.3.1: NOT RELEASED YET
231
-External Compatibility Breaks
232
-*****************************
234
-.. These may require users to change the way they use Bazaar.
239
-.. New commands, options, etc that users may wish to try out.
244
-.. Improvements to existing commands, especially improved performance
245
- or memory usage, or better results.
248
+This is a bugfix release. Upgrading is recommended for all users of earlier
254
=== modified file 'doc/en/whats-new/whats-new-in-2.3.txt'
255
--- doc/en/whats-new/whats-new-in-2.3.txt 2011-02-03 16:29:18 +0000
256
+++ doc/en/whats-new/whats-new-in-2.3.txt 2011-03-10 11:10:36 +0000
258
improvements made to the core product, it highlights enhancements within the
259
broader Bazaar world of potential interest to those upgrading.
261
-Bazaar 2.3.0 is fully compatible both locally and on the network with 2.0 2.1,
262
-and 2.2, and can read and write repositories generated by all previous
263
+Bazaar 2.3.1 includes all the fixes in the un-released 2.0.7, 2.1.4 and 2.2.5
264
+versions that weren't included in 2.3.0 and fixes some bugs on its own.
266
+See the :doc:`../release-notes/index` for details.
268
+Bazaar 2.3 is fully compatible both locally and on the network with 2.0, 2.1,
269
+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
275
244
#. Tag the new release::
279
248
#. Push those changes to a bzr repository that is public and accessible on
280
249
the Internet. PQM will pull from this repository when it attempts to merge
422
392
releases. If you do not have a Freshmeat account yet, ask one of the
425
The purpose here is to point users to the latest stable release while still
426
publishing announcements for development releases.
428
There are several kinds of modifications that could be done there via the
429
``Administration`` box in the lower right area of the page:
431
* Edit the project: This is where most of the URLs proposed in the
432
``Links`` box are edited. This should rarely change except for the URLs
433
related to the latest stable release.
435
* New announcement: When doing a release (beta, candidates, final), put the
436
summary of the release (you can't embed URLs there, the moderation staff
437
remove them). Users can still access the releases notes via the ``Release
438
Notes`` URL in the ``Links`` box in the upper right area of the
439
page. When doing the first stable release in a series, delete the
440
``Unstable installers`` <https://launchpad.net/bzr/x.y/x.ybn> and
441
``Unstable source tarball``
442
<http://launchpad.net/bzr/x.y/x.ybn/+download/bzr-x.ybn.tar.gz>
443
links. Conversely, when creating the first beta in a development series,
444
create these links again. Check all links when doing other kinds of
447
* Set direct download: When releasing a new stable release, this should
448
point to the corresponding launchpad page:
449
<https://launchpad.net/bzr/x.y/x.y.z/>
451
395
#. Update `<http://en.wikipedia.org/wiki/Bazaar_(software)>`_ -- this should
452
396
be done for final releases but not for beta releases or Release Candidates.
added
removed
doc/developers/releasing.txt
