5
5
.. contents:: List of Releases
11
:2.2b3: NOT RELEASED YET
19
* ``bzr commit`` accepts ``-p`` (for "patch") as a shorter name for
21
(Parth Malwankar, #571467)
23
* ``bzr ignore`` now supports a ``--default-rules`` option that displays
24
the default ignore rules used by bzr. The flag ``--old-default-rules``
25
is no longer supported by ``ignore``.
26
(Parth Malwankar, #538703)
28
* ``bzr pack`` now supports a ``--clean-obsolete-packs`` option that
29
can save disk space by deleting obsolete pack files created during the
31
(Parth Malwankar, #304320)
36
* ``.bazaar``, ``.bazaar/bazaar.conf`` and ``.bzr.log`` inherit user and
37
group ownership from the containing directory. This allow bzr to work
39
(Martin <gzlist@googlemail.com>, Parth Malwankar, #376388)
41
* ``bzr log --exclude-common-ancestry -r X..Y`` displays the revisions that
42
are part of Y ancestry but not part of X ancestry (aka the graph
44
(Vincent Ladeuil, #320119)
46
* ``bzr selftest --parallel=fork`` wait for its children avoiding zombies.
47
(Vincent Ladeuil, #566670)
49
* ``bzr selftest`` should not use ui.note() since it's not unicode safe.
50
(Vincent Ladeuil, #563997)
52
* Don't mention --no-strict when we just issue the warning about unclean trees.
53
(Vincent Ladeuil, #401599)
55
* Fixed ``AssertionError`` when accessing smart servers running Bazaar
57
(Andrew Bennetts, #528041)
59
* Reduce peak memory by one copy of compressed text.
60
(John Arbash Meinel, #566940)
62
* Show the filenames when a file rename fails so that the error will be
64
(Martin Pool, #491763)
69
* ``append_revisions_only`` will now be interpreted as a boolean and a
70
warning emitted if illegal values are used. Note that for projects
71
that needs to maintain compatibility with previsous bzr versions,
72
only 'True' and 'False' strings must be used (previous versions of
73
bzr will interpret all strings differing from 'True'
74
(case-sensitive) as false.
75
(Brian de Alwis, Vincent Ladeuil)
77
* ``Config.get_user_option_as_bool`` will now warn if a value cannot
78
be interpreted as a boolean.
87
* Added ``bzrlib.merge.PerFileMerger``, a more convenient way to write
88
some kinds of ``merge_file_content`` hook functions.
91
* `BzrDir`, `Branch`, `Repository` and `WorkingTree` now all support `user_url`,
92
`user_transport`, `control_url` and `control_transport` members pointing
93
respectively to the directory containing the ``.bzr`` control directory,
94
and to the directory within ``.bzr`` used for the particular component.
95
All of them inherit from `ControlComponent` which provides default
99
* Lock methods on ``Tree``, ``Branch`` and ``Repository`` are now
100
expected to return an object which can be used to unlock them. This reduces
101
duplicate code when using cleanups. The previous 'tokens's returned by
102
``Branch.lock_write`` and ``Repository.lock_write`` are now attributes
103
on the result of the lock_write. ``repository.RepositoryWriteLockResult``
104
and ``branch.BranchWriteLockResult`` document this. (Robert Collins)
109
* ``log._get_info_for_log_files`` now takes an add_cleanup callable.
112
* ``_remember_remote_is_before`` no longer raises AssertionError when
113
suboptimal network behaviour is noticed; instead it just mutters to the
114
log file (and warns the user if they have set the ``hpss`` debug flag).
115
This was causing unnecessary aborts for performance bugs that are minor
117
(Andrew Bennetts, #528041)
119
* Permit bzr to run under ``python -OO`` which reduces the size of bytecode
120
files loaded from disk. To ensure docstrings needed for help are never
121
stripped, the prefix ``__doc__ =`` should now be used.
122
(Martin <gzlist@googlemail.com>)
127
* Added ``bzrlib.tests.matchers`` as a place to put matchers, along with
128
our first in-tree matcher. See the module docstring for details.
131
* ``bzr selftest --parallel=subprocess`` now works correctly on win32.
132
(Gordon Tyler, #551332)
134
* Workaround ``Crypto.Random`` check leading to spurious test
135
failures on Lucid, FreeBSD and gentoo.
136
(Vincent Ladeuil, #528436)
143
This is a somewhat early second beta of the 2.2 series, to fix a python2.4
144
incompatibility in the 2.2b1 release. It also includes a swag of
145
performance, usability and correctness improvements: test feedback on all
146
of these would be welcome.
11
:2.2b2: NOT RELEASED YET
191
49
which is not installed any more" error.
192
50
(Martin Pool, James Westby, #528114)
194
* Reset ``siginterrupt`` flag to False every time we handle a signal
195
installed with ``set_signal_handler(..., restart_syscall=True)`` (from
196
``bzrlib.osutils``. Reduces the likelihood of "Interrupted System Call"
197
errors after two window resizes.
200
52
* When invoked with a range revision, ``bzr log`` doesn't show revisions
201
that are not part of the Y revisions ancestry anymore when invoked with
53
that are not part of the ancestry anymore.
203
54
(Vincent Ladeuil, #474807)
205
* Properly handle ``param_name`` attribute for ``ListOption``.
206
(Martin von Gagern, 387117)
537
393
happens, and another warning will be written if the log file could not
538
394
be closed after retrying 100 times. (Andrew Bennetts, #531746)
543
:2.1.2: NOT RELEASED YET
548
* ``bzr switch`` does not die if a ConfigurableFileMerger is used.
549
(Aaron Bentley, #559436)
551
* Fixed ``AssertionError`` when accessing smart servers running Bazaar
553
(Andrew Bennetts, #528041)
555
* Reset ``siginterrupt`` flag to False every time we handle a signal
556
installed with ``set_signal_handler(..., restart_syscall=True)`` (from
557
``bzrlib.osutils``. Reduces the likelihood of "Interrupted System Call"
558
errors after two window resizes.
564
* ``_remember_remote_is_before`` no longer raises AssertionError when
565
suboptimal network behaviour is noticed; instead it just mutters to the
566
log file (and warns the user if they have set the ``hpss`` debug flag).
567
This was causing unnecessary aborts for performance bugs that are minor
569
(Andrew Bennetts, #528041)
987
805
tests that 'failed' - they're all just failures.
993
:2.0.6: NOT RELEASED YET
998
* Additional merges after an unrelated branch has been merged with its
999
history no longer crash when deleted files are involved.
1000
(Vincent Ladeuil, John Arbash Meinel, #375898)
1002
* ``bzr revert`` now only takes write lock on working tree, instead of on
1003
both working tree and branch.
1004
(Danny van Heumen, #498409)
1006
* ``bzr upgrade`` now creates the ``backup.bzr`` directory with the same
1007
permissions as ``.bzr`` directory on a POSIX OS.
1008
(Parth Malwankar, #262450)
1010
* Repositories accessed via a smart server now reject being stacked on a
1011
repository in an incompatible format, as is the case when accessing them
1012
via other methods. This was causing fetches from those repositories via
1013
a smart server (e.g. using ``bzr branch``) to receive invalid data.
1014
(Andrew Bennetts, #562380)
1021
This fifth release in our 2.0 series addresses several user-inconvenience
1022
bugs. None are critical, but upgrading is recommended for all users on
1023
earlier 2.0 releases.
813
:2.0.5: NOT RELEASED YET
added
removed
NEWS
