11
:2.4.2: 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.
35
* Cope with Unix filesystems, such as smbfs, where chmod gives 'permission
36
denied'. (Martin Pool, #606537)
38
* When the ``limbo`` or ``pending-deletion`` directories exist, typically
39
because of an interrupted tree update, but are empty, bzr no longer
40
errors out, because there is nothing for the user to clean up. Also,
41
errors in creation of these directories are no longer squelched.
42
(Martin Pool, #427773)
44
* During merges, when two entries end up using the same path for two
45
different file-ids (the same file being 'bzr added' in two different
46
branches) , 'duplicate' conflicts are created instead of 'content'
47
ones. This was previously leading to a 'Malformed tramsform' exception.
48
(Vincent Ladeuil, #880701)
50
* 'Malformed transform' exceptions are now recognized as internal errors
51
instead of user errors and report a traceback. This will reduce user
52
confusion as there is generally nothing users can do about them.
53
(Vincent Ladeuil, #880701)
55
* Prevent a traceback being printed to stderr when logging has problems and
56
accept utf-8 byte string without breaking. (Martin Packman, #714449)
61
.. Improved or updated documentation.
66
.. Changes that may require updates in plugins or other code that uses
72
.. Major internal changes, unlikely to be visible to users or plugin
73
developers, but interesting for bzr developers.
78
.. Fixes and changes that are only relevant to bzr's test framework and
79
suite. This can include new facilities for writing tests, fixes to
80
spurious test failures and changes to the way things should be tested.
82
* Account for slightly improved compression with newer versions of zlib in
83
``bt.test_btree_index`` tests. (Martin Packman, #940453)
91
This is a bugfix release. Most of the bugs dealt with portability
92
issues. Upgrading is recommended for all users of earlier 2.4 releases.
94
External Compatibility Breaks
95
*****************************
107
* Fixed a bug where ``bzr tags -r x..y`` loaded the branch history once for
108
every revision in the range; it's now much faster. (Vincent Ladeuil, #857335)
113
* Fixed an infinite loop when creating a repo at the root of the filesystem,
114
i.e. "/", due to posixpath.normpath() not collapsing 2 leading slashes into
115
one, thus respecting the POSIX standard, but making relpath() loop infinitely.
116
(Florian Vichot, #861008)
118
* Fixed loading of external merge tools from config to properly decode
119
command-lines which contain embedded quotes. (Gordon Tyler, #828803)
121
* Include declaration of 'changed' to avoid an UnboundLocalError in dirstate
122
pyrex code with new Cython versions. (Denys Duchier, #837221)
124
* Prevent several kinds of OverflowError and other fallout from failing to fit
125
stat fields into four bytes in dirstate pack_stat implementations.
126
(Martin Packman, #683191 #706957)
128
* Return early from create_delta_index_from_delta given tiny inputs. This
129
avoids raising a spurious MemoryError on certain platforms such as AIX.
130
(John Arbash Meinel, #856731)
135
* Corrected documentation for ``bzr serve`` in the Admin Guide.
136
(Morten Bøgeskov, Martin Pool, #832576)
151
* Accept both old and new style testtools output in selftest tests.
152
(Jelmer Vernooij, Martin Packman, #815423)
154
* Fix the race for TestingThreadingTCPServer in
155
test_server_crash_while_responding. (Vincent Ladeuil, #869366)
157
* Really corrupt the pack file without depending on a special length or value.
158
(Vincent Ladeuil, #807032)
166
This is a bugfix release. Upgrading is recommended for all users of earlier
169
It includes fixes from previous stable releases and address some issues with
173
External Compatibility Breaks
174
*****************************
176
.. These may require users to change the way they use Bazaar.
181
.. New commands, options, etc that users may wish to try out.
186
.. Improvements to existing commands, especially improved performance
187
or memory usage, or better results.
192
.. Fixes for situations where bzr would previously crash or give incorrect
193
or undesirable results.
195
* ``config.LocationMatcher`` properly excludes unrelated sections.
196
(Vincent Ladeuil, #829237)
198
* ``dirstate.fdatasync`` and ``repository.fdatasync`` can now properly be
199
disabled. (Vincent Ladeuil, #824513)
201
* Disable ``os.fsync`` and ``os.fdatasync`` by default when running
202
``bzr selftest``. You can use ``--sync`` to re-enable them.
203
(John Arbash Meinel, #837293)
205
* Fix i18n use when no environment variables are set. (Jelmer Vernooij, #810701)
207
* Avoid UnicodeDecode error when reporting EINVAL from transports.
208
(IWATA Hidetaka, #829237)
213
.. Improved or updated documentation.
215
* Corrected documentation for BZR_PROGRESS_BAR.
216
(Dennis Benzinger, #735417)
221
.. Changes that may require updates in plugins or other code that uses
227
.. Major internal changes, unlikely to be visible to users or plugin
228
developers, but interesting for bzr developers.
233
.. Fixes and changes that are only relevant to bzr's test framework and
234
suite. This can include new facilities for writing tests, fixes to
235
spurious test failures and changes to the way things should be tested.
237
* The test suite should now be able to run under weird environments where
238
``/etc/passwd`` doesn't contain the ``uid`` for the user running selftest
239
or where ``fakeroot`` is used but ``/root`` is inacessible.
240
(Vincent Ladeuil, #825027)
11
:2.4.0: NOT RELEASED YET
247
This release marks the start of a new long-term-stable series. From here, we
248
will only make bugfix releases on the 2.4 series (2.4.1, etc, and support it
249
until February 2013), while 2.5 will become our new development series.
251
This is a bugfix and polish release over the 2.3 series, with a large number
252
of bugs fixed (>150 for the 2.4 series alone), and some performance
253
improvements. Support for python 2.4 and 2.5 has been dropped, many large
254
working tree operations have been optimized as well as some stacked branches
257
Only bugfixes from other stables series have been included since 2.4b5 so
258
all known fixed bugs are included here.
260
Users are encouraged to upgrade from the other stable series.
13
263
External Compatibility Breaks
14
264
*****************************
32
282
.. Fixes for situations where bzr would previously crash or give incorrect
33
283
or undesirable results.
35
* Fix i18n use when no environment variables are set. (Jelmer Vernooij, #810701)
285
* A call to CHKInventory's filter-method will not result in a
286
DuplicateFileId error, if you move a subfolder and change a file in
288
(Bastian Bowe, #809901)
290
* Accessing a packaging branch on Launchpad (eg, ``lp:ubuntu/bzr``) now
291
checks to see if the most recent published source package version for
292
that project is present in the branch tags. This should help developers
293
trust whether the packaging branch is up-to-date and can be used for new
294
changes. The level of verbosity is controlled by the config item
295
``launchpad.packaging_verbosity``. It can be set to one of
302
only display if the branch is out-of-date
305
also display single-line up-to-date and missing,
309
(default) display multi-line content for all states
312
(John Arbash Meinel, #609187, #812928)
314
* Cope with not all Python versions having a ``clear`` method on
315
``TestCase._type_equality_funcs``.
316
(Martin [gz], Jelmer Vernooij, #809048)
318
* Fetching tags when fetching the tip revision of a branch is now
319
controlled by the config setting ``branch.fetch_tags``. The behavior has
320
been reverted to 2.3's not-fetching tagged revisions by default.
321
(John Arbash Meinel, #771184)
323
* The fix for bug #513709 caused us to open a new connection when
324
switching a lightweight checkout that was pointing at a bound branch.
325
This isn't necessary because we know the master URL without opening it,
326
avoiding an extra SSH connection, etc.
327
(John Arbash Meinel, #812285)