11
:2.4.1: NOT RELEASED YET
13
External Compatibility Breaks
14
*****************************
16
.. These may require users to change the way they use Bazaar.
21
.. New commands, options, etc that users may wish to try out.
26
.. Improvements to existing commands, especially improved performance
27
or memory usage, or better results.
32
.. Fixes for situations where bzr would previously crash or give incorrect
33
or undesirable results.
38
.. Improved or updated documentation.
43
.. Changes that may require updates in plugins or other code that uses
49
.. Major internal changes, unlikely to be visible to users or plugin
50
developers, but interesting for bzr developers.
55
.. Fixes and changes that are only relevant to bzr's test framework and
56
suite. This can include new facilities for writing tests, fixes to
57
spurious test failures and changes to the way things should be tested.
65
This release marks the start of a new long-term-stable series. From here, we
66
will only make bugfix releases on the 2.4 series (2.4.1, etc, and support it
67
until February 2013), while 2.5 will become our new development series.
69
This is a bugfix and polish release over the 2.3 series, with a large number
70
of bugs fixed (>150 for the 2.4 series alone), and some performance
71
improvements. Support for python 2.4 and 2.5 has been dropped, many large
72
working tree operations have been optimized as well as some stacked branches
75
Only bugfixes from other stables series have been included since 2.4b5 so
76
all known fixed bugs are included here.
78
Users are encouraged to upgrade from the other stable series.
81
External Compatibility Breaks
82
*****************************
84
.. These may require users to change the way they use Bazaar.
89
.. New commands, options, etc that users may wish to try out.
94
.. Improvements to existing commands, especially improved performance
95
or memory usage, or better results.
100
.. Fixes for situations where bzr would previously crash or give incorrect
101
or undesirable results.
103
* A call to CHKInventory's filter-method will not result in a
104
DuplicateFileId error, if you move a subfolder and change a file in
106
(Bastian Bowe, #809901)
108
* Accessing a packaging branch on Launchpad (eg, ``lp:ubuntu/bzr``) now
109
checks to see if the most recent published source package version for
110
that project is present in the branch tags. This should help developers
111
trust whether the packaging branch is up-to-date and can be used for new
112
changes. The level of verbosity is controlled by the config item
113
``launchpad.packaging_verbosity``. It can be set to one of
120
only display if the branch is out-of-date
123
also display single-line up-to-date and missing,
127
(default) display multi-line content for all states
130
(John Arbash Meinel, #609187, #812928)
132
* Cope with not all Python versions having a ``clear`` method on
133
``TestCase._type_equality_funcs``.
134
(Martin [gz], Jelmer Vernooij, #809048)
136
* Fetching tags when fetching the tip revision of a branch is now
137
controlled by the config setting ``branch.fetch_tags``. The behavior has
138
been reverted to 2.3's not-fetching tagged revisions by default.
139
(John Arbash Meinel, #771184)
141
* The fix for bug #513709 caused us to open a new connection when
142
switching a lightweight checkout that was pointing at a bound branch.
143
This isn't necessary because we know the master URL without opening it,
144
avoiding an extra SSH connection, etc.
145
(John Arbash Meinel, #812285)
151
.. Improved or updated documentation.
156
.. Changes that may require updates in plugins or other code that uses
162
.. Major internal changes, unlikely to be visible to users or plugin
163
developers, but interesting for bzr developers.
168
.. Fixes and changes that are only relevant to bzr's test framework and
169
suite. This can include new facilities for writing tests, fixes to
170
spurious test failures and changes to the way things should be tested.
172
* `BranchBuilder.build_snapshot` now supports a "flush" action. This
173
cleanly and reliably allows tests using `BranchBuilder` to construct
174
branches that e.g. rename files out of a directory and unversion that
175
directory in the same revision. Previously some changes were impossible
176
due to the order that `build_snapshot` performs its actions.
179
* `TestCaseWithMemoryTransport` is faster now: `_check_safety_net` now
180
just compares the bytes in the dirstate file to its pristine state,
181
rather than opening the WorkingTree and calling ``last_revision()``.
182
This reduces the overall test suite time by about 10% on my laptop.
11
:2.4b5: NOT RELEASED YET
191
This is the fifth (and last) beta of the 2.4 series leading to
192
2.4.0 release in August 2011. Beta releases are suitable for
193
everyday use but may cause some incompatibilities with plugins.
195
This release includes all bug fixed in previous series known at
196
the time of this release.
13
198
External Compatibility Breaks
14
199
*****************************
16
.. These may require users to change the way they use Bazaar.
21
.. New commands, options, etc that users may wish to try out.
23
206
* New command ``verify-signatures`` to check if all commits or specified commits
24
207
have digital signatures from trusted keys. Requires python-gpgme to be
38
.. Improvements to existing commands, especially improved performance
39
or memory usage, or better results.
221
* ``Branch.open`` is now about 3x faster (about 2ms instead of 6.5ms).
224
* Pack, dirstate, and index files are synced to persistent storage if
225
possible when writing finishes, to reduce the risk of problems caused by
226
a machine crash or similar problem. This can be turned off through the
227
``dirstate.fdatasync`` and ``repository.fdatasync`` options, which can
228
be set in ``locations.conf`` or ``bazaar.conf``. (Martin Pool,
44
234
* Display a proper error message when a config file content cannot be
45
235
decoded as UTF-8 or when it cannot be parsed.
46
(Vincent Ladeuil, #502060, #688677, #792246)
236
(Vincent Ladeuil, #502060, #688677, #797246)
238
* Generate a single conflict (instead of two) when merging a branch
239
modifying and renaming a file in a branch that deleted it (or vice-versa).
240
(Vincent Ladeuil, #688101)
242
* Give a more helpful message when the bzr executable doesn't match the
243
library. (This typically happens because of a misconfigured PYTHONPATH
244
or half-installed bzr.)
245
(Martin Pool, #804553)
48
247
* Properly load utf8-encoded config files. (Vincent Ladeuil, #799212)
50
.. Fixes for situations where bzr would previously crash or give incorrect
51
or undesirable results.
56
.. Improved or updated documentation.
249
* ``GraphThunkIdsToKeys.merge_sort`` now properly returns
250
keys rather than ids. (Jelmer Vernooij, #799677)
252
* ``TreeTransformBase.fixup_new_roots`` can now check that a tree root
253
is present. (Jelmer Vernooij, #801257)
61
.. Changes that may require updates in plugins or other code that uses
258
* New attributes ``WorkingTreeFormat.supports_versioned_directories`` and
259
``RepositoryFormat.supports_versioned_directories``.
260
(Jelmer Vernooij, #765815)
262
* The "revno" field type when using the python version-info format is now
263
a string (to handle dotted revnos) (Benoît Pierre, #796259)
67
.. Major internal changes, unlikely to be visible to users or plugin
68
developers, but interesting for bzr developers.
268
* Start implementing localization, starting with command help text (but not
269
the command options themselves). This will allow bootstrapping the bzr
270
internationalization process. (Inada Naoki)
73
.. Fixes and changes that are only relevant to bzr's test framework and
74
suite. This can include new facilities for writing tests, fixes to
75
spurious test failures and changes to the way things should be tested.
77
275
* Fix test failures when running as a homeless user (debian buildd). Tests
78
276
leaking into ``${HOME}/.bzr.log`` should be detected properly now.
79
277
(Vincent Ladeuil, #798698)
added
removed
doc/en/release-notes/bzr-2.4.txt
