1
*************************
2
What's New in Bazaar 2.5?
3
*************************
5
Bazaar 2.5 bas been released on the 24th of February 2012 and marks the
6
start of a new long-term-stable series. From here, we will only make bugfix
7
releases on the 2.5 series (2.5.1, etc, and support it until April 2017),
8
while 2.6 will become our new development series.
10
This document accumulates a high level summary of what's changed. See the
11
:doc:`../release-notes/index` for a full list.
13
Users are encouraged to upgrade from the other stable series. This
14
document outlines the improvements in Bazaar 2.5 vs Bazaar 2.4. As well as
15
summarizing improvements made to the core product, it highlights
16
enhancements within the broader Bazaar world of potential interest to
19
Bazaar 2.5.0 is fully compatible both locally and on the network with 2.0,
20
2.1, 2.2, 2.3 and 2.4, and can read and write repositories generated by all
23
Overriding configuration options from the command line
24
******************************************************
26
The ``-O`` parameter available for all bzr commands allows a user to
27
override a configuration option from the command line. For example::
29
bzr pull -v -Olog_format=line
31
will change the way the pulled revisions are displayed (the default log
32
format is ``long``). This a work in progress and only some options are
35
Working on a posix system without a locale
36
******************************************
38
Previously bzr needed a valid locale set to work with branches containing
39
non-ascii filenames. It will now use utf-8 rather than ascii as a fallback
40
encoding for interacting with the filesystem. This makes creating a working
41
tree and commiting to it possible for such branches in most environments.
43
SSL Certificate Verification Support in urllib HTTPS backend
44
************************************************************
46
In previous versions of Bazaar, only one of the two supported HTTPS
47
backends, pycurl, supported verification of SSL certificates. This version
48
also introduces this support for the urllib backend.
50
Along with this support two new options have been introduced to control
51
which CA's are trusted and to what degree server certificates should be
52
verified. See ``bzr help ssl.ca_certs`` and ``bzr help ssl.cert_reqs``
55
Users who have previously used the urllib HTTPS backend with servers
56
with invalid or untrusted certificates can continue to do so by
57
adding the required certificates to the trusted CA certificate file
58
(recommended) or by setting the ``ssl.cert_reqs`` option to ``none``.
63
A large number of new methods have been added to the smart server, making
64
raw file access through the VFS unnecessary in almost all situations, with
65
the major exception of operations involving stacked branches.
67
Commands that have become significantly faster when using a remote branch
68
over ``bzr://``, ``bzr+ssh://`` or ``bzr+http://`` include:
70
* ``bzr checkout --lightweight``
76
Several commands which used to make multiple connections to the server now
77
make only a single one. Connection setup has a fairly high overhead,
78
especially to Launchpad, so this can save several seconds for some
81
To benefit from the improved smart server, both the server and the
82
client need to be running bzr 2.5.
84
Basic colocated branch support
85
******************************
87
The UI now has basic support for colocated branches. In full URLs,
88
a specific colocated branch can be specified using URL path segment
89
parameters. For example a branch named ``stronk`` could be addressed using
90
``http://example.com/path/to/dir,branch=stronk``.
92
The new ``bzr branches`` command can be used to list all present branches
93
in a directory, and indicates what the currently active branch is.
95
Several commands also accept co-located branch names directly, such as
101
All Bazaar formats now allow setting ``feature flags``. These can be used
102
by plugins to extend Bazaar formats and require the presence of particular
103
plugins or versions of Bazaar to open them, without having to introduce
104
completely new formats.
106
See ``doc/developers/feature-flags.txt`` for details.
108
Branch history access
109
*********************
111
Several commands or options that previously required access to the full
112
branch history now only access those parts of the history they actually
113
need. This significantly improves their performance for branches
114
with large histories.
119
A new command ``bzr verify-signatures`` can be used to verify GPG
120
signatures made with ``bzr commit`` or the ``bzr sign-my-commits``
126
Most error messages, help topics and other user-visible text can now be
127
translated. Initial translations for Russian, Japanese and Spanish exist.
132
The ``po_merge`` plugin has been added. It provides a merge hook
133
to automate merging of changes to gettext template files. Refer to
134
``bzr help po_merge`` for documentation on how to
135
enable it and what it can do.
137
Documentation in texinfo format
138
*******************************
140
Sphinx (>= 1.1.2) provides a better texinfo builder than the alpha-quality
141
one provided with bzr sources. Most of the bzr documentation can be
142
processed and produce valid ``.info`` files.
147
For more detailed information on the changes made, see the the
148
:doc:`../release-notes/index` for:
150
* the interim bzr `milestones <https://launchpad.net/bzr/2.5>`_
151
* the plugins you use.
153
For a summary of changes made in earlier releases, see:
155
* :doc:`whats-new-in-2.1`
156
* :doc:`whats-new-in-2.2`
157
* :doc:`whats-new-in-2.3`
158
* :doc:`whats-new-in-2.4`
161
vim: tw=74 ft=rst ff=unix
added
removed
doc/en/whats-new/whats-new-in-2.5.txt
