Bazaar Revision Control System

Bazaar Revision Control System (also known as bzr) is an open source changeset-oriented revision control system based on Arch that makes it possible to retain previous changes to projects and coordinate development with other developers.

Its goal is to speed development of an upwards- compatible version of Arch.

Features:

• All the transparent and robust storage features of GNU Arch.
• seamless upgrade path to [WWW] bazaar-ng
• direct support for URLs - one command can checkout or merge from remote locations.
• integrated GPG support - zero setup for most signed archive situations
• faster - checkout, most local operations, commits
• svn-like diff, switch, import, export, log commands
• Explicit tracking of conflicts, preventing accidental commits of files with conflicts
• single merge command that allows merging between arbitrary branches.
• Daily builds of the latest code (Downloads).
• fully compatible with tla - drop in and start using
• supports debian version numbers in branch names
• annotate support
• internationalised via gettext and [WWW] Rosetta.
• Python bindings.

What is new in this release:

• External Compatibility Breaks:
• ``bzr lp-propose --approve`` now also adds an "Approve" vote to the merge proposal. (Jonathan Lange)
• New Features:
• ``bzr switch --store`` now stores uncommitted changes in the branch, and restores them when switching back to the branch. (Aaron Bentley)
• New option '--context' for 'bzr diff' command, to configure the amount of context (i.e. showing lines that have not changed). Also available as the named parameter 'context_lines' to bzrlib.diff.internal_diff(). (Paul Nixon)
• The 'grep' plugin is now shipped with bzr. (Jelmer Vernooij)
• The 'ping' plugin is now shipped with bzr. (Jelmer Vernooij)
• Improvements:
• ``bzr help env-variables`` now points users at ``bzr help configuration`` which has much more detailed information on the same stuff. (Robert Collins)
• ``bzr lp-find-proposal`` now only cares about the revision-id that is specified, not the branch you use. This was enabled by a new API call in Launchpad's web service. (Aaron Bentley)
• Implement authentication.conf password obfuscation, the password_encoding option can now be set to base64. (Florian Dorn)
• Local configurations files (i.e. accessed on the local file system like ``bazaar.conf`` and ``locations.conf``) are now shared, reducing the number of IOs when querying a configuation option. (Vincent Ladeuil, #832042)
• ``bzr lp-propose --approve`` now correctly specifies the approved revision and provides an "Approve" vote from the proposer, allowing for smoother interaction with downstream merge tools. (Jonathan Lange)
• Bug Fixes:
• Add a ``progress_bar`` configuration option defaulting to ``BZR_PROGRESS_BAR``. This can be set in ``bazaar.conf`` or specified from the command line with ``-Oprogress_bar=text``. (Vincent Ladeuil, #388275)
• ``Authentication.Config`` now always returns unicode user names and passwords. (Vincent Ladeuil, #514301)
• Fixed a bug where the entire contents of ``/etc/mailname`` is read in. We only want to read in the first line so that comments could be added and would be ignored. (Haw Loeung, #932515)
• Fixed a syntax error in ``doc/ja/user-guide/http_smart_server.txt`` that causes breakage with docutils 0.9.1. (Vincent Ladeuil, Jelmer Vernooij, #1066307)
• Support utf8 characters in platform names even without looking inside the box (Fedora's Schrodinger's Cat). (Toshio Kuratomi, Vincent Ladeuil, #1195783)
• Warn when ``--show-base`` is used for ``pull`` in a treeless branch instead of failing. It's useless but harmless. (Vincent Ladeuil, #1022160)
• When a missing referenced chk root error is encountered, bzr now suggests running ``bzr reconcile --canonicalize-chks``. (Jelmer Vernooij)
• When pushing a specific revision, create the new working tree at that revision. (#484516, Neil Martinsen-Burrell)

What is new in version 2.6 Beta 2:

• This release includes minor bug fixes and all know bug fixes including the ones made for the previous stable releases.

What is new in version 2.5.0:

• This release marks the start of a new long-term-stable series. From here, we will only make bugfix releases on the 2.5 series (2.5.1, etc, and support it until April 2017), while 2.6 will become our new development series. This is a bugfix and polish release over the 2.4 series, with a large number of bugs fixed (~170 for the 2.5 series alone). The 2.5 series provides a faster smart protocol implementation for many operations, basic support for colocated branches. We have started translating bzr with the 2.5 series: https://translations.launchpad.net/bzr, more than 20 languages have already been registered but these are the early days, contributions welcome.

What is new in version 2.4.2 / 2.5 Beta 6:

• This introduces the support for colocated branches into the '2a' format in a backward compatible way, fix more glitches in the colocated UI, verify https certificates for the urllib https client implementation, fix some more unicode issues and more.

What is new in version 2.5 Beta 5:

• This release includes many improvements in the smart server, UI polish for the colocated branches, enhancements to the config framework and more internal uses, bug fixes related to unicode and locale support and more.
• All bug fixed in previous series known at the time of this release are included.

What is new in version 2.5 Beta 4:

• This release includes many improvements in the smart server, UI polish for the colocated branches, optimizations for revision specifiers to avoid history sized operations, enhancements to the config framework, bug fixes related to unicode paths and more.

What is new in version 2.5 Beta 3:

• 2.5b3 contains all know bug fixes including the ones made for the previous stable releases.
• This release includes log options for ``push`` and ``pull``, more UI polish for colocated branches, a better and more coherent implementation for UI dialogs, enhancements to the config framework and more.

What is new in version 2.5 Beta 1:

• This is the first beta in the 2.5 series. 2.5.0 is planned to be released in February 2012. This beta release is suitable for everyday use, but may cause some incompatibilities with plugins. Some plugins may need small updates to work. All known bugfixes are included.

What is new in version 2.4.1:

• This is a bugfix release. Upgrading is recommended for all users on earlier 2.4 releases.
• 2.4.1 contains all known bug fixes for all stable releases (including the ones we made for the previous stable series).