11
:2.5b1: 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 ``from_unicode`` parameter can be specified when registering a config
24
option. This implements boolean and integer config options when the
25
provided ``bool_from_store`` and ``int_from_store`` are used.
28
* A ``from_unicode`` parameter can be specified when registering a config
29
option. This implements boolean, integer and list config options when the
30
provided ``bool_from_store``, ``int_from_store`` and ``list_from_store``
31
are used for this parameter. (Vincent Ladeuil)
33
* Accessing a packaging branch on Launchpad (eg, ``lp:ubuntu/bzr``) now
34
checks to see if the most recent published source package version for
35
that project is present in the branch tags. This should help developers
36
trust whether the packaging branch is up-to-date and can be used for new
37
changes. The level of verbosity is controlled by the config item
38
``launchpad.packaging_verbosity``. It can be set to one of
45
only display if the branch is out-of-date
48
also display single-line up-to-date and missing,
52
(default) display multi-line content for all states
55
(John Arbash Meinel, #609187, #812928)
57
* Add a config option gpg_signing_key for setting which GPG key should
58
be used to sign commits. Also default to using the gpg user identity
59
which matches user_email() as set by whoami. (Jonathan Riddell,
62
* An ``invalid`` parameter can be specified when registering a config option
63
to decide what should be done when invalid values are
64
encountered. 'warning' and 'eeror' will respectively emit a warning and
65
ignore the value or errors out. (Vincent Ladeuil)
67
* bzr log -m now matches message, author, committer and bugs instead
68
of just matching the message. --message keeps its original meaning,
69
while --match-message, --match-author, --match-committer and
70
--match-bugs match each of those fields.
72
* ``bzr help configuration/<option>`` display the help for ``option`` for
73
all registered configuration options. (Vincent Ladeuil, #747050)
75
* Relative local paths can now be specified in URL syntax by using the
76
"file:" prefix. (Jelmer Vernooij)
81
.. Improvements to existing commands, especially improved performance
82
or memory usage, or better results.
87
.. Fixes for situations where bzr would previously crash or give incorrect
88
or undesirable results.
90
* A call to CHKInventory's filter-method will not result in a
91
DuplicateFileId error, if you move a subfolder and change a file in
93
(Bastian Bowe, #809901)
95
* Decode ``BZR_HOME`` with fs encoding on posix platforms to avoid unicode
96
errors. (Vincent Ladeuil, #822571)
98
* Fix i18n use when no environment variables are set. (Jelmer Vernooij, #810701)
100
* TreeTransformBase.fixup_new_roots no longer forces trees to have a root, so
101
operations that use it, like merge, can now create trees without a root.
107
.. Improved or updated documentation.
109
* Release instructions refreshed. (Vincent Ladeuil)
114
.. Changes that may require updates in plugins or other code that uses
117
* New class ``URL`` in ``bzrlib.utils`` for managing parsed URLs.
120
* New methods ``get_transport_from_path`` and ``get_transport_from_url``
121
have been added that only support opening from a path or a URL,
122
unlike ``get_transport``. (Jelmer Vernooij)
124
* New method ``Tree.get_file_verifier`` which allows tree implementations
125
to return non-sha1 checksums to verify files.
126
(Jelmer Vernooij, #720831)
128
* New method ``InterTree.file_content_matches`` which checks that
129
two files in different trees have the same contents.
132
* New registry ``OptionRegistry`` specialized for configuration options.
135
* Remove ``AtomicFile.closed`` which has been deprecated in bzr 0.10.
138
* Remove ``commands._builtin_commands``, ``commands.shlex_split_unicode``,
139
``Command._maybe_expand_globs`` and ``Command.run_direct`` deprecated in
140
2.10 and 2.2.0. (Vincent Ladeuil)
142
* Remove ``diff.get_trees_and_branches_to_diff`` deprecated in 2.2.0.
144
* Remove ``log.calculate_view_revisions``, ``log._filter_revision_range``,
145
``log.get_view_revisions`` which have been deprecated in bzr 2.1.0. Also
146
remove ``log.show_one_log`` which was never properly deprecated but wasn't
147
used and is easy to inline if needed. (Vincent Ladeuil)
149
* Remove ``trace.info``, ``trace.error`` and ``trace.show_log_error``
150
deprecated in 2.1.0. (Vincent Ladeuil)
152
* Remove ``TransportListRegistry.set_default_transport``, as the concept of
153
a default transport is currently unused. (Jelmer Vernooij)
155
* Remove ``UIFactory.warn_cross_format_fetch`` and
156
``UIFactory.warn_experimental_format_fetch`` in favor of
157
``UIFactory.show_user_warning``. (Jelmer Vernooij)
159
* There is a new class `ContentFilterTree` that provides a facade for
160
content filtering. The `filtered` parameter to `export` is deprecated
161
in favor of passing a filtered tree, and the specific exporter plugins
162
no longer support it.
165
* ``Transport`` now has a ``_parsed_url`` attribute instead of
166
separate ``_user``, ``_password``, ``_port``, ``_scheme``, ``_host``
167
and ``_path`` attributes. Proxies are provided for the moment but
168
may be removed in the future. (Jelmer Vernooij)
174
.. Major internal changes, unlikely to be visible to users or plugin
175
developers, but interesting for bzr developers.
177
* New method ``ControlDir._get_selected_branch`` which returns the
178
colocated branch selected using path segment parameters.
179
(Jelmer Vernooij, #380871)
184
.. Fixes and changes that are only relevant to bzr's test framework and
185
suite. This can include new facilities for writing tests, fixes to
186
spurious test failures and changes to the way things should be tested.
188
* `BranchBuilder.build_snapshot` now supports a "flush" action. This
189
cleanly and reliably allows tests using `BranchBuilder` to construct
190
branches that e.g. rename files out of a directory and unversion that
191
directory in the same revision. Previously some changes were impossible
192
due to the order that `build_snapshot` performs its actions.
195
* Don't require ``os.fdatasync`` to be defined on all supported OSes
196
(BSD-based OSes don't define it). (Vincent Ladeuil, #822649)
198
* Fix compatibility with testtools 0.9.12. (Jelmer Vernooij, #815423)
200
* ``LockDir`` can now be run when the local hostname is ``localhost``.
201
(Jelmer Vernooij, #825994)
203
* ``ModuleAvailableFeature`` won't try to import already imported modules,
204
allowing it to be used for modules with side-effects.
205
(Vincent Ladeuil, #712474)
207
* `TestCaseWithMemoryTransport` is faster now: `_check_safety_net` now
208
just compares the bytes in the dirstate file to its pristine state,
209
rather than opening the WorkingTree and calling ``last_revision()``.
210
This reduces the overall test suite time by about 10% on my laptop.
213
* Update `TestCase.knownFailure` to the testtools way of handling expected
214
failures to resolve Python 2.7 incompatibility. (Martin [gz], #607400)
217
vim: tw=74 ft=rst ff=unix
added
removed
doc/en/release-notes/bzr-2.5.txt
