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
* ``Repository.get_inventory_sha1()`` has been removed. (Jelmer Vernooij)
17
* Deleted very old hidden commands ``versionedfile-list``,
18
``weave-plan-merge``, ``weave-merge-text``.
21
* ``Repository.get_inventory_sha1()`` and ``Repository.get_revision_xml()``
22
have been removed. (Jelmer Vernooij)
24
* ``Repository.get_revision_inventory()`` has been removed in favor of
25
``Repository.get_inventory()``. (Jelmer Vernooij)
27
* All test servers have been moved out of the bzrlib.transport hierarchy to
28
bzrlib.tests.test_server *except* for MemoryServer, ChrootServer and
29
PathFilteringServer. ``bzrlib`` users may encounter test failures that can
30
be fixed by updating the related imports from ``bzrlib.transport.xxx`` to
31
``bzrlib.tests.test_server``.
25
40
automatically or by running ``apport-bug``. No information is sent
26
41
without specific permission from the user. (Martin Pool, #515052)
43
* Parsing of command lines, for example in ``diff --using``, no longer
44
treats backslash as an escape character on Windows. (Gordon Tyler,
28
47
* Tree-shape conflicts can be resolved by providing ``--take-this`` and
29
48
``--take-other`` to the ``bzr resolve`` command. Just marking the conflict
30
49
as resolved is still accessible via the ``--done`` default action.
52
* Merges can be proposed on Launchpad with the new lp-propose-merge command.
53
(Aaron Bentley, Jonathan Lange)
58
* Added docstring for ``Tree.iter_changes``
59
(John Arbash Meinel, #304182)
61
* Allow exporting a single file using ``bzr export``.
62
(Michal Junák, #511987)
36
64
* Avoid infinite recursion when probing for apport.
37
65
(Vincent Ladeuil, #516934)
67
* Avoid ``malloc(0)`` in ``patiencediff``, which is non-portable.
68
(Martin Pool, #331095)
70
* ``bzr add`` will not add conflict related files unless explicitly required.
71
(Vincent Ladeuil, #322767, #414589)
73
* ``bzr remove-tree`` can now remove multiple working trees.
74
(Jared Hance, Andrew Bennetts, #253137)
76
* ``bzr upgrade`` now names backup directory as ``backup.bzr.~N~`` instead
77
of ``backup.bzr``. This directory is ignored by bzr commands such as
79
(Parth Malwankar, #335033, #300001)
81
* Network transfer amounts and rates are now displayed in SI units according
82
to the Ubuntu Units Policy <https://wiki.ubuntu.com/UnitsPolicy>.
83
(Gordon Tyler, #514399)
85
* Support kind markers for socket and fifo filesystem objects. This
86
prevents ``bzr status --short`` from crashing when those files are
87
present. (John Arbash Meinel, #303275)
39
89
* Tolerate patches with leading noise in ``bzr-handle-patch``.
40
90
(Toshio Kuratomi, Martin Pool, #502076)
95
* New ``bzrlib.initialize`` is recommended for programs using bzrlib to
96
run when starting up; it sets up several things that previously needed
97
to be done separately.
98
(Martin Pool, #507710)
100
* Remove unused ``CommandFailed`` exception.
106
* ``bzrlib.commands.run_bzr`` is more extensible: callers can supply the
107
functions to load or disable plugins if they wish to use a different
108
plugin mechanism; the --help, --version and no-command name code paths
109
now use the generic pluggable command lookup infrastructure.
115
* New `bzrlib.tests.test_import_tariff` can make assertions about what
116
Python modules are loaded, to guard against startup time or library
117
dependency regressions.
45
120
* Stop sending apport crash files to ``.cache`` in the directory from
46
121
which ``bzr selftest`` was run. (Martin Pool, #422350)
48
bzr 2.1.0 (not released yet)
49
############################
56
* Network transfer amounts and rates are now displayed in SI units according
57
to the Ubuntu Units Policy, https://wiki.ubuntu.com/UnitsPolicy.
58
(Gordon Tyler, #514399)
126
:2.1.1: not released yet
131
* Register SIGWINCH handler only when creating a ``TextUIFactory``; avoids
132
problems importing bzrlib from a non-main thread.
133
(Elliot Murphy, #521989)
135
* Standardize the error handling when creating a new ``StaticTuple``
136
(problems will raise TypeError). (Matt Nordhoff, #457979)
138
* Merge correctly when this_tree is not a WorkingTree. (Aaron Bentley)
143
* Added What's New in Bazaar 2.1 document. (Ian Clatworthy)
148
:Codename: Strasbourg
151
This release marks our second long-term-stable series. The Bazaar team
152
has decided that we will continue to make bugfix-only 2.0.x and 2.1.x
153
releases, along with 2.2 development releases.
155
This is a fairly incremental update, focusing on polish and bugfixing.
156
There are no changes for supported disk formats. Key updates include
157
reduced memory consumption for many operations, a new per-file merge
158
hook, ignore patterns can now include '!' to exclude files, globbing
159
support for all commands on Windows, and support for addressing home
160
directories via ``bzr+ssh://host/~/`` syntax.
162
Users are encouraged to upgrade from the 2.0 stable series.
167
* Don't require testtools to use sftp.
168
(Vincent Ladeuil, #516183)
60
170
* Fix "AttributeError in Inter1and2Helper" during fetch.
61
171
(Martin Pool, #513432)
173
* ``bzr update`` performs the two merges in a more logical order and will stop
174
when it encounters conflicts.
175
(Gerard Krol, #113809)
63
177
* Fix ``log`` to better check ancestors even if merged revisions are involved.
64
178
(Vincent Ladeuil, #476293)
66
180
* Give a better error message when doing ``bzr bind`` in an already bound
67
181
branch. (Neil Martinsen-Burrell, #513063)
183
* Ignore ``KeyError`` from ``remove_index`` during ``_abort_write_group``
184
in a pack repository, which can happen harmlessly if the abort occurs during
185
finishing the write group. Also use ``bzrlib.cleanup`` so that any
186
other errors that occur while aborting the individual packs won't be
187
hidden by secondary failures when removing the corresponding indices.
188
(Andrew Bennetts, #423015)
69
190
* Set the mtime of files exported to a directory by ``bzr export`` all to
70
191
the same value to avoid confusing ``make`` and other date-based build
71
192
systems. (Robert Collins, #515631)
added
removed
NEWS
