5
5
.. contents:: List of Releases
8
bzr 2.2.0b1 (not released yet)
9
##############################
12
:2.2.0b1: Not released yet
14
14
Compatibility Breaks
15
15
********************
17
* Deleted very old hidden commands ``versionedfile-list``,
18
``weave-plan-merge``, ``weave-merge-text``.
17
21
* ``Repository.get_inventory_sha1()`` has been removed. (Jelmer Vernooij)
23
* All test servers have been moved out of the bzrlib.transport hierarchy to
24
bzrlib.tests.test_server *except* for MemoryServer, ChrootServer and
25
PathFilteringServer. ``bzrlib`` users may encounter test failures that can
26
be fixed by updating the related imports from ``bzrlib.transport.xxx`` to
27
``bzrlib.tests.test_server``.
33
* If the Apport crash-reporting tool is available, bzr crashes are now
34
stored into the ``/var/crash`` apport spool directory, and the user is
35
invited to report them to the developers from there, either
36
automatically or by running ``apport-bug``. No information is sent
37
without specific permission from the user. (Martin Pool, #515052)
39
* Tree-shape conflicts can be resolved by providing ``--take-this`` and
40
``--take-other`` to the ``bzr resolve`` command. Just marking the conflict
41
as resolved is still accessible via the ``--done`` default action.
47
* Added docstring for ``Tree.iter_changes``
48
(John Arbash Meinel, #304182)
50
* Allow exporting a single file using ``bzr export``.
51
(Michal Junák, #511987)
53
* Avoid infinite recursion when probing for apport.
54
(Vincent Ladeuil, #516934)
56
* Avoid ``malloc(0)`` in ``patiencediff``, which is non-portable.
57
(Martin Pool, #331095)
59
* ``bzr add`` will not add conflict related files unless explicitly required.
60
(Vincent Ladeuil, #322767, #414589)
62
* ``bzr remove-tree`` can now remove multiple working trees.
63
(Jared Hance, Andrew Bennetts, #253137)
65
* Network transfer amounts and rates are now displayed in SI units according
66
to the Ubuntu Units Policy <https://wiki.ubuntu.com/UnitsPolicy>.
67
(Gordon Tyler, #514399)
69
* Support kind markers for socket and fifo filesystem objects. This
70
prevents ``bzr status --short`` from crashing when those files are
71
present. (John Arbash Meinel, #303275)
76
* New ``bzrlib.initialize`` is recommended for programs using bzrlib to
77
run when starting up; it sets up several things that previously needed
78
to be done separately.
79
(Martin Pool, #507710)
81
* Remove unused ``CommandFailed`` exception.
87
* New `bzrlib.tests.test_import_tariff` can make assertions about what
88
Python modules are loaded, to guard against startup time or library
89
dependency regressions.
92
* Stop sending apport crash files to ``.cache`` in the directory from
93
which ``bzr selftest`` was run. (Martin Pool, #422350)
101
This release marks our second long-term-stable series. The Bazaar team
102
has decided that we will continue to make bugfix-only 2.0.x and 2.1.x
103
releases, along with 2.2 development releases.
105
This is a fairly incremental update, focusing on polish and bugfixing.
106
There are no changes for supported disk formats. Key updates include
107
reduced memory consumption for many operations, a new per-file merge
108
hook, ignore patterns can now include '!' to exclude files, globbing
109
support for all commands on Windows, and support for addressing home
110
directories via ``bzr+ssh://host/~/`` syntax.
112
Users are encouraged to upgrade from the 2.0 stable series.
117
* Don't require testtools to use sftp.
118
(Vincent Ladeuil, #516183)
25
120
* Fix "AttributeError in Inter1and2Helper" during fetch.
26
121
(Martin Pool, #513432)
123
* ``bzr update`` performs the two merges in a more logical order and will stop
124
when it encounters conflicts.
125
(Gerard Krol, #113809)
127
* Fix ``log`` to better check ancestors even if merged revisions are involved.
128
(Vincent Ladeuil, #476293)
130
* Give a better error message when doing ``bzr bind`` in an already bound
131
branch. (Neil Martinsen-Burrell, #513063)
133
* Ignore ``KeyError`` from ``remove_index`` during ``_abort_write_group``
134
in a pack repository, which can happen harmlessly if the abort occurs during
135
finishing the write group. Also use ``bzrlib.cleanup`` so that any
136
other errors that occur while aborting the individual packs won't be
137
hidden by secondary failures when removing the corresponding indices.
138
(Andrew Bennetts, #423015)
140
* Set the mtime of files exported to a directory by ``bzr export`` all to
141
the same value to avoid confusing ``make`` and other date-based build
142
systems. (Robert Collins, #515631)
147
* Fetching into experimental formats will now print a warning. (Jelmer
45
161
* ``Repository.serialise_inventory`` has been renamed to
46
162
``Repository._serialise_inventory`` to indicate it is private.
164
* Using the ``bzrlib.chk_map`` module from within multiple threads at the
165
same time was broken due to race conditions with a module level page
166
cache. This shows up as a KeyError in the ``bzrlib.lru_cache`` code with
167
``bzrlib.chk_map`` in the backtrace, and can be triggered without using
168
the same high level objects such as ``bzrlib.repository.Repository``
169
from different threads. chk_map now uses a thread local cache which may
170
increase memory pressure on processes using threads.
171
(Robert Collins, John Arbash Meinel, #514090)
173
* The new ``merge_file_content`` should now be ok with tests to avoid
175
(Vincent Ladeuil, #515597)
180
* Use ``bzrlib.cleanup`` rather than less robust ``try``/``finally``
181
blocks in several places in ``bzrlib.merge``. This avoids masking prior
182
errors when errors like ``ImmortalPendingDeletion`` occur during cleanup
184
(Andrew Bennetts, #517275)
189
* The ``remove_index`` method of
190
``bzrlib.repofmt.pack_repo.AggregateIndex`` no longer takes a ``pack``
191
argument. This argument was always ignored.
192
(Andrew Bennetts, #423015)
added
removed
NEWS
