28
28
format is ``long``). This a work in progress and only some options are
31
Working on a posix system without a locale
32
******************************************
34
Previously bzr needed a valid locale set to work with branches containing
35
non-ascii filenames. It will now use utf-8 rather than ascii as a fallback
36
encoding for interacting with the filesystem. This makes creating a working
37
tree and commiting to it possible for such branches in most environments.
39
SSL Certificate Verification Support in urllib HTTPS backend
40
************************************************************
42
In previous versions of Bazaar, only one of the two supported HTTPS
43
backends, pycurl, supported verification of SSL certificates. This version
44
also introduces this support for the urllib backend.
46
Along with this support two new options have been introduced to control
47
which CA's are trusted and to what degree server certificates should be
48
verified. See ``bzr help ssl.ca_certs`` and ``bzr help ssl.cert_reqs``
51
Users who have previously used the urllib HTTPS backend with servers
52
with invalid or untrusted certificates can continue to do so by
53
adding the required certificates to the trusted CA certificate file
54
(recommended) or by setting the ``ssl.cert_reqs`` option to ``none``.
59
A large number of new methods have been added to the smart server, making
60
raw file access through the VFS unnecessary in almost all situations, with
61
the major exception of operations involving stacked branches.
63
Commands that have become significantly faster when using a remote branch
64
over ``bzr://``, ``bzr+ssh://`` or ``bzr+http://`` include:
66
* ``bzr checkout --lightweight``
72
Several commands which used to make multiple connections to the server now
73
make only a single one. Connection setup has a fairly high overhead,
74
especially to Launchpad, so this can save several seconds for some
77
To benefit from the improved smart server, both the server and the
78
client need to be running bzr 2.5.
80
Basic colocated branch support
81
******************************
83
The UI now has basic support for colocated branches. In full URLs,
84
a specific colocated branch can be specified using URL path segment
85
parameters. For example a branch named ``stronk`` could be addressed using
86
``http://example.com/path/to/dir,branch=stronk``.
88
The new ``bzr branches`` command can be used to list all present branches
89
in a directory, and indicates what the currently active branch is.
91
Several commands also accept co-located branch names directly, such as
97
All Bazaar formats now allow setting ``feature flags``. These can be used
98
by plugins to extend Bazaar formats and require the presence of particular
99
plugins or versions of Bazaar to open them, without having to introduce
100
completely new formats.
102
See ``doc/developers/feature-flags.txt`` for details.
104
Branch history access
105
*********************
107
Several commands or options that previously required access to the full
108
branch history now only access those parts of the history they actually
109
need. This significantly improves their performance for branches
110
with large histories.
115
A new command ``bzr verify-signatures`` can be used to verify GPG
116
signatures made with ``bzr commit`` or the ``bzr sign-my-commits``
122
Most error messages, help topics and other user-visible text can now be
123
translated. Initial translations for Russian, Japanese and Spanish exist.
128
The ``po_merge`` plugin has been added. It provides a merge hook
129
to automate merging of changes to gettext template files. Refer to
130
``bzr help po_merge`` for documentation on how to
131
enable it and what it can do.
32
133
Further information
33
134
*******************
added
removed
doc/en/whats-new/whats-new-in-2.5.txt
