11
:2.3.5: 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 cleanly with buggy HTTP proxies that close the socket in the middle
36
of a multipart response. (Martin Pool, #198646).
41
.. Improved or updated documentation.
46
.. Changes that may require updates in plugins or other code that uses
52
.. Major internal changes, unlikely to be visible to users or plugin
53
developers, but interesting for bzr developers.
58
.. Fixes and changes that are only relevant to bzr's test framework and
59
suite. This can include new facilities for writing tests, fixes to
60
spurious test failures and changes to the way things should be tested.
66
11
:Codename: One and counting
69
This is a bugfix release. Upgrading is recommended for all users of earlier
72
This mainly fixes bug #786980 which blocked the SRU process for Ubuntu Natty.
12
:2.3.4: NOT RELEASED YET
74
14
External Compatibility Breaks
75
15
*****************************
87
27
.. Improvements to existing commands, especially improved performance
88
28
or memory usage, or better results.
90
* Tweak an RPC implementation for ``Repository.get_parent_map``, it was
91
doing an inefficient ``small_set.difference_update(large_set)`` when we
92
can do ``small_set = small_set.difference(large_set)``. This speeds up
93
discovery time by about 10%. (John Arbash Meinel)
98
33
.. Fixes for situations where bzr would previously crash or give incorrect
99
34
or undesirable results.
101
* Accept some differences for ``bound_location`` from the config files that
102
were leading to a 'ReadOnlyError: A write attempt was made in a read only
103
transaction' error. (Vincent Ladeuil, #786980)
105
* Don't fail with traceback if `bzr serve` is running as a service on Windows,
106
and there is no USERNAME, nor BZR_EMAIL or other whoami-related environment
107
variables set. (Alexander Belchenko, Bug #660174)
114
41
* Updated the "Using stacked branches" section of the user guide to
115
42
describe committing to stacked branches and expanded its discussion of
116
pushing a stacked branch. (Andrew Bennetts)
43
pushing a stcked branch. (Andrew Bennetts)