1
*************************
2
What's New in Bazaar 2.5?
3
*************************
5
Bazaar 2.5 has 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
Bazaar 2.5.1 includes all the fixes in the un-released 2.0.7, 2.1.5, 2.2.6,
24
2.3.5 and 2.4.3 versions that weren't included in 2.5.0 and fixes some bugs
27
Overriding configuration options from the command line
28
******************************************************
30
The ``-O`` parameter available for all bzr commands allows a user to
31
override a configuration option from the command line. For example::
33
bzr pull -v -Olog_format=line
35
will change the way the pulled revisions are displayed (the default log
36
format is ``long``). This a work in progress and only some options are
39
Working on a posix system without a locale
40
******************************************
42
Previously bzr needed a valid locale set to work with branches containing
43
non-ascii filenames. It will now use utf-8 rather than ascii as a fallback
44
encoding for interacting with the filesystem. This makes creating a working
45
tree and commiting to it possible for such branches in most environments.
47
SSL Certificate Verification Support in urllib HTTPS backend
48
************************************************************
50
In previous versions of Bazaar, only one of the two supported HTTPS
51
backends, pycurl, supported verification of SSL certificates. This version
52
also introduces this support for the urllib backend.
54
Along with this support two new options have been introduced to control
55
which CA's are trusted and to what degree server certificates should be
56
verified. See ``bzr help ssl.ca_certs`` and ``bzr help ssl.cert_reqs``
59
Users who have previously used the urllib HTTPS backend with servers
60
with invalid or untrusted certificates can continue to do so by
61
adding the required certificates to the trusted CA certificate file
62
(recommended) or by setting the ``ssl.cert_reqs`` option to ``none``.
67
A large number of new methods have been added to the smart server, making
68
raw file access through the VFS unnecessary in almost all situations, with
69
the major exception of operations involving stacked branches.
71
Commands that have become significantly faster when using a remote branch
72
over ``bzr://``, ``bzr+ssh://`` or ``bzr+http://`` include:
74
* ``bzr checkout --lightweight``
80
Several commands which used to make multiple connections to the server now
81
make only a single one. Connection setup has a fairly high overhead,
82
especially to Launchpad, so this can save several seconds for some
85
To benefit from the improved smart server, both the server and the
86
client need to be running bzr 2.5.
88
Basic colocated branch support
89
******************************
91
The UI now has basic support for colocated branches. In full URLs,
92
a specific colocated branch can be specified using URL path segment
93
parameters. For example a branch named ``stronk`` could be addressed using
94
``http://example.com/path/to/dir,branch=stronk``.
96
The new ``bzr branches`` command can be used to list all present branches
97
in a directory, and indicates what the currently active branch is.
99
Several commands also accept co-located branch names directly, such as
105
All Bazaar formats now allow setting ``feature flags``. These can be used
106
by plugins to extend Bazaar formats and require the presence of particular
107
plugins or versions of Bazaar to open them, without having to introduce
108
completely new formats.
110
See ``doc/developers/feature-flags.txt`` for details.
112
Branch history access
113
*********************
115
Several commands or options that previously required access to the full
116
branch history now only access those parts of the history they actually
117
need. This significantly improves their performance for branches
118
with large histories.
123
A new command ``bzr verify-signatures`` can be used to verify GPG
124
signatures made with ``bzr commit`` or the ``bzr sign-my-commits``
130
Most error messages, help topics and other user-visible text can now be
131
translated. Initial translations for Russian, Japanese and Spanish exist.
136
The ``po_merge`` plugin has been added. It provides a merge hook
137
to automate merging of changes to gettext template files. Refer to
138
``bzr help po_merge`` for documentation on how to
139
enable it and what it can do.
141
Documentation in texinfo format
142
*******************************
144
Sphinx (>= 1.1.2) provides a better texinfo builder than the alpha-quality
145
one provided with bzr sources. Most of the bzr documentation can be
146
processed and produce valid ``.info`` files.
151
For more detailed information on the changes made, see the the
152
:doc:`../release-notes/index` for:
154
* the interim bzr `milestones <https://launchpad.net/bzr/2.5>`_
155
* the plugins you use.
157
For a summary of changes made in earlier releases, see:
159
* :doc:`whats-new-in-2.1`
160
* :doc:`whats-new-in-2.2`
161
* :doc:`whats-new-in-2.3`
162
* :doc:`whats-new-in-2.4`
165
vim: tw=74 ft=rst ff=unix
added
removed
doc/en/whats-new/whats-new-in-2.5.txt
