5
5
.. contents:: List of Releases
8
bzr 2.1.0rc1 (not released yet)
9
###############################
8
bzr 2.2.0b1 (not released yet)
9
##############################
12
:2.1.0rc1: 2009-01-06 (expected)
14
14
Compatibility Breaks
15
15
********************
20
* The ``suppress_warnings`` configuration option has been introduced and
21
accept the ``format_deprecation`` value to disable the corresponding
22
warning for repositories. It can be set to in either ``bazaar.conf``,
23
``locations.conf`` or ``branch.conf``.
17
* ``Repository.get_inventory_sha1()`` has been removed. (Jelmer Vernooij)
25
* Fix "AttributeError in Inter1and2Helper" during fetch.
26
(Martin Pool, #513432)
47
:Codename: after the bubbles
50
This is a quick-turn-around to update a small issue with our new per-file
51
merge hook. We expect no major changes from this to the final 2.1.0.
56
* The new ``merge_file_content`` hook point has been altered to provide a
57
better API where state for extensions can be stored rather than the
58
too-simple function based approach. This fixes a performance regression
59
where branch configuration would be parsed per-file during merge. As
60
part of this the included news_merger has been refactored into a base
61
helper class ``bzrlib.merge.ConfigurableFileMerger``.
62
(Robert Collins, John Arbash Meinel, #513822)
68
:Codename: the 'new' stable
71
This is the first stable release candidate for Bazaar's 2.1 series. From
72
this point onwards, the 2.1 series will be considered stable (as the 2.0
73
series) and only bugfixes are expected to be incorporated. The dozen or so
74
bugfixes in the 2.0.4 release are also included in this release (along
75
with more than 15 more bugfixes). Some of the interesting features are
76
support for per-file merge hooks, ``bzr unshelve --preview``, support
77
for using ! in ignore files to exclude files from being ignored, a small
78
memory leak was squashed, and many ``ObjectNotLocked`` errors were fixed.
79
This looks to be a very good start for a new stable series.
85
* Add bug information to log output when available.
86
(Neil Martinsen-Burrell, Guillermo Gonzalez, #251729)
88
* Added ``merge_file_content`` hook point to ``Merger``, allowing plugins
89
to register custom merge logic, e.g. to provide smarter merging for
92
* Bazaar now includes the ``news_merge`` plugin. It is disabled by
93
default, to enable it add a ``news_merge_files`` option to your
94
configuration. Consult ``bzr help news_merge`` for more information.
97
* ``bzr branch`` now takes a ``--bind`` option. This lets you
98
branch and bind all in one command. (Ian Clatworthy)
100
* ``bzr switch`` now takes a ``--revision`` option, to allow switching to
101
a specific revision of a branch. (Daniel Watkins, #183559)
103
* ``bzr unshelve --preview`` can now be used to show how a patch on the
104
shelf would be applied to the working tree.
105
(Guilherme Salgado, #308122)
107
* ``bzr update`` now takes a ``--revision`` argument. This lets you
108
change the revision of the working tree to any revision in the
109
ancestry of the current or master branch. (Matthieu Moy, Mark Hammond,
112
* ``-Dbytes`` can now be used to display the total number of bytes
113
transferred for the current command. This information is always logged
114
to ``.bzr.log`` for later inspection. (John Arbash Meinel)
116
* New ignore patterns. Patterns prefixed with '!' are exceptions to
117
ignore patterns and take precedence over regular ignores. Such
118
exceptions are used to specify files that should be versioned which
119
would otherwise be ignored. Patterns prefixed with '!!' act as regular
120
ignore patterns, but have highest precedence, even over the '!'
121
exception patterns. (John Whitley, #428031)
123
* The ``supress_warnings`` configuration option has been introduced to disable
124
various warnings (it currently only supports the ``format_deprecation``
125
warning). The new option can be set in any of the following locations:
126
``bazaar.conf``, ``locations.conf`` and/or ``branch.conf``.
24
127
(Ted Gould, Matthew Fuller, Vincent Ladeuil)
132
* Always show a message if an OS error occurs while trying to run a
133
user-specified commit message editor.
134
(Martin Pool, #504842)
136
* ``bzr diff`` will now use the epoch when it is unable to determine
137
the timestamp of a file, if the revision it was introduced in is a
138
ghost. (Jelmer Vernooij, #295611)
29
140
* ``bzr switch -b`` can now create branches that are located using directory
30
141
services such as ``lp:``, even when the branch name doesn't contain a
31
142
'/'. (Neil Martinsen-Burrell, #495263)
33
144
* ``bzr unshelve`` has improved messages about what it is doing.
34
145
(Neil Martinsen-Burrell, #496917)
147
* Concurrent autopacking is more resilient to already-renamed pack files.
148
If we find that a file we are about to obsolete is already obsoleted, we
149
do not try to rename it, and we leave the file in ``obsolete_packs``.
150
The code is also fault tolerant if a file goes missing, assuming that
151
another process already removed the file.
152
(John Arbash Meinel, Gareth White, #507557)
154
* Fix "Too many concurrent requests" in reconcile when network connection
155
fails. (Andrew Bennetts, #503878)
157
* Fixed a side effect mutation of ``RemoteBzrDirFormat._network_name``
158
that caused some tests to fail when run in a non-default order.
159
Probably no user impact. (Martin Pool, #504102)
161
* Fixed ``ObjectNotLocked`` error in ``bzr cat -rbranch:../foo FILE``.
162
(Andrew Bennetts, #506274)
164
* FTP transports support Unicode paths by encoding/decoding them as utf8.
165
(Vincent Ladeuil, #472161)
36
167
* Listen to the SIGWINCH signal to update the terminal width.
37
168
(Vincent Ladeuil, #316357)
170
* Progress bars are now hidden when ``--quiet`` is given.
171
(Martin Pool, #320035)
173
* ``SilentUIFactory`` now supports ``make_output_stream`` and discards
174
whatever is written to it. This un-breaks some plugin tests that
175
depended on this behaviour.
176
(Martin Pool, #499757)
178
* When operations update the working tree, all affected files should end
179
up with the same mtime. (eg. when versioning a generated file, if you
180
update the source and the generated file together, the generated file
181
should appear up-to-date.)
182
(John Arbash Meinel, Martin <gzlist>, #488724)
187
* Added ``add_cleanup`` and ``cleanup_now`` to ``bzrlib.command.Command``.
188
All the builtin commands now use ``add_cleanup`` rather than
189
``try``/``finally`` blocks where applicable as it is simpler and more
190
robust. (Andrew Bennetts)
192
* All except a small number of storage formats are now hidden, making
193
the help for numerous commands far more digestible. (Ian Clatworthy)
195
* Attempts to open a shared repository as a branch (e.g. ``bzr branch
196
path/to/repo``) will now include "location is a repository" as a hint in
197
the error message. (Brian de Alwis, Andrew Bennetts, #440952)
199
* Push will now inform the user when they are trying to push to a foreign
200
VCS for which roundtripping is not supported, and will suggest them to
201
use dpush. (Jelmer Vernooij)
203
* The version of bzr being run is now written to the log file.
42
206
* Transport network activity indicator is shown more of the time when
43
207
Bazaar is doing network IO.
213
* Add documentation on creating merges with more than one parent.
214
(Neil Martinsen-Burrell, #481526)
216
* Better explain the --uncommitted option of merge.
217
(Neil Martinsen-Burrell, #505088)
219
* Improve discussion of pending merges in the documentation for
220
``revert``. (Neil Martinsen-Burrell, #505093)
222
* Improved help for ``bzr send``.
223
(Martin Pool, Bojan Nikolic)
225
* There is a System Administrator's Guide in ``doc/en/admin-guide``,
226
including discussions of installation, relevant plugins, security and
227
backup. (Neil Martinsen-Burrell)
229
* The ``conflicts`` help topic has been renamed to ``conflict-types``.
232
* The User Reference is now presented as a series of topics.
233
Many of the included topics have link and format tweaks applied.
239
* Added ``cachedproperty`` decorator to ``bzrlib.decorators``.
52
242
* Many test features were renamed from ``FooFeature`` to ``foo_feature``
53
243
to be consistent with instances being lower case and classes being
54
244
CamelCase. For the features that were more likely to be used, we added a
55
245
deprecation thunk, but not all. (John Arbash Meinel)
247
* Merger classes (such as ``Merge3Merger``) now expect a ``this_branch``
248
parameter in their constructors, and provide ``this_branch`` as an
249
attribute. (Andrew Bennetts)
251
* The Branch hooks pre_change_branch_tip no longer masks exceptions raised
252
by plugins - the original exceptions are now preserved. (Robert Collins)
254
* The Transport ``Server.tearDown`` method is now renamed to
255
``stop_server`` and ``setUp`` to ``start_server`` for consistency with
256
our normal naming pattern, and to avoid confusion with Python's
257
``TestCase.tearDown``. (Martin Pool)
259
* ``WorkingTree.update`` implementations must now accept a ``revision``
265
* Added ``BzrDir.open_branchV3`` smart server request, which can receive
266
a string of details (such as "location is a repository") as part of a
267
``nobranch`` response. (Andrew Bennetts, #440952)
269
* New helper osutils.UnicodeOrBytesToBytesWriter which encodes unicode
270
objects but passes str objects straight through. This is used for
271
selftest but may be useful for diff and other operations that generate
272
mixed output. (Robert Collins)
274
* New exception ``NoRoundtrippingSupport``, for use by foreign branch
275
plugins. (Jelmer Vernooij)
63
bzr 2.0.4 (not released yet)
64
############################
280
* ``bzrlib.tests.permute_for_extension`` is a helper that simplifies
281
running all tests in the current module, once against a pure python
282
implementation, and once against an extension (pyrex/C) implementation.
283
It can be used to dramatically simplify the implementation of
284
``load_tests``. (John Arbash Meinel)
286
* ``bzrlib.tests.TestCase`` now subclasses ``testtools.testcase.TestCase``.
287
This permits features in testtools such as getUniqueInteger and
288
getUniqueString to be used. Because of this, testtools version 0.9.2 or
289
newer is now a dependency to run bzr selftest. Running with versions of
290
testtools less than 0.9.2 will cause bzr to error while loading the test
291
suite. (Robert Collins)
293
* Shell-like tests now support the command "mv" for moving files. The
294
syntax for ``mv file1 file2``, ``mv dir1 dir2`` and ``mv file dir`` is
295
supported. (Neil Martinsen-Burrell)
297
* The test progress bar no longer distinguishes tests that 'errored' from
298
tests that 'failed' - they're all just failures.
305
:Codename: smooth sailing
308
The fourth bugfix-only release in the 2.0 series contains more than a
309
dozen bugfixes relative to 2.0.3. The primary focus is on handling
310
interruptions and concurrent operations more cleanly, there is also a fair
311
improvement to ``bzr export`` when exporting a remote branch.
317
* ``bzr annotate`` on another branch with ``-r branch:...`` no longer
318
fails with an ``ObjectNotLocked`` error. (Andrew Bennetts, #496590)
320
* ``bzr export dir`` now requests all file content as a record stream,
321
rather than requsting the file content one file-at-a-time. This can make
322
exporting over the network significantly faster (54min => 9min in one
323
case). (John Arbash Meinel, #343218)
325
* ``bzr serve`` no longer slowly leaks memory. The compiled
326
``bzrlib.bencode.Encoder()`` class was using ``__del__`` to cleanup and
327
free resources, and it should have been using ``__dealloc__``.
328
This will likely have an impact on any other process that is serving for
329
an extended period of time. (John Arbash Meinel, #494406)
331
* Check for SIGINT (Ctrl-C) and other signals immediately if ``readdir``
332
returns ``EINTR`` by calling ``PyErr_CheckSignals``. This affected the
333
optional ``_readdir_pyx`` extension. (Andrew Bennetts, #495023)
335
* Concurrent autopacks will no longer lose a newly created pack file.
336
There was a race condition, where if the reload happened at the right
337
time, the second packer would forget the name of the newly added pack
338
file. (John Arbash Meinel, Gareth White, #507566)
340
* Give a clearer message if the lockdir disappears after being apparently
341
successfully taken. (Martin Pool, #498378)
343
* Give a warning when fetching between repositories (local or remote) with
344
sufficiently different formats that the content will need to be
345
serialized (ie ``InterDifferingSerializer`` or ``inventory-deltas``), so
346
the user has a clue that upgrading could make it faster.
347
(Martin Pool, #456077)
349
* If we fail to open ``~/.bzr.log`` write a clear message to stderr rather
350
than using ``warning()``. The log file is opened before logging is set
351
up, and it leads to very confusing: 'no handlers for "bzr"' messages for
352
users, rather than something nicer.
353
(John Arbash Meinel, Barry Warsaw, #503886)
355
* Refuse to build with any Pyrex 0.9.4 release, as they have known bugs.
356
(Martin Pool, John Arbash Meinel, #449372)
358
* ``setup.py bdist_rpm`` now properly finds extra files needed for the
359
build. (there is still the distutils bug
360
http://bugs.python.org/issue644744) (Joe Julian, #175839)
362
* The 2a format wasn't properly restarting autopacks when something
363
changed underneath it (like another autopack). Now concurrent
364
autopackers will properly succeed. (John Arbash Meinel, #495000)
366
* ``TreeTransform`` can now handle when a delta says that the file id for
367
the tree root changes. Rather than trying to rename your working
368
directory, or failing early saying that you can't have multiple
369
tree roots. This also fixes revert, update, and pull when the root id
370
changes. (John Arbash Meinel, #494269, #504390)
372
* ``_update_current_block`` no longer suppresses exceptions, so ^C at just
373
the right time will get propagated, rather than silently failing to move
374
the block pointer. (John Arbash Meinel, Gareth White, #495023)
379
* We have a new ``test_source`` that ensures all pyrex ``cdef`` functions
380
handle exceptions somehow. (Possibly by setting ``# cannot_raise``
381
rather than an ``except ?:`` clause.) This should help prevent bugs like
382
bug #495023. (John Arbash Meinel)
added
removed
NEWS
