21
21
.. New commands, options, etc that users may wish to try out.
23
* The ``log_format`` configuration can be used with ``-Olog_format=line`` to
24
change the format ``push`` and ``pull`` use to display the
25
revisions. I.e.: ``bzr pull -v -Olog_format=short`` will use the ``short``
26
format instead of the default ``long`` one. (Vincent Ladeuil, #861472)
31
.. Improvements to existing commands, especially improved performance
32
or memory usage, or better results.
34
* ``bzr version-info`` now takes a ``--revision`` argument.
35
(Jelmer Vernooij, #238705)
37
* ``bzr revno`` now takes a ``--revision`` argument.
38
(Jelmer Vernooij, #870649)
43
.. Fixes for situations where bzr would previously crash or give incorrect
44
or undesirable results.
46
* ``bzr mkdir --quiet`` now does not print a line for every created
47
directory. (Martin von Gagern, #869915)
52
.. Improved or updated documentation.
57
.. Changes that may require updates in plugins or other code that uses
60
* ``Branch.revision_history`` is now deprecated. (Jelmer Vernooij, #799519)
65
.. Major internal changes, unlikely to be visible to users or plugin
66
developers, but interesting for bzr developers.
68
* ``ControlDirFormat`` now has a new method ``supports_transport``
69
which format implementations can use whether or not they can access
70
a control dir over a particular transport. (Jelmer Vernooij)
75
.. Fixes and changes that are only relevant to bzr's test framework and
76
suite. This can include new facilities for writing tests, fixes to
77
spurious test failures and changes to the way things should be tested.
79
* Ensure TestCase instances are deallocated immediately after running where
80
possible. This greatly reduces the peak resource needs of a full test suite
81
run. The new ``-Euncollected_cases`` selftest flag will add failures if any
82
case which persists pasts its expected lifetime. (Martin Packman, #613247)
88
This is the second beta of the 2.5 series, leading to a 2.5.0 release in
89
February 2012. Beta releases are suitable for everyday use but may cause some
90
incompatibilities with plugins.
92
This release includes more filtering options for ``bzr log``, idle
93
connections handling for ``bzr serve``, a ``development-colo`` experimental
94
format to flesh out the colocated branches UI, better support for foreign
95
formats, enhancements to the config framework and more.
97
This release includes all bug fixed in previous series known at the time of
102
External Compatibility Breaks
103
*****************************
110
* A new ``-O`` standard option (common to all commands) have been added. It
111
provides a value for a config option in the ``-Oname=value`` form that
112
takes precedence over all definitions found in config files. It can be
113
used multiple times to override different options.
114
(Vincent Ladeuil, #491196)
116
* ``bzr log`` now has an option called ``--omit-merges`` to omit
117
those commits that merged branches, i.e. those having more than one
119
In order to avoid confusion, the previous command line option
120
``--include-merges`` has been renamed to ``--include-merged``.
121
The old name of the command line option will still be accepted.
122
The name change also affects ``bzr missing``.
125
23
* ``bzr serve`` will now disconnect clients if they have not issued an RPC
126
24
request after 5minutes. On POSIX platforms, this will also happen for
127
25
``bzr serve --inet``. This can be overridden with the configuration
131
29
finish the current request, and then close the connection.
132
30
(John Arbash Meinel, #824797, #795025)
134
* The new experimental format ``development-colo`` supports colocated
135
branches. This format will eventually be merged back into the ``2a``
136
format when it has stabilized and there is adequate UI support for
138
(Jelmer Vernooij, #831481)
36
.. Improvements to existing commands, especially improved performance
37
or memory usage, or better results.
143
39
* Fixed a bug where ``bzr tags -r x..y`` loaded the branch history once for
144
40
every revision in the range; it's now much faster. (Vincent Ladeuil, #857335)
146
* ``bzr info -v`` can now be run against branches that don't support
147
``last_revision_info``, in which case the branch information will simply
148
not be displayed. (Jelmer Vernooij)
153
* ``bzr shelve`` can now be used in emacs shells as the input handling is
154
turned into a line-based one when ``INSIDE_EMACS`` is set (which is the
155
case for all recent emacs versions). (Vincent Ladeuil, #856261)
157
* ``bzr tags`` can now be used against remote repositories that do
158
not provide access to the revision graph. (Jelmer Vernooij, #858942)
160
* ``bzr update PATH`` will stop if you seem to be asking it to update
161
anything less than a whole tree, because that's not supported by ``bzr``'s
162
concept that the whole tree has a single basis revision. Previously, it
163
would go ahead and update the whole tree, which was surprising.
164
(Martin Pool, #557886)
166
* Don't crash if ``bzrlib.initialize()`` has not been called while accessing
167
configs. (Vincent Ladeuil, #863401)
45
.. Fixes for situations where bzr would previously crash or give incorrect
46
or undesirable results.
169
48
* Redirects between http and https no longer discard path information
170
49
in some cases. (Jelmer Vernooij, #853765)
175
54
* ``WorkingTree.get_file_mtime`` now raises NoSuchId if a file id is
176
55
specified that is unknown. (Jelmer Vernooij, #847435)
60
.. Improved or updated documentation.
182
* ``Branch.get_revision_delta`` has been deprecated. Use
183
``Repository.get_revision_delta`` instead. (Jelmer Vernooij, #859712)
185
* Plugins that implement custom protocols for ``bzr serve`` should now
186
also take an argument ``timeout``. This is used by the the bzr protocol
187
to close a connection if a client has been idle for more than X seconds.
188
(Default 5minutes). (John Arbash Meinel)
190
* ``Repository.fileids_altered_by_revision_ids`` has been moved to
191
``VersionedFileRepository`` and is no longer part of the standard
192
``Repository`` interface. (Jelmer Vernooij)
194
* The argument ``include_merges`` to ``missing.find_unmerged`` has
195
been renamed to ``include_merged``. The old name is still supported
196
for now but will cause a deprecation warning. (Martin von Gagern)
65
.. Changes that may require updates in plugins or other code that uses
198
68
* The new method ``ControlDirFormat.is_initializable()`` returns a boolean
199
69
indicating whether or not it is possible to use any of the
224
98
:2.5b1: 2011-09-15
226
100
This is the first beta of the 2.5 series, leading up to a 2.5.0
227
release in February 2012.
229
This release includes better support for gpg signing, better support for
230
i18n (mostly command help and error messages), more options to filter ``bzr
231
log`` output, more support for colocated branches ("location,branch=XXX"
232
syntax), better feedback on updated tags for various commands, faster
233
branching into an empty repository, enhancements to the config framework and
236
Beta releases are suitable for everyday use but may cause some
237
incompatibilities with plugins. Some plugins may need small updates to work
101
release in February 2012. Beta releases are suitable for everyday use
102
but may cause some incompatibilities with plugins. Some plugins may need
103
small updates to work with 2.5b1.
240
105
External Compatibility Breaks
241
106
*****************************
297
162
while ``--match-message, --match-author, --match-committer`` and
298
163
``--match-bugs`` match each of those fields. (Jacek Sieka)
165
* ``bzr log`` now has an option called ``--omit-merges`` to ommit
166
those commits that merged branches, i.e. those having more than one
168
In order to avoid confusion, the previous command line option
169
``--include-merges`` has been renamed to ``--include-merged``.
170
The old name of the command line option will still be accepted.
171
The name change also affects ``bzr missing``.
300
174
* ``config.Option`` can now declare ``default_from_env``, a list of
301
175
environment variables to get a default value from. (Vincent Ladeuil)