11
:2.5b2: NOT RELEASED YET
13
External Compatibility Breaks
14
*****************************
16
.. These may require users to change the way they use Bazaar.
21
.. New commands, options, etc that users may wish to try out.
23
* A new ``-O`` standard option (common to all commands) have been added. It
24
provides a value for a config option in the ``-Oname=value`` form that
25
takes precedence over all definitions found in config files. It can be
26
used multiple times to override different options.
27
(Vincent Ladeuil, #491196)
29
* ``bzr serve`` will now disconnect clients if they have not issued an RPC
30
request after 5minutes. On POSIX platforms, this will also happen for
31
``bzr serve --inet``. This can be overridden with the configuration
32
variable ``serve.client_timeout`` or in the command line parameter
33
``bzr serve --client-timeout=X``. Further, it is possible to request
34
``bzr serve [--inet]`` to shutdown gracefully by sending SIGHUP. It will
35
finish the current request, and then close the connection.
36
(John Arbash Meinel, #824797, #795025)
42
.. Improvements to existing commands, especially improved performance
43
or memory usage, or better results.
45
* Fixed a bug where ``bzr tags -r x..y`` loaded the branch history once for
46
every revision in the range; it's now much faster. (Vincent Ladeuil, #857335)
48
* ``bzr info -v`` can now be run against branches that don't support
49
``last_revision_info``, in which case the branch information will simply
50
not be displayed. (Jelmer Vernooij)
55
.. Fixes for situations where bzr would previously crash or give incorrect
56
or undesirable results.
58
* ``bzr shelve`` can now be used in emacs shells as the input handling is
59
turned into a line-basde one when ``INSIDE_EMACS`` is set (which is the
60
case for all recent emacs versions). (Vincent Ladeuil, #856261)
62
* ``bzr update PATH`` will stop if you seem to be asking it to update
63
anything less than a whole tree, because that's not supported by bzr's
64
concept that the whole tree has a single basis revision. Previously, it
65
would go ahead and update the whole tree, which was surprising.
66
(Martin Pool, #557886)
68
* Redirects between http and https no longer discard path information
69
in some cases. (Jelmer Vernooij, #853765)
71
* The ``--overwrite`` argument to ``bzr push`` and ``bzr pull`` no longer
72
reports all tags as changed. (Jelmer Vernooij, #845396)
74
* ``WorkingTree.get_file_mtime`` now raises NoSuchId if a file id is
75
specified that is unknown. (Jelmer Vernooij, #847435)
80
.. Improved or updated documentation.
85
.. Changes that may require updates in plugins or other code that uses
88
* ``Branch.get_revision_delta`` has been deprecated. Use
89
``Repository.get_revision_delta`` instead. (Jelmer Vernooij, #859712)
91
* ``Repository.fileids_altered_by_revision_ids`` has been moved to
92
``VersionedFileRepository`` and is no longer part of the standard
93
``Repository`` interface. (Jelmer Vernooij)
95
* The new method ``ControlDirFormat.is_initializable()`` returns a boolean
96
indicating whether or not it is possible to use any of the
97
initialization methods of that format to create a new control dir.
103
.. Major internal changes, unlikely to be visible to users or plugin
104
developers, but interesting for bzr developers.
106
* ``Branch`` objects can now use a config stack with the newly introduced
107
``get_config_stack()``. Both ``get_config`` and ``get_config_stack`` can
108
be used for the same branch but it's recommended to stick to one for a
114
* Test scripts can now use ``bzr shelve`` and provide their input as
115
complete lines. (Vincent Ladeuil, #856261)
117
.. Fixes and changes that are only relevant to bzr's test framework and
118
suite. This can include new facilities for writing tests, fixes to
119
spurious test failures and changes to the way things should be tested.
121
* Really corrupt the pack file without depending on a special length or value.
122
(Vincent Ladeuil, #807032)
130
This is the first beta of the 2.5 series, leading up to a 2.5.0
131
release in February 2012. Beta releases are suitable for everyday use
132
but may cause some incompatibilities with plugins. Some plugins may need
133
small updates to work with 2.5b1.
135
External Compatibility Breaks
136
*****************************
143
* A ``from_unicode`` parameter can be specified when registering a config
144
option. This implements boolean, integer and list config options when the
145
provided ``bool_from_store``, ``int_from_store`` and ``list_from_store``
146
are used for this parameter. (Vincent Ladeuil)
148
* Accessing a packaging branch on Launchpad (eg, ``lp:ubuntu/bzr``) now
149
checks to see if the most recent published source package version for
150
that project is present in the branch tags. This should help developers
151
trust whether the packaging branch is up-to-date and can be used for new
152
changes. The level of verbosity is controlled by the config item
153
``launchpad.packaging_verbosity``. It can be set to one of
160
only display if the branch is out-of-date
163
also display single-line up-to-date and missing,
167
(default) display multi-line content for all states
170
(John Arbash Meinel, #609187, #812928)
172
* Add a config option gpg_signing_key for setting which GPG key should
173
be used to sign commits. Also default to using the gpg user identity
174
which matches user_email() as set by whoami.
175
(Jonathan Riddell, #68501)
177
* An ``invalid`` parameter can be specified when registering a config option
178
to decide what should be done when invalid values are
179
encountered. 'warning' and 'error' will respectively emit a warning and
180
ignore the value or errors out. (Vincent Ladeuil)
182
* bzr add now skips large files in recursive mode. The default "large"
183
size is 20MB, and is configurable via the add.maximum_file_size
184
option. A value of 0 disables skipping. Named items passed to add are
185
never skipped. (Shannon Weyrick, #54624)
187
* ``bzr help configuration/<option>`` display the help for ``option`` for
188
all registered configuration options. (Vincent Ladeuil, #747050)
190
* ``bzr log -m`` now matches message, author, committer and bugs instead
191
of just matching the message. ``--message`` keeps its original meaning,
192
while ``--match-message, --match-author, --match-committer`` and
193
``--match-bugs`` match each of those fields. (Jacek Sieka)
195
* ``bzr log`` now has an option called ``--omit-merges`` to ommit
196
those commits that merged branches, i.e. those having more than one
198
In order to avoid confusion, the previous command line option
199
``--include-merges`` has been renamed to ``--include-merged``.
200
The old name of the command line option will still be accepted.
201
The name change also affects ``bzr missing``.
204
* ``config.Option`` can now declare ``default_from_env``, a list of
205
environment variables to get a default value from. (Vincent Ladeuil)
207
* ``config.NameMatcher`` can be used to implement config stores and stacks
208
that need to provide specific option values for arbitrary unique IDs (svn
209
repository UUIDs, etc). (Vincent Ladeuil, #843638)
211
* New builtin ``bzr branches`` command, which lists all colocated branches
212
in a directory. (Jelmer Vernooij, #826820)
214
* Relative local paths can now be specified in URL syntax by using the
215
"file:" prefix. (Jelmer Vernooij)
217
* Report commits signed with expired keys in ``verify-signatures``.
218
(Jonathan Riddell, #804254)
220
* Translations are now enabled for command help, errors and globally
221
for any message using gettext given on output. (Jonathan Riddell,
227
* ``bzr add`` will now warn about nested subtrees that are skipped.
228
(Jelmer Vernooij, #187342)
230
* ``bzr commit -m ''`` can now be used to force an empty commit message.
231
Entering an empty commit message in the message editor still triggers
232
an error. (Jelmer Vernooij)
234
* ``bzr pull`` will now mention how many tags it has updated.
235
(Jelmer Vernooij, #164450)
237
* ``bzr tag`` no longer errors if a tag already exists but refers to the
238
same revision, and will mention when a tag has been updated
239
rather than created. (Jelmer Vernooij, #381203)
241
* ``bzr uncommit`` will now remove tags that refer to removed revisions.
242
The ``--keep-tags`` option can be used to prevent this behaviour.
243
(Jelmer Vernooij, #605814)
245
* Do not run i18n initialisation twice. (Jonathan Riddell)
247
* Install translation .mo files. (Jonathan Riddell)
249
* Locations printed by ``bzr upgrade`` are now formatted before display.
252
* ``Repository.get_parent_map`` now estimates the size of the returned
253
content more accurately. This means that we get closer to the desired
254
64kB/request. For repositories converted from svn, this can be an
255
improvement of approx 5:1 in round trips to discover the whole history.
258
* Support a ``bugtracker`` option which is used by ``bzr commit --fixes``
259
if no bug tracker was specified on the command line.
260
(Jelmer Vernooij, #334860)
262
* Use gettext.NullTranslations in i18n to allow use of i18n even when
263
translations are not turned on. (Jonathan Riddell)
268
* ``bzr commit`` now correctly reports missing files as "removed", not
269
"modified". (Jelmer Vernooij, #553955)
271
* ``bzr reconfigure`` will now allow multiple non-conflicting requests
272
in a single invocation, e.g. ``--branch`` and ``--use-shared``.
273
(Martin von Gagern, #842993)
275
* A call to CHKInventory's filter-method will not result in a
276
DuplicateFileId error, if you move a subfolder and change a file in
278
(Bastian Bowe, #809901)
280
* Branching from a stacked branch no longer does a ``get_parent_map``
281
request for each revisions that is in the stacked-on repository while
282
determining what revisions need to be fetched. This mostly impacts
283
branching initialy into an empty shared repository when the source is
284
not the development focus. (John Arbash Meinel, #388269)
286
* Decode ``BZR_HOME`` with fs encoding on posix platforms to avoid unicode
287
errors. (Vincent Ladeuil, #822571)
289
* Fix fallout from URL handling changes in 2.5 that caused an IndexError to be
290
raised whenever a transport at the drive root was opened on windows.
291
(Martin [gz], #841322)
293
* Fixed loading of external merge tools from config to properly decode
294
command-lines which contain embedded quotes. (Gordon Tyler, #828803)
296
* Rather than an error being raised, a warning is now printed when the
297
current user does not have permission to read a configuration file.
298
(Jelmer Vernooij, #837324)
300
* The pull command will now always use separate connections for the
301
case where the destination is a heavyweight checkout of some remote
302
branch on the same host as the source branch.
303
(Martin von Gagern, #483661)
305
* TreeTransformBase.fixup_new_roots no longer forces trees to have a root, so
306
operations that use it, like merge, can now create trees without a root.
312
* Release instructions refreshed. (Vincent Ladeuil)
317
* ``BranchFormat.initialize`` now takes a ``append_revisions_only``
318
argument. (Jelmer Vernooij)
320
* ``Branch._get_checkout_format`` now takes a ``lightweight`` argument
321
which indicates if the format should be for a lightweight or a
322
heavyweight checkout. (Jelmer Vernooij)
324
* ``ControlDir.create_branch`` now takes a ``append_revisions_only`` argument.
327
* New class ``URL`` in ``bzrlib.utils`` for managing parsed URLs.
330
* New method ``Config.get_user_option_as_int_from_SI`` added for expanding a
331
value in SI format (i.e. "20MB", "1GB") into its integer equivalent.
334
* New method ``InterTree.file_content_matches`` which checks that
335
two files in different trees have the same contents.
338
* New method ``Tree.get_file_verifier`` which allows tree implementations
339
to return non-sha1 checksums to verify files.
340
(Jelmer Vernooij, #720831)
342
* New methods ``get_transport_from_path`` and ``get_transport_from_url``
343
have been added that only support opening from a path or a URL,
344
unlike ``get_transport``. (Jelmer Vernooij)
346
* New registry ``OptionRegistry`` specialized for configuration options.
349
* Plugins that implement custom protocols for ``bzr serve`` should now
350
also take an argument ``timeout``. This is used by the the bzr protocol
351
to close a connection if a client has been idle for more than X seconds.
352
(Default 5minutes). (John Arbash Meinel)
354
* Remove ``AtomicFile.closed`` which has been deprecated in bzr 0.10.
357
* Remove ``commands._builtin_commands``, ``commands.shlex_split_unicode``,
358
``Command._maybe_expand_globs`` and ``Command.run_direct`` deprecated in
359
2.10 and 2.2.0. (Vincent Ladeuil)
361
* Remove ``diff.get_trees_and_branches_to_diff`` deprecated in 2.2.0.
363
* Remove ``log.calculate_view_revisions``, ``log._filter_revision_range``,
364
``log.get_view_revisions`` which have been deprecated in bzr 2.1.0. Also
365
remove ``log.show_one_log`` which was never properly deprecated but wasn't
366
used and is easy to inline if needed. (Vincent Ladeuil)
368
* Remove ``trace.info``, ``trace.error`` and ``trace.show_log_error``
369
deprecated in 2.1.0. (Vincent Ladeuil)
371
* Remove ``TransportListRegistry.set_default_transport``, as the concept of
372
a default transport is currently unused. (Jelmer Vernooij)
374
* Remove ``UIFactory.warn_cross_format_fetch`` and
375
``UIFactory.warn_experimental_format_fetch`` in favor of
376
``UIFactory.show_user_warning``. (Jelmer Vernooij)
378
* ``Tags`` containers can now declare whether they support versioned
379
tags and whether tags can refer to ghost tags.
382
* ``Tags.merge_to`` now returns a dictionary with the updated tags
383
and a set of conflicts, rather than just conflicts. (Jelmer Vernooij)
385
* There is a new class `ContentFilterTree` that provides a facade for
386
content filtering. The `filtered` parameter to `export` is deprecated
387
in favor of passing a filtered tree, and the specific exporter plugins
388
no longer support it.
391
* ``Transport`` now has a ``_parsed_url`` attribute instead of
392
separate ``_user``, ``_password``, ``_port``, ``_scheme``, ``_host``
393
and ``_path`` attributes. Proxies are provided for the moment but
394
may be removed in the future. (Jelmer Vernooij)
396
* The argument ``include_merges`` to ``missing.find_unmerged`` has
397
been renamed to ``include_merged``. The old name is still supported
398
for now but will cause a deprecation warning. (Martin von Gagern)
404
* A new debug flag ``hpss_client_no_vfs`` will now cause the HPSS client
405
to raise a ``HpssVfsRequestNotAllowed`` exception when a VFS request
406
is attempted. (Jelmer Vernooij)
408
* New method ``ControlDir._get_selected_branch`` which returns the
409
colocated branch selected using path segment parameters.
410
(Jelmer Vernooij, #380871)
415
* Blackbox tests (including test scripts) can be debugged interactively (see
416
bzrlib.debug.BzrPdb for details). (Vincent Ladeuil)
418
* `BranchBuilder.build_snapshot` now supports a "flush" action. This
419
cleanly and reliably allows tests using `BranchBuilder` to construct
420
branches that e.g. rename files out of a directory and unversion that
421
directory in the same revision. Previously some changes were impossible
422
due to the order that `build_snapshot` performs its actions.
425
* Don't require ``os.fdatasync`` to be defined on all supported OSes
426
(BSD-based OSes don't define it). (Vincent Ladeuil, #822649)
428
* Fix compatibility with testtools 0.9.12. (Jelmer Vernooij, #815423)
430
* ``LockDir`` can now be run when the local hostname is ``localhost``.
431
(Jelmer Vernooij, #825994)
433
* ``ModuleAvailableFeature`` won't try to import already imported modules,
434
allowing it to be used for modules with side-effects.
435
(Vincent Ladeuil, #712474)
437
* Output time stamps while running ``make check`` to get better timings from
438
pqm. (Vincent Ladeuil, #837926)
440
* `TestCaseWithMemoryTransport` is faster now: `_check_safety_net` now
441
just compares the bytes in the dirstate file to its pristine state,
442
rather than opening the WorkingTree and calling ``last_revision()``.
443
This reduces the overall test suite time by about 10% on my laptop.
446
* Update `TestCase.knownFailure` to the testtools way of handling expected
447
failures to resolve Python 2.7 incompatibility. (Martin [gz], #607400)
450
vim: tw=74 ft=rst ff=unix
added
removed
doc/en/release-notes/bzr-2.5.txt
