5
5
.. contents:: List of Releases
9
bzr 2.1.0b3 (not released yet)
8
bzr 2.1.0b4 (not released yet)
10
9
##############################
11
:Codename: san francisco airport
23
* After renaming a file, the dirstate could accidentally reference
24
``source\\path`` rather than ``source/path`` on Windows. This might be a
25
source of some dirstate-related failures. (John Arbash Meinel)
27
* ``bzr ignore /`` no longer causes an IndexError. (Gorder Tyler, #456036)
29
* ``bzr mv --quiet`` really is quiet now. (Gordon Tyler, #271790)
31
* Lots of bugfixes for the test suite on Windows. We should once again
32
have a test suite with no failures on Windows. (Once all the patches
33
have landed, remove this line.) (John Arbash Meinel)
51
bzr 2.0.3 (not released yet)
52
############################
65
* Fix for shell completion and short options. (Benoît PIERRE)
67
* Improve "Binary files differ" hunk handling. (Aaron Bentley, #436325)
74
* Include Japanese translations for documentation (Inada Naoki)
90
:Codename: after sprint recovery
93
This release was pushed up from its normal release cycle due to a
94
regression in python 2.4 compatibility in 2.1.0b2. Since this regression
95
was caught before 2.1.0b2 was officially announced, the full changelog
96
includes both 2.1.0b3 and 2.1.0b2 changes.
98
Highlights of 2.1.0b3 are: new globbing code for all commands on Windows,
99
the test suite now conforms to python's trunk enhanced semantics (skip,
100
etc.), and ``bzr info -v`` will now report the correct branch and repo
101
formats for Remote objects.
107
* Users can define a shelve editor to provide shelf functionality at a
108
granularity finer than per-patch-hunk. (Aaron Bentley)
113
* Fix for shell completion and short options. (Benoît PIERRE)
24
115
* Hooks daughter classes should always call the base constructor.
25
116
(Alexander Belchenko, Vincent Ladeuil, #389648)
118
* Improve "Binary files differ" hunk handling. (Aaron Bentley, #436325)
27
120
* On Windows, do glob expansion at the command-line level (as is usually
28
121
done in bash, etc.) This means that *all* commands get glob expansion
29
122
(bzr status, bzr add, bzr mv, etc). It uses a custom command line
30
123
parser, which allows us to know if a given section was quoted. It means
31
you can now do ``bzr ignore "*.py"``. It also means that single-quotes
32
are now treated as quoted ``bzr ignore '*.py'``.
124
you can now do ``bzr ignore "*.py"``.
33
125
(John Arbash Meinel, #425510, #426410, #194450)
35
127
* Sanitize commit messages that come in from the '-m' flag. We translate
37
129
allow those because XML store silently translate it anyway. (The parser
38
130
auto-translates \r\n => \n in ways that are hard for us to catch.)
132
* Show correct branch and repository format descriptions in
133
``bzr info -v`` on a smart server location. (Andrew Bennetts, #196080)
40
135
* The fix for bug #186920 accidentally broke compatibility with python
41
136
2.4. (Vincent Ladeuil, #475585)
142
* Include Japanese translations for documentation (Inada Naoki)
147
* -Dhpssvfs will now trigger on ``RemoteBzrDir._ensure_real``, providing
148
more debugging of VFS access triggers. (Robert Collins)
59
150
* KnownFailure is now signalled to ``ExtendedTestResult`` using the same
60
151
method that Python 2.7 uses - ``addExpectedFailure``. (Robert Collins)
153
* ``--parallel=fork`` is now compatible with --subunit.
154
(Robert Collins, Vincent Ladeuil, #419776)
62
156
* TestNotApplicable is now handled within the TestCase.run method rather
63
157
than being looked for within ``ExtendedTestResult.addError``. This
64
158
provides better handling with other ``TestResult`` objects, degrading to
added
removed
NEWS
