[ANN] bzr 2.3b4 released !

[vila]

The Bazaar team is happy to announce availability of a new
release of the bzr adaptive version control system.
Bazaar is part of the GNU system <http://gnu.org/>.

This is the fourth beta of the 2.3 series, leading up to a 2.3.0 release in
February. Beta releases are suitable for everyday use but may cause some
incompatibilities with plugins.

2.3b4 includes bug fixes for the ``config`` command and conflict
resolution. More changes were made for the test scripts handling to make it
easier to add reproducing recipes to bugs.

It also includes bug fixes from the 2.2.2 release as well as the bug fixes
in the upcoming 2.0.7, 2.1.4 and 2.2.3 releases. This means that all known
fixed bugs at the time of this release are included.

Thanks to everyone who contributed patches, suggestions, and feedback.

Bazaar is now available for download from
https://launchpad.net/bzr/2.3/2.3b4/ as a source tarball;

Packages are available for:

- Ubuntu: https://launchpad.net/~bzr-beta-ppa/+archive/ppa,
- OSX: https://launchpad.net/bzr/2.3/2.3b4/

Packages for various other systems will be available soon (including
windows).

Thanks to everyone who helped packaging.

bzr 2.3b4
#########

:2.3.b4: 2010-12-03

*****************************

  (none)

Improvements
************

* Bazaar now caches a branch's tags while that branch is read-locked.
  This removes 1 network roundtrip from most interactions with a remote
  branch. (Andrew Bennetts)

* ``bzr config <option>`` will now display only the value itself so scripts
  can use it to query the currently active configuration. Displaying several
  options matching a given regular expression is now controlled via the
  ``--all`` option. (Vincent Ladeuil, bug #670251)

* ``bzr resolve`` now reports the number of conflicts resolved and the
  number of remaining conflicts. This provides a better feedback about the
  whole resolution process. (Vincent Ladeuil)

* Read configuration files in $XDG_CONFIG_HOME/bazaar on Unix if there is
  already a directory there. (Neil Martinsen-Burrell, #195397)

Bug Fixes
*********

* Better message if there is an error while setting ownership of
  ``.bazaar`` directory. (Parth Malwankar, #657553)

* ``bzr config`` properly displays list values. (Vincent Ladeuil, #672382)

* ``bzr config`` will now respect option policies when displaying the value
  and display the definition sections when appropriate.
  (Vincent Ladeuil, #671050)

* Don't create commit message files in the current directory to avoid nasty
  interactions with emacs (which tries to establish the status of the file
  during the commit which breaks on windows). (Vincent Ladeuil, #673637)

* ``bzr resolve --take-other <file>`` will not crash anymore if ``<file>``
  is involved in a text conflict (but the conflict is still not
  resolved). (Vincent Ladeuil, #646961)

* Merge will now correctly locate a lca where there is a criss-cross merge
  of a new root. (Gary van der Merwe, #588698)

* Report error if non-ASCII command option given. (Rory Yorke, #140563)

* ``tools/check-newsbug.py`` is now based on ``lp:hydrazine`` and no longer
  crashes when encountering private bugs (they are just displayed as such).
  (Vincent Ladeuil, #354985)

Internals
*********

* ``BranchBuilder.build_snapshot`` now accepts parent_ids == [].
  This can be used to create a new root in the graph. (Gary van der Merwe)

* Old repository development formats
  RepositoryFormatCHK1 and RepositoryFormatCHK2 have been removed, and so
  have the corresponding metadir format options ``development-rich-root``,
  ``development6-rich-root``, and ``development7-rich-root``.

Testing
*******

* Add a null_output_matches_anything keyword argument with default False to
  bzrlib.tests.script.ScriptRunner.run_script to specify that the command
  output should not be checked (as opposed to expecting an empty output).
  (Neil Martinsen-Burrell, #662509)

* Blank output section in scriptrunner tests no longer match any output.
  Instead, use '...' as a wildcard if you don't care about the output.
  (Martin Pool, #637830)

* Bump minimum testtools version required to run ``bzr selftest`` from 0.9.2
  to 0.9.5 which will allow tests that need the fixed unicode handling to be
  written. (Martin [gz])

* Printing selftest results to a non-UTF-8 console will now escape characters
  that can't be encoded rather than aborting the test run with an exception.
  (Martin [gz], #633216)

--E402B1815F4.1291905204/axe--