1
*************************
2
What's New in Bazaar 2.4?
3
*************************
5
Bazaar 2.4 is still under development, and will be released in August 2011.
6
This document accumulates a high level summary of what's changed. See the
7
:doc:`../release-notes/index` for a full list.
9
Users are encouraged to upgrade from the other stable series. This
10
document outlines the improvements in Bazaar 2.4 vs Bazaar 2.3. As well as
11
summarizing improvements made to the core product, it highlights
12
enhancements within the broader Bazaar world of potential interest to
15
Bazaar 2.4.0 is fully compatible both locally and on the network with 2.0,
16
2.1, 2.2 and 2.3, and can read and write repositories generated by all
19
Dropping Python2.4 and Python2.5 support
20
****************************************
22
Bazaar 2.4.0 is the first version of bzr to drop support for python
23
versions before 2.6. The 2.3 series will still be maintained in bugfix
24
mode for people who need older versions of python. You can also use
25
Launchpad to nominate fixes for 2.3. We can't fix everything, but that can
26
help guide us to what people are running into. Upgrading to python2.6
27
allows us to clean up the syntax in our files, and makes it easier to work
28
on python3 compatibility.
33
External merge tool configuration has been added to ``bzr`` core. The name
34
and commandline of one or more external merge tools can be defined in
35
bazaar.conf. See the help topic ``configuration`` for more details.
37
Tagged revisions are copied
38
***************************
40
When tags are copied from a branch, the associated revisions are now copied
41
too. Previously operations like branching, merging or pulling might have
42
copied new tags visible in ``bzr tags``, but not copied the revisions. Now
43
revisions from tags will always be present, so that operations like ``bzr
44
log -r tag:foo`` will always work.
46
Deprecated command synonyms
47
***************************
49
Two built-in synonyms for ``bzr branch`` have been deprecated: ``clone`` and
55
Option values can now refer to other options in the same configuration file by
56
enclosing them in curly brackets (``{option}``). This is an opt-in feature
57
during the beta period controlled by the ``bzr.config.expand`` option that
58
should be declared in ``bazaar.conf`` and no other file.
60
Changelog merge plugin
61
**********************
63
The ``changelog_merge`` plugin has been added. It provides a merge hook
64
to automate merging of changes to ``ChangeLog`` files in GNU's change log
65
format. Refer to ``bzr help changelog_merge`` for documentation on how to
66
enable it and what it can do.
68
Faster operations on Large Trees
69
********************************
71
Many bzr commands used to run into pathological behavior on large trees
72
(>10k files), reading the inventory data in random order causing cache
73
thrashing. Various other tweaks have been applied with feedback from large
74
trees. A possibly incomplete list is as follows for running commands on a
77
bzr-2.3.1 bzr-2.3.2 bzr-2.4 action
78
3m39s 1m03s bzr co --lightweight
81
4m45s 29s 17s bzr pull
85
Faster stacked branches
86
***********************
88
Creating a stacked branch from a smart server with ``bzr branch
89
--stacked`` is a bit faster now. For small branches it does 20% fewer
90
network roundtrips. Other operations where a local branch is stacked on a
91
branch hosted on a smart server will also benefit.
96
For more detailed information on the changes made, see the the
97
:doc:`../release-notes/index` for:
99
* the interim bzr `milestones <https://launchpad.net/bzr/2.4>`_
100
* the plugins you use.
102
For a summary of changes made in earlier releases, see:
104
* :doc:`whats-new-in-2.1`
105
* :doc:`whats-new-in-2.2`
106
* :doc:`whats-new-in-2.3`
109
vim: tw=74 ft=rst ff=unix