5
5
.. contents:: List of Releases
11
:2.2b3: NOT RELEASED YET
16
* An API break has been made to the lock_write method of ``Branch`` and
17
``Repository`` objects; they now return ``branch.BranchWriteLockResult``
18
and ``repository.RepositoryWriteLockResult`` objects. This makes
19
changing the API in future easier and permits some cleaner calling code.
25
* ``bzr commit`` accepts ``-p`` (for "patch") as a shorter name for
27
(Parth Malwankar, #571467)
29
* ``bzr ignore`` now supports a ``--default-rules`` option that displays
30
the default ignore rules used by bzr. The flag ``--old-default-rules``
31
is no longer supported by ``ignore``.
32
(Parth Malwankar, #538703)
34
* ``bzr pack`` now supports a ``--clean-obsolete-packs`` option that
35
can save disk space by deleting obsolete pack files created during the
37
(Parth Malwankar, #304320)
42
* ``.bazaar``, ``.bazaar/bazaar.conf`` and ``.bzr.log`` inherit user and
43
group ownership from the containing directory. This allow bzr to work
45
(Martin <gzlist@googlemail.com>, Parth Malwankar, #376388)
47
* ``bzr log --exclude-common-ancestry -r X..Y`` displays the revisions that
48
are part of Y ancestry but not part of X ancestry (aka the graph
50
(Vincent Ladeuil, #320119)
52
* ``bzr selftest --parallel=fork`` wait for its children avoiding zombies.
53
(Vincent Ladeuil, #566670)
55
* ``bzr selftest`` should not use ui.note() since it's not unicode safe.
56
(Vincent Ladeuil, #563997)
58
* Don't mention --no-strict when we just issue the warning about unclean trees.
59
(Vincent Ladeuil, #401599)
61
* Fixed ``AssertionError`` when accessing smart servers running Bazaar
63
(Andrew Bennetts, #528041)
65
* Reduce peak memory by one copy of compressed text.
66
(John Arbash Meinel, #566940)
68
* Show the filenames when a file rename fails so that the error will be
70
(Martin Pool, #491763)
75
* ``append_revisions_only`` will now be interpreted as a boolean and a
76
warning emitted if illegal values are used. Note that for projects
77
that needs to maintain compatibility with previsous bzr versions,
78
only 'True' and 'False' strings must be used (previous versions of
79
bzr will interpret all strings differing from 'True'
80
(case-sensitive) as false.
81
(Brian de Alwis, Vincent Ladeuil)
83
* ``Config.get_user_option_as_bool`` will now warn if a value cannot
84
be interpreted as a boolean.
93
* Added ``bzrlib.merge.PerFileMerger``, a more convenient way to write
94
some kinds of ``merge_file_content`` hook functions.
97
* `BzrDir`, `Branch`, `Repository` and `WorkingTree` now all support `user_url`,
98
`user_transport`, `control_url` and `control_transport` members pointing
99
respectively to the directory containing the ``.bzr`` control directory,
100
and to the directory within ``.bzr`` used for the particular component.
101
All of them inherit from `ControlComponent` which provides default
105
* Lock methods on ``Tree``, ``Branch`` and ``Repository`` are now
106
expected to return an object which can be used to unlock them. This reduces
107
duplicate code when using cleanups. The previous 'tokens's returned by
108
``Branch.lock_write`` and ``Repository.lock_write`` are now attributes
109
on the result of the lock_write. ``repository.RepositoryWriteLockResult``
110
and ``branch.BranchWriteLockResult`` document this. (Robert Collins)
115
* ``log._get_info_for_log_files`` now takes an add_cleanup callable.
118
* ``_remember_remote_is_before`` no longer raises AssertionError when
119
suboptimal network behaviour is noticed; instead it just mutters to the
120
log file (and warns the user if they have set the ``hpss`` debug flag).
121
This was causing unnecessary aborts for performance bugs that are minor
123
(Andrew Bennetts, #528041)
125
* Permit bzr to run under ``python -OO`` which reduces the size of bytecode
126
files loaded from disk. To ensure docstrings needed for help are never
127
stripped, the prefix ``__doc__ =`` should now be used.
128
(Martin <gzlist@googlemail.com>)
133
* Added ``bzrlib.tests.matchers`` as a place to put matchers, along with
134
our first in-tree matcher. See the module docstring for details.
137
* ``bzr selftest --parallel=subprocess`` now works correctly on win32.
138
(Gordon Tyler, #551332)
140
* Workaround ``Crypto.Random`` check leading to spurious test
141
failures on Lucid, FreeBSD and gentoo.
142
(Vincent Ladeuil, #528436)
149
This is a somewhat early second beta of the 2.2 series, to fix a python2.4
150
incompatibility in the 2.2b1 release. It also includes a swag of
151
performance, usability and correctness improvements: test feedback on all
152
of these would be welcome.
11
:2.2b2: NOT RELEASED YET
164
* ``bzr dpush``, ``bzr push`` and ``bzr send`` will now issue a warning
165
instead of failing when dirty trees are involved. The corresponding
166
``dpush_strict``, ``push_strict`` and ``send_strict`` should be set to
167
True explicitly to get the previous behaviour.
168
(Vincent Ladeuil, #519319)
170
* ``bzr export`` to tar file does not fail if any parent directory
171
contains unicode characters. This works around upstream Python bug
172
http://bugs.python.org/issue8396 .
173
(Parth Malwankar, #413406)
175
* ``bzr switch`` does not die if a ConfigurableFileMerger is used.
176
(Aaron Bentley, #559436)
178
* ``bzr update`` when a pending merge in the working tree has been merged
179
into the master branch will no longer claim that old commits have become
180
pending merges. (Robert Collins, #562079)
182
* ``bzrlib.mutabletree.MutableTree.commit`` will now support a passed in
183
config as in previous versions of bzrlib. (Robert Collins)
185
* Fix glitch in the warning about unclean trees display.
186
(Vincent Ladeuil, #562665)
188
* Fixed Python2.4 incompatibilities in the bzr2.2b1 source tarball.
191
* Help messages generated by ``RegistryOption.from_kwargs`` list the
192
switches in alphabetical order, rather than in an undefined order.
193
(Martin von Gagern, #559409)
195
* Make sure the ``ExecutablePath`` and ``InterpreterPath`` are set in
196
Apport crash reports, to avoid "This problem report applies to a program
197
which is not installed any more" error.
198
(Martin Pool, James Westby, #528114)
200
* Reset ``siginterrupt`` flag to False every time we handle a signal
201
installed with ``set_signal_handler(..., restart_syscall=True)`` (from
202
``bzrlib.osutils``. Reduces the likelihood of "Interrupted System Call"
203
errors after two window resizes.
206
25
* When invoked with a range revision, ``bzr log`` doesn't show revisions
207
that are not part of the Y revisions ancestry anymore when invoked with
26
that are not part of the ancestry anymore.
209
27
(Vincent Ladeuil, #474807)
211
* Properly handle ``param_name`` attribute for ``ListOption``.
212
(Martin von Gagern, 387117)
217
* ``bzr commit`` will prompt before using a commit message that was
218
generated by a template and not edited by the user.
219
(Robert Collins, #530265)
221
* ``bzr diff`` read-locks the trees and branches only once, saving about
222
10-20ms on ``bzr diff`` in a bzr.dev tree.
225
* ``bzr missing`` read-locks the branches only once.
228
* ``bzr pull`` locks the branches and tree only once.
231
* Index lookups in pack repositories search recently hit pack files first.
232
In repositories with many pack files this can greatly reduce the
233
number of files accessed, the number of bytes read, and the number of
234
read calls. An incremental pull via plain HTTP takes half the time and
235
bytes for a moderately large repository. (Andrew Bennetts)
237
* Index lookups only re-order the indexes when the hit files aren't
238
already first. Reduces the cost of reordering
239
(John Arbash Meinel, #562429)
241
32
* Less code is loaded at startup. (Cold-cache start time is about 10-20%
243
34
(Martin Pool, #553017)
248
* ``bzrlib.diff.get_trees_and_branches_to_diff`` is deprecated. Use
249
``get_trees_and_branches_to_diff_locked`` instead.
255
* ``bzrlib.commands.Command.run_direct`` is no longer needed - the pre
256
2.1 method of calling run() to perform testing or direct use via the API
257
is now possible again. As part of this, the _operation attribute on
258
Command is now transient and only exists for the duration of ``run()``.
52
:2.2.0b1: Not released yet
266
54
Compatibility Breaks
267
55
********************
543
329
happens, and another warning will be written if the log file could not
544
330
be closed after retrying 100 times. (Andrew Bennetts, #531746)
549
:2.1.2: NOT RELEASED YET
554
* ``bzr switch`` does not die if a ConfigurableFileMerger is used.
555
(Aaron Bentley, #559436)
557
* Fixed ``AssertionError`` when accessing smart servers running Bazaar
559
(Andrew Bennetts, #528041)
561
* Reset ``siginterrupt`` flag to False every time we handle a signal
562
installed with ``set_signal_handler(..., restart_syscall=True)`` (from
563
``bzrlib.osutils``. Reduces the likelihood of "Interrupted System Call"
564
errors after two window resizes.
570
* ``_remember_remote_is_before`` no longer raises AssertionError when
571
suboptimal network behaviour is noticed; instead it just mutters to the
572
log file (and warns the user if they have set the ``hpss`` debug flag).
573
This was causing unnecessary aborts for performance bugs that are minor
575
(Andrew Bennetts, #528041)
993
741
tests that 'failed' - they're all just failures.
999
:2.0.6: NOT RELEASED YET
1004
* Additional merges after an unrelated branch has been merged with its
1005
history no longer crash when deleted files are involved.
1006
(Vincent Ladeuil, John Arbash Meinel, #375898)
1008
* ``bzr revert`` now only takes write lock on working tree, instead of on
1009
both working tree and branch.
1010
(Danny van Heumen, #498409)
1012
* ``bzr upgrade`` now creates the ``backup.bzr`` directory with the same
1013
permissions as ``.bzr`` directory on a POSIX OS.
1014
(Parth Malwankar, #262450)
1016
* Repositories accessed via a smart server now reject being stacked on a
1017
repository in an incompatible format, as is the case when accessing them
1018
via other methods. This was causing fetches from those repositories via
1019
a smart server (e.g. using ``bzr branch``) to receive invalid data.
1020
(Andrew Bennetts, #562380)
1027
This fifth release in our 2.0 series addresses several user-inconvenience
1028
bugs. None are critical, but upgrading is recommended for all users on
1029
earlier 2.0 releases.
749
:2.0.5: NOT RELEASED YET
added
removed
NEWS
