2
2
What's New in Bazaar 2.3?
3
3
*************************
5
Bazaar 2.3 is still under development, and will be released in February
6
2011. This document accumulates a high level summary of what's changed.
5
Bazaar 2.3 has been released on the 3rd of February 2011 and marks the start
6
of another long-term-stable series. From here, we will only make bugfix
7
releases on the 2.3 series (2.3.1, etc), while 2.4 will become our new
8
development series. The 2.1 and 2.2 series will also continue to get
9
bugfixes. (Currently 2.0 is planned to be EOLed circa September 2011.)
11
This document accumulates a high level summary of what's changed.
8
13
:doc:`../release-notes/index` for a full list.
10
Users are encouraged to upgrade from the other stable series. This
11
document outlines the improvements in Bazaar 2.3 vs Bazaar 2.2. As well as
12
summarizing improvements made to the core product, it highlights
13
enhancements within the broader Bazaar world of potential interest to
16
Bazaar 2.3.0 is fully compatible both locally and on the network with 2.0
17
2.1, and 2.2, and can read and write repositories generated by all
15
Users are encouraged to upgrade from the other stable series. This document
16
outlines the improvements in Bazaar 2.3 vs Bazaar 2.2. As well as summarizing
17
improvements made to the core product, it highlights enhancements within the
18
broader Bazaar world of potential interest to those upgrading.
20
Bazaar 2.3.1 includes all the fixes in the un-released 2.0.7, 2.1.4 and 2.2.5
21
versions that weren't included in 2.3.0 and fixes some bugs on its own.
23
See the :doc:`../release-notes/index` for details.
25
Bazaar 2.3 is fully compatible both locally and on the network with 2.0, 2.1,
26
and 2.2. It can read and write repositories generated by all previous
32
* Committing a new revision in a stacked branch is now supported, as long as
33
you are using the current repository format (2a). It will preserve the
34
stacking invariants, etc, so that fetching after commit is guaranteed to
35
work. (John Arbash Meinel, #375013)
23
37
* Support for some old development formats have been removed:
24
38
``development-rich-root``, ``development6-rich-root``, and
25
39
``development7-rich-root``. These formats were always labelled experimental
38
52
get the old behavior, one can use ``bzr tags --sort=alpha``.
39
53
(Neil Martinsen-Burrell, #640760)
55
* On platforms other than Windows and Mac OS X, Bazaar will use configuration
56
files that live in $XDG_CONFIG_HOME/bazaar if that directory exists. This
57
allows interested individuals to conform to the XDG Base Directory
58
specification. The plugin location has not changed and is still
59
~/.bazaar/plugins. To use a different directory for plugins, use the
60
environment variable BZR_PLUGIN_PATH. (Neil Martinsen-Burrell, #195397)
62
* ``bzr upgrade`` now operates recursively when run on a shared
63
repository, automatically upgrading the branches within it, and has
64
grown additional options for showing what it will do and cleaning up
65
after itself. (Ian Clatworthy, Matthew Fuller, #89830, #374734, #422450)
41
67
Launchpad integration
42
68
*********************
46
72
``bzr launchpad-login user && bzr push lp:~/project/branch`` will now
47
73
push to ``lp:~user/project/branch``. (John Arbash Meinel)
75
* Launchpad has announced that the ``edge.launchpad.net`` instance is
76
deprecated and may be shut down in the future
77
<http://blog.launchpad.net/general/edge-is-deprecated>. Bazaar has therefore
78
been updated in this release to talk to the main (``launchpad.net``) servers,
79
rather than the ``edge`` ones.
49
81
Performance improvements
50
82
************************
56
88
* ``bzr send`` uses less memory.
57
89
(John Arbash Meinel, #614576)
91
* Fetches involving stacked branches and branches with tags now do slightly less
92
I/O, and so does branching from an existing branch. This also improves the
93
network performance of these operations. (Andrew Bennetts)
59
95
* Inventory entries now consume less memory (on 32-bit Ubuntu file entries
60
96
have dropped from 68 bytes to 40, and directory entries from 120 bytes
61
97
to 48). This affects most operations, and depending on the size of the
118
154
default behaviour is specified (if needed) by setting the variable to
119
155
``conflict``. (Vincent Ladeuil, #323111)
157
* ``bzr resolve --take-this`` and ``bzr resolve --take-other`` can now be
158
used for text conflicts. This will ignore the differences that were merged
159
cleanly and replace the file with its content in the current branch
160
(``--take-this``) or with its content in the merged branch
161
(``--take-other``). (Vincent Ladeuil, #638451)
121
163
* ``bzr resolve`` now provides more feedback about the conflicts just
122
164
resolved and the remaining ones. (Vincent Ladeuil)
138
180
working tree or branch as well as the ability to set or remove an
139
181
option. Scripts can also use it to get only the value for a given option.
141
Expected releases for the 2.3 series
142
************************************
144
The 2.3 series has entered the beta phase and 2.3.0 should be released soon
145
enough to be included into Natty Narwhal.
147
As a rough estimate, consider that 2.3.0 will be released in February
148
2011 and be supported until August 2012. Additional releases will be
149
made if critical bugs are encountered
152
183
Further information
153
184
*******************
added
removed
doc/en/whats-new/whats-new-in-2.3.txt
