Codename: | One and counting |
---|---|
2.3.4: | 2011-07-14 |
This is a bugfix release. Upgrading is recommended for all users of earlier 2.3 releases.
This mainly fixes bug #786980 which blocked the SRU process for Ubuntu Natty.
2.3.3: | 2011-05-13 |
---|
This is a bugfix release. Upgrading is recommended for all users of earlier 2.3 releases.
This fixed a bug in the test suite triggered by python-2.7 deprecating some tests helpers.
2.3.2: | 2011-05-12 |
---|
This is a bugfix release. Upgrading is recommended for all users of earlier 2.3 releases.
This was never released due to bug #760435 interrupting the release process by breaking the test suite under python-2.7 on natty.
None
None
Bazaar now infers the default user email address on Unix from the local account name plus the contents of /etc/mailname if that file exists. In particular, this means that committing as root through etckeeper will normally not require running bzr whoami first. (Martin Pool, #616878)
bzr merge --preview --pull should respect the --preview option first, and not actually change the branch tip revision. (John Arbash Meinel, Dennis Duchier, #760152)
bzr push into a repository (that doesn't have a branch), will no longer copy all revisions in the repository. Only the ones in the ancestry of the source branch, like it does in all other cases. (John Arbash Meinel, #465517)
Fix UnboundLocalError: local variable 'lock_url' in wait_lock error, especially while trying to save configuration from QBzr. (Martin Pool, #733136)
Fix "Unable to obtain lock" error when pushing to a bound branch if tags had changed. Bazaar was attempting to open and lock the master branch twice in this case. (Andrew Bennetts, #733350)
Standalone bzr.exe installation on Windows: user can put additional python libraries into site-packages subdirectory of the installation directory, this might be required for "installing" extra dependencies for some plugins. (Alexander Belchenko, #743256)
plugins because it's often too long. (Martin Pool, #716389)
None.
2.3.1: | 2011-03-10 |
---|
This is a bugfix release. Upgrading is recommended for all users of earlier 2.3 releases.
2.3.0: | 2011-02-03 |
---|
This release marks the start of another long-term-stable series. From here, we will only make bugfix releases on the 2.3 series (2.3.1, etc, and support it until August 2012), while 2.4 will become our new development series. The 2.1 and 2.2 series will also continue to get bugfixes. (Currently 2.0 is planned to be EOLed circa September 2011 and will receive only critical bugfixes.)
This is a bugfix and polish release over the 2.2 series, with a large number of bugs fixed (>130), and some performance improvements. Some features have been enhanced including commits on stacked branches, upgrades of related branches, shortcut URL schemes for ubuntu and debian on launchpad and better conflict resolution.
Only bugfixes from other stables series have been included since 2.3b5 so all known fixed bugs are included here.
Users are encouraged to upgrade from the other stable series.
2.3.b5: | 2011-01-13 |
---|
This is the fifth and last 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.3b5 includes bug fixes for committing to stacked branches, smoother upgrades of multiple branches, compatibility with python-2.7, full test suite passing on Ubuntu Natty and windows, less round-trips for several smart server operations, better support text conflicts resolve actions and some more.
All known fixed bugs in other series (2.0, 2.1, 2.2) are also included here.
(none)
2.3.b4: | 2010-12-03 |
---|
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.
(none)
2.3b3: | 2010-11-05 |
---|
(none)
2.3b2: | 2010-10-08 |
---|
2.3b1: | 2010-09-20 |
---|
This is the first beta of the 2.3 series, leading up to a 2.3.0 release in January or February. Beta releases are suitable for everyday use but may cause some incompatibilities with plugins. Some plugins may need small updates to work with 2.3b1.
2.3b1 includes some performance improvements in both speed and memory consumption, some preliminary support for generating a texinfo version of the doc and better support for launchpad. Many changes were made to make our test suite more robust as well as numerous documentation fixes. It improves the common infrastructure for dealing with colocated named branches and foreign branches. We plan to continue with these themes through the 2.3 series.
It also includes bug fixes for 2.0.6, 2.1.3 and 2.2.1 and over 40 fixes of its own.
(none)
When passing a file to UTF8DirReader make sure to close the current directory file handle after the chdir fails. Otherwise when passing many filenames into a command line bzr status we would leak descriptors. (John Arbash Meinel, #583486)
ControlDirFormat and ControlDir have been split out of BzrDirFormat and BzrDir, respectively. ControlDirFormat and ControlDir should be used as the base classes for new non-.bzr implementations.
BzrDirFormat.register_control_format has been renamed to ControlDirFormat.register_format.
BzrDirFormat.register_server_control_format has been removed.
Probing for control directories is now done by separate objects derived from bzrlib.controldir.Prober and registered using bzrlib.controldir.ControlDirFormat.register_prober or bzrlib.controldir.ControlDirFormat.register_server_prober. BzrDirFormat.probe_transport has been moved onto Prober.
BzrDirFormat.register_format has been renamed to BzrProber.register_bzrdir_format.
bzrlib.bzrdir.network_format_registry has been moved to bzrlib.controldir.
(Jelmer Vernooij)
bzrlib.transform.TreeTransformBase.final_kind, bzrlib.transform.TreeTransform.tree_kind and bzrlib.transform.TransformPreview.tree_kind now return None instead of raising NoSuchFile. (Vincent Ladeuil)
BzrError subclasses no longer support the name "message" to be used as an argument for __init__ or in _fmt format specification as this breaks in some Python versions. errors.LockError.__init__ argument is now named "msg" instead of earlier "message". (Parth Malwankar, #603461)
Configuration files should now use the from_string constructor rather than the file parameter of the _get_parser method. The later has been deprecated. from_string also accept a save=True parameter to have the configuration file immediately written to disk. (Vincent Ladeuil)
Deprecate treating a PushResult and PullResult as an integer for the relative change in revno. (Martin Pool)
FileInWrongBranch is deprecated in favour of PathNotChild and no longer raised. (Martin Pool)
IniBaseConfig objects should now use the from_string constructor the rather than the file parameter of the _get_parser method. The later has been deprecated. (Vincent Ladeuil)
InventoryEntry instances now raise AttributeError if you try to assign to attributes that are irrelevant to that kind of entry. e.g. setting symlink_target on an InventoryFile will fail. It is still okay to read those attributes on any kind of InventoryEntry. The complete list of affected attributes is: executable, text_id, text_sha1, text_size (only valid for kind == file); symlink_target (only valid for kind == link); and reference_revision (only valid for kind == tree-reference). (Andrew Bennetts)
InventoryEntry objects no longer have _put_in_tar or _put_on_disk methods. (Andrew Bennetts)
The get_filename parameter in the config.IniBaseConfig constructor has been deprecated, use the file_name parameter instead. (Vincent Ladeuil)
tree_files and internal_tree_files are now deprecated in favor of WorkingTree.open_containing_paths. (Martin Pool)
Codename: | Suggestions welcome |
---|---|
2.2.5: | NOT RELEASED YET |
2.2.4: | 2011-02-04 |
---|
This is a bugfix release. Only one bug has been fixed, a regression from 2.2.3 involving only certain operations with launchpad. Upgrading is recommended for all users on earlier 2.2 releases.
2.2.3: | 2011-01-20 |
---|
This is a bugfix release. Upgrading is recommended for all users on earlier 2.2 releases.
2.2.2: | 2010-11-25 |
---|
This is a bugfix release. None of these bugfixes are critical, but upgrading is recommended for all users on earlier 2.2 releases.
2.2.1: | 2010-09-17 |
---|
This is a bugfix release which also includes bugfixes from 2.0.6 and 2.1.3. None are critical, but upgrading is recommended for all users on earlier 2.2 releases.
Codename: | La Hulpe |
---|---|
2.2: | 2010-08-06 |
This release marks the start of another long-term-stable series. From here, we will only make bugfix releases on the 2.2 series (2.2.1, etc), while 2.3 will become our new development series. The 2.0 and 2.1 series will also continue to get bugfixes. (Currently 2.0 is planned to be supported for another 6 months.)
This is primarily a bugfix and polish release over the 2.1 series, with a large number of bugs fixed (>120), and some performance improvements.
There are some compatibility changes in this release. For users of bzrlib as a library, we now request that they call bzrlib.initialize and use the returned context manager appropriately. For commandline users we no longer guess user identity for bzr commit, users must specify their identity using bzr whoami (you don't need to specify your identity for readonly operations).
Users are encouraged to upgrade from the other stable series.
Codename: | Monkey Magic |
---|---|
2.2b4: | 2010-07-10 |
This fourth and final beta in the 2.2 series now stabilizes the internal APIs. Plugin authors are recommended to ensure their releases are compatible, so that 2.2rc1 can be a true release candidate, containing stable and compatible plugin versions.
For users of bzrlib as a library, one of the primary changes is to request that they call bzrlib.initialize and use the returned context manager appropriately.
Better interaction with bzr-loom to make sure branching from a loom even over a smart server still yields a local loom. Not to mention lots of bugfixes over 2.2b3.
2.2b3: | 2010-05-28 |
---|
This third beta in the 2.2 series brings with it all the goodness of 2.1.2 and 2.0.6 (though it preceeds 2.0.6 slightly). Of particular note for users are compatibility fixes with bzr 1.5 and below servers, a hopeful end to the EINTR errors caused by SIGWINCH interactions, a shiny new bash completion script and bzr will no longer guess at identity details - it was too unreliable in reality. Use bzr whoami on every new install. For developers we have some API changes which may impact plugins as well as a bunch of our regular improvements to internal clarity and test support.
Added bzrlib.tests.matchers as a place to put matchers, along with our first in-tree matcher. See the module docstring for details. (Robert Collins)
(Gordon Tyler, #551332)
Workaround Crypto.Random check leading to spurious test failures on Lucid, FreeBSD and gentoo. (Vincent Ladeuil, #528436)
New class ExecutableFeature for checking the availability of executables on the PATH. Migrated from bash_completion plugin. (Martin von Gagern)
2.2b2: | 2010-04-16 |
---|
This is a somewhat early second beta of the 2.2 series, to fix a python2.4 incompatibility in the 2.2b1 release. It also includes a swag of performance, usability and correctness improvements: test feedback on all of these would be welcome.
2.2b1: | 2010-04-01 |
---|
This is the first beta of the 2.2 series, leading up to a 2.2.0 release in July or August. Beta releases are suitable for everyday use but may cause some incompatibilities with plugins. Some plugins may need small updates to work with 2.2b1.
2.2b1 includes some changes to make merge conflicts easier to understand and resolve. It also removes some old unnecessary code, and loads somewhat less code at startup. It starts adding a common infrastructure for dealing with colocated named branches, which can be implemented in various ways in either bzr native or foreign formats. On Ubuntu and other platforms with the apport bug-reporting library, there's an easier path to report problems with bzr. We plan to continue with these themes through the 2.2 series.
Over thirty bugs have been fixed, including in the log command, exporting to tarballs, restarting interrupted system calls, portability of compiled extensions, making backups during upgrade, and locking on FTP.
Added docstring for Tree.iter_changes (John Arbash Meinel, #304182)
Allow additional arguments to RemoteRepository.add_inventory_by_delta(). (Jelmer Vernooij, #532631)
Allow exporting a single file using bzr export. (Michal Junák, #511987)
Allow syscalls to automatically restart when TextUIFactory's SIGWINCH handler is invoked, avoiding EINTR errors during blocking IO, which are often poorly handled by Python's libraries and parts of bzrlib. (Andrew Bennetts, #496813)
Avoid infinite recursion when probing for apport. (Vincent Ladeuil, #516934)
Avoid malloc(0) in patiencediff, which is non-portable. (Martin Pool, #331095)
Avoid truncating svn URLs. (Martin Pool, Martin von Gagern, #545185)
bzr add will not add conflict related files unless explicitly required. (Vincent Ladeuil, #322767, #414589)
bzr dump-btree now works on *.cix and *.six files. Those indices do not have reference lists, so dump-btree will simply show None instead. (Andrew Bennetts, #488607)
bzr help will no longer trigger the get_missing_command hook when doing a topic lookup. This avoids prompting (like 'no command plugins/loom, did you mean log?') when getting help. In future we may trigger the hook deliberately when no help topics match from any help index. (Robert Collins, #396261)
bzr log -n0 -r..A.B.C should not crash but just consider the None revspec as representing the first revision of the branch. (Vincent Ladeuil, #519862)
bzr remove-tree can now remove multiple working trees. (Jared Hance, Andrew Bennetts, #253137)
bzr resolve --take-this and --take-other now correctly renames the kept file on content conflicts where one side deleted the file. (Vincent Ladeuil, #529968)
bzr upgrade now creates the backup.bzr directory with the same permissions as .bzr directory on a POSIX OS. (Parth Malwankar, #262450)
bzr upgrade now names backup directory as backup.bzr.~N~ instead of backup.bzr. This directory is ignored by bzr commands such as add. (Parth Malwankar, #335033, #300001)
Cope with non-utf8 characters inside .bzrignore. (Jason Spashett, #183504)
Correctly interpret "451 Rename/move failure: Directory not empty" from FTP servers while trying to take a lock. (Martin Pool, #528722)
DirStateRevisionTree.kind() was returning wrong result when 'kind' changes occured between the workingtree and one of its parents. (Vincent Ladeuil, #535547)
Fix log to better check ancestors even if merged revisions are involved. (Vincent Ladeuil, #476293)
Loading a plugin from a given path with BZR_PLUGINS_AT doesn't depend on os.lisdir() order and is now reliable. (Vincent Ladeuil, #552922).
Many IO operations that returned EINTR were retried even if it wasn't safe to do so via careless use of until_no_eintr. Bazaar now only retries operations that are safe to retry, and in some cases has switched to operations that can be retried (e.g. sock.send rather than sock.sendall). (Andrew Bennetts, Martin <gzlist@googlemail.com>, #496813)
Path conflicts now support --take-this and --take-other even when a deletion is involved. (Vincent Ladeuil, #531967)
Network transfer amounts and rates are now displayed in SI units according to the Ubuntu Units Policy <https://wiki.ubuntu.com/UnitsPolicy>. (Gordon Tyler, #514399)
Support kind markers for socket and fifo filesystem objects. This prevents bzr status --short from crashing when those files are present. (John Arbash Meinel, #303275)
directory. (Parth Malwankar, #138600)
SSH child processes will now ignore SIGQUIT on nix systems so breaking into the debugger won't kill the session. (Martin <gzlist@googlemail.com>, #162502)
Tolerate patches with leading noise in bzr-handle-patch. (Toshio Kuratomi, Martin Pool, #502076)
update -r now supports updating to revisions that are not on mainline (i.e. it supports dotted revisions). (Parth Malwankar, #517800)
Use first apparent author not committer in GNU Changelog format. (Martin von Gagern, #513322)
2.1.5: | NOT RELEASED YET |
---|
2.1.4: | 2011-05-16 |
---|
The fourth release in our 2.1 series addresses some user-inconvenience bugs. None are critical, but upgrading is recommended for all users on earlier 2.1 releases.
None.
Codename: | Do run run |
---|---|
2.1.3: | 2010-09-17 |
The third release in our 2.1 series addresses several user-inconvenience bugs (and includes the fixes done in 2.0.6). None are critical, but upgrading is recommended for all users on earlier 2.1 releases.
2.1.2: | 2010-05-28 |
---|
This release fixes two critical networking issues with older servers and with interrupted system call errors when pushing or pulling. We recommend upgrading to anyone running a 2.1.x version of bzr.
2.1.1: | 2010-03-24 |
---|
This is a small bugfix release. Upgrading is recommended for anyone running 2.1.0 or earlier.
Codename: | Strasbourg |
---|---|
2.1.0: | 2010-02-11 |
This release marks our second long-term-stable series. The Bazaar team has decided that we will continue to make bugfix-only 2.0.x and 2.1.x releases, along with 2.2 development releases.
This is a fairly incremental update, focusing on polish and bugfixing. There are no changes for supported disk formats. Key updates include reduced memory consumption for many operations, a new per-file merge hook, ignore patterns can now include '!' to exclude files, globbing support for all commands on Windows, and support for addressing home directories via bzr+ssh://host/~/ syntax.
Users are encouraged to upgrade from the 2.0 stable series.
Codename: | after the bubbles |
---|---|
2.1.0rc2: | 2010-01-29 |
This is a quick-turn-around to update a small issue with our new per-file merge hook. We expect no major changes from this to the final 2.1.0.
Codename: | the 'new' stable |
---|---|
2.1.0rc1: | 2009-01-21 |
This is the first stable release candidate for Bazaar's 2.1 series. From this point onwards, the 2.1 series will be considered stable (as the 2.0 series) and only bugfixes are expected to be incorporated. The dozen or so bugfixes in the 2.0.4 release are also included in this release (along with more than 15 more bugfixes). Some of the interesting features are support for per-file merge hooks, bzr unshelve --preview, support for using ! in ignore files to exclude files from being ignored, a small memory leak was squashed, and many ObjectNotLocked errors were fixed. This looks to be a very good start for a new stable series.
Codename: | san francisco airport |
---|---|
2.1.0b4: | 2009-12-14 |
The fourth beta release in the 2.1 series brings with it a significant number of bugfixes (~20). The test suite is once again (finally) "green" on Windows, and should remain that way for future releases. There are a few performance related updates (faster upgrade and log), and several UI tweaks. There has also been a significant number of tweaks to the runtime documentation. 2.1.0b4 include everything from the 2.0.3 release.
Codename: | after sprint recovery |
---|---|
2.1.0b3: | 2009-11-16 |
This release was pushed up from its normal release cycle due to a regression in python 2.4 compatibility in 2.1.0b2. Since this regression was caught before 2.1.0b2 was officially announced, the full changelog includes both 2.1.0b3 and 2.1.0b2 changes.
Highlights of 2.1.0b3 are: new globbing code for all commands on Windows, the test suite now conforms to python's trunk enhanced semantics (skip, etc.), and bzr info -v will now report the correct branch and repo formats for Remote objects.
Codename: | a load off my mind |
---|---|
2.1.0b2: | 2009-11-02 |
This is our second feature-filled release since 2.0, pushing us down the path to a 2.1.0. Once again, all bugfixes in 2.0.2 are present in 2.1.0b2.
Key highlights in this release are: improved handling of failures-during-cleanup for commit, fixing a long-standing bug with bzr+http and shared repositories, all lp: URLs to be resolved behind proxies, and a new StaticTuple datatype, allowing us to reduce memory consumption (50%) and garbage collector overhead (40% faster) for many operations.
Codename: | While the cat is away |
---|---|
2.1.0b1: | 2009-10-14 |
This is the first development release in the new split "stable" and "development" series. As such, the release is a snapshot of bzr.dev without creating a release candidate first. This release includes a fair amount of internal changes, with deprecated code being removed, and several new feature developments. People looking for a stable code base with only bugfixes should focus on the 2.0.1 release. All bugfixes present in 2.0.1 are present in 2.1.0b1.
Highlights include support for bzr+ssh://host/~/homedir style URLs, finer control over the plugin search path via extended BZR_PLUGIN_PATH syntax, visible warnings when extension modules fail to load, and improved error handling during unlocking.
Bazaar can now send mail through Apple OS X Mail.app. (Brian de Alwis)
bzr+ssh and bzr paths can now be relative to home directories specified in the URL. Paths starting with a path segment of ~ are relative to the home directory of the user running the server, and paths starting with ~user are relative to the home directory of the named user. For example, for a user "bob" with a home directory of /home/bob, these URLs are all equivalent:
If bzr serve was invoked with a --directory argument, then no home directories outside that directory will be accessible via this method.
This is a feature of bzr serve, so pre-2.1 clients will automatically benefit from this feature when bzr on the server is upgraded. (Andrew Bennetts, #109143)
Extensions can now be compiled if either Cython or Pyrex is available. Currently Pyrex is preferred, but that may change in the future. (Arkanes)
Give more control on BZR_PLUGIN_PATH by providing a way to refer to or disable the user, site and core plugin directories. (Vincent Ladeuil, #412930, #316192, #145612)
2.0.7: | NOT RELEASED YET |
---|
2.0.6: | 2010-09-17 |
---|
The sixth release in our 2.0 series addresses several user-inconvenience bugs. None are critical, but upgrading is recommended for all users on earlier 2.0 releases.
2.0.5: | 2010-03-23 |
---|
This fifth release in our 2.0 series addresses several user-inconvenience bugs. None are critical, but upgrading is recommended for all users on earlier 2.0 releases.
Codename: | smooth sailing |
---|---|
2.0.4: | 2010-01-21 |
The fourth bugfix-only release in the 2.0 series contains more than a dozen bugfixes relative to 2.0.3. The primary focus is on handling interruptions and concurrent operations more cleanly, there is also a fair improvement to bzr export when exporting a remote branch.
Codename: | little italy |
---|---|
2.0.3: | 2009-12-14 |
The third stable release of Bazaar has a small handful of bugfixes. As expected, this has no internal or external compatibility changes versus 2.0.2 (or 2.0.0).
Codename: | after the scare |
---|---|
2.0.2: | 2009-11-02 |
The second in our "let's keep the stable bugfixes flowing" series. As expected this has a few (~9) bugfixes relative to 2.0.1, and no major api changes or features.
Codename: | Stability First |
---|---|
2.0.1: | 2009-10-14 |
The first of our new ongoing bugfix-only stable releases has arrived. It includes a collection of 12 bugfixes applied to bzr 2.0.0, but does not include any of the feature development in the 2.1.0 series.
2.0.0: | 2009-09-22 |
---|---|
Codename: | Instant Karma |
This release of Bazaar makes the 2a (previously 'brisbane-core') format the default when new branches or repositories are created. This format is substantially smaller and faster for many operations. Most of the work in this release focuses on bug fixes and stabilization, covering both 2a and previous formats. (See the Upgrade Guide for information on migrating existing projects.)
This release also improves the documentation content and presentation, including adding Windows HtmlHelp manuals.
The Bazaar team decided that 2.0 will be a long-term supported release, with bugfix-only 2.0.x releases based on it, continuing for at least six months or until the following stable release.
2.0.0rc2: | 2009-09-10 |
---|
Codename: | no worries |
---|---|
2.0.0rc1: | 2009-08-26 |
Codename: | nein nein nein! |
---|---|
1.18.1: | 2009-09-09 |
This release fixes two small but worthwhile bugs relevant to users on Microsoft Windows: some commands that failed on with locking errors will now work, and a bug that caused poor performance after committing a file with line-ending conversion has now been fixed. It also fixes a bug in pushing to older servers.
Codename: | little traveller |
---|---|
1.18: | 2009-08-20 |
1.18rc1: | 2009-08-10 |
This release of Bazaar marches on towards the 2.0 release in which the 2a 'brisbane-core' format becomes generally recommended. Most of the work in this release now focusses on bug fixes and stabilization, covering both 2a and previous formats. There is a new text-mode interactive merge feature, a new guide to migration to 2a format in the user documentation, and pushing branches to a smart server is now much faster.
The Bazaar team decided that 2.0 will be a long-term supported release, with bugfix-only releases based on it continuing for at least six months or until the following stable release.
There are no changes from 1.18rc1 to 1.18.
Codename: | so-late-its-brunch |
---|---|
1.17rc1: | 2009-07-13 |
1.17: | 2009-07-20 |
Bazaar continues to blaze a straight and shining path to the 2.0 release and the elevation of the 2a beta format to the full glory of "supported and stable".
Highlights in this release include greatly reduced memory consumption during commits, faster ls, faster annotate, faster network operations if you're specifying a revision number and the final destruction of those annoying progress bar artifacts.
Released: | 2009-06-26 |
---|
End user testing of the 2a format revealed two serious bugs. The first, #365615, caused bzr to raise AbsentContentFactory errors when autopacking. This meant that commits or pushes to 2a-format repositories failed intermittently.
The second bug, #390563, caused the smart server to raise AbsentContentFactory when streaming 2a stacked 2a-format branches. This particularly affected branches stored on Launchpad in the 2a format.
Both of these bugs cause command failures only, neither of them cause data corruption or data loss. And, of course, both of these bugs are now fixed.
Codename: | yesterday-in-california |
---|---|
1.16rc1: | 2009-06-11 |
1.16: | 2009-06-18 |
This version of Bazaar contains the beta release of the new 2a repository format, suitable for testing by fearless, advanced users. This format or an updated version of it will become the default format in Bazaar 2.0. Please read the NEWS entry before even thinking about upgrading to the new format.
Also included are speedups for many operations on huge projects, a bug fix for pushing stacked new stacked branches to smart servers and the usual bevy of bug fixes and improvements.
A new repository format 2a has been added. This is a beta release of the brisbane-core (aka group-compress) project. This format now suitable for wider testing by advanced users willing to deal with some bugs. We would appreciate test reports, either positive or negative. Format 2a is substantially smaller and faster for many operations on many trees. This format or an updated version will become the default in bzr 2.0.
This is a rich-root format, so this repository format can be used with bzr-svn. Bazaar branches in previous non-rich-root formats can be converted (including by merge, push and pull) to format 2a, but not vice versa. We recommend upgrading previous development formats to 2a.
Upgrading to this format can take considerable time because it expands and more concisely repacks the full history.
If you use stacked branches, you must upgrade the stacked branches before the stacked-on branches. (See <https://bugs.launchpad.net/bugs/374735>)
--development7-rich-root is a new dev format, similar to --dev6 but using a Revision serializer using bencode rather than XML. (Jelmer Vernooij, John Arbash Meinel)
mail_client=claws now supports --body (and message body hooks). Also uses configured from address. (Barry Warsaw)
--development6-rich-root can now stack. (Modulo some smart-server bugs with stacking and non default formats.) (John Arbash Meinel, #373455)
--development6-rich-root delays generating a delta index for the first object inserted into a group. This has a beneficial impact on bzr commit since each committed texts goes to its own group. For committing a 90MB file, it drops peak memory by about 200MB, and speeds up commit from 7s => 4s. (John Arbash Meinel)
Numerous operations are now faster for huge projects, i.e. those with a large number of files and/or a large number of revisions, particularly when the latest development format is used. These operations (and improvements on OpenOffice.org) include:
(Ian Clatworthy)
Pyrex version of bencode support. This provides optimized support for both encoding and decoding, and is now found at bzrlib.bencode. bzrlib.utils.bencode is now deprecated. (Alexander Belchenko, Jelmer Vernooij, John Arbash Meinel)
1.15rc1: | 2009-05-16 |
---|---|
1.15: | 2009-05-22 |
1.15.1: | 2009-06-09 |
The smart server will no longer raise 'NoSuchRevision' when streaming content with a size mismatch in a reconstructed graph search. New command bzr dpush. Plugins can now define their own annotation tie-breaker when two revisions introduce the exact same line.
Codename: | brisbane-core |
---|---|
1.14rc1: | 2009-04-06 |
1.14rc2: | 2009-04-19 |
1.14: | 2009-04-28 |
1.14.1: | 2009-05-01 |
New formats 1.14 and 1.14-rich-root supporting End-Of-Line (EOL) conversions, keyword templating (via the bzr-keywords plugin) and generic content filtering. End-of-line conversion is now supported for formats supporting content filtering.
Codename: | paraskavedekatriaphobia |
---|---|
1.13: | 2009-03-14 |
1.13rc1: | 2009-03-10 |
1.13.1: | 2009-03-23 |
1.13.2: | 2009-04-27 |
GNU Changelog output can now be produced by bzr log --gnu-changelog. Debug flags can now be set in ~/.bazaar/bazaar.conf. Lightweight checkouts and stacked branches should both be much faster over remote connections.
A regression was found in the 1.13.1 release. When bzr 1.13.1 and earlier push a stacked branch they do not take care to push all the parent inventories for the transferred revisions. This means that a smart server serving that branch often cannot calculate inventory deltas for the branch (because smart server does not/cannot open fallback repositories). Prior to 1.13 the server did not have a verb to stream revisions out of a repository, so that's why this bug has appeared now.
A couple regessions where found in the 1.13 release. The pyrex-generated C extensions are missing from the .tar.gz and .zip files. Documentation on how to generate GNU ChangeLogs is wrong.
Codename: | 1234567890 |
---|---|
1.12: | 2009-02-13 |
1.12rc1: | 2009-02-10 |
This release of Bazaar contains many improvements to the speed, documentation and functionality of bzr log and the display of logged revisions by bzr status. bzr now also gives a better indication of progress, both in the way operations are drawn onto a text terminal, and by showing the rate of network IO.
Codename: | "Eyes up!" |
---|---|
Released: | 2009-01-19 |
This first monthly release of Bazaar for 2009 improves Bazaar's operation in Windows, Mac OS X, and other situations where file names are matched without regard to capitalization: Bazaar tries to match the case of an existing file. This release of Bazaar also improves the efficiency of Tortoise Windows Shell integration and lets it work on 64-bit platforms.
The UI through which Bazaar supports historic formats has been improved, so 'bzr help formats' now gives a simpler and shorter list, with clear advice.
This release also fixes a number of bugs, particularly a glitch that can occur when there are concurrent writes to a pack repository.
Codename: | "Eyes up!" |
---|---|
Released: | 2009-01-09 |
Released: | 2008-12-05 |
---|
Bazaar 1.10 has several performance improvements for copying revisions (especially for small updates to large projects). There has also been a significant amount of effort in polishing stacked branches. The commands shelve and unshelve have become core commands, with an improved implementation.
The only changes versus bzr-1.10rc1 are bugfixes for stacked branches.
Released: | 2008-11-28 |
---|
This release of Bazaar focuses on performance improvements when pushing and pulling revisions, both locally and to remote networks. The popular shelve and unshelve commands, used to interactively revert and restore work in progress, have been merged from bzrtools into the bzr core. There are also bug fixes for portability, and for stacked branches.
Released: | 2008-11-07 |
---|
This release of Bazaar adds a new repository format, 1.9, with smaller and more efficient index files. This format can be specified when creating a new repository, or used to losslessly upgrade an existing repository. bzr 1.9 also speeds most operations over the smart server protocol, makes annotate faster, and uses less memory when making checkouts or pulling large amounts of data.
Released: | 2008-10-31 |
---|
Released: | 2008-10-16 |
---|
Bazaar 1.8 includes several fixes that improve working tree performance, display of revision logs, and merges. The bzr testsuite now passes on OS X and Python 2.6, and almost completely passes on Windows. The smartserver code has gained several bug fixes and performance improvements, and can now run server-side hooks within an HTTP server.
Released: | 2008-10-07 |
---|
Released: | 2008-09-24 |
---|
This release just includes an update to how the merge algorithm handles file paths when we encounter complex history.
Released: | 2008-09-23 |
---|
This release includes many bug fixes and a few performance and feature improvements. bzr rm will now scan for missing files and remove them, like how bzr add scans for unknown files and adds them. A bit more polish has been applied to the stacking code. The b-tree indexing code has been brought in, with an eye on using it in a future repository format. There are only minor installer changes since bzr-1.7rc2.
Released: | 2008-09-17 |
---|
A few bug fixes from 1.7rc1. The biggest change is a new RemoteBranch.get_stacked_on_url RPC. This allows clients that are trying to access a Stacked branch over the smart protocol, to properly connect to the stacked-on location.
Released: | 2008-09-09 |
---|
This release candidate for bzr 1.7 has several bug fixes and a few performance and feature improvements. bzr rm will now scan for missing files and remove them, like how bzr add scans for unknown files and adds them. A bit more polish has been applied to the stacking code. The b-tree indexing code has been brought in, with an eye on using it in a future repository format.
Released: | 2008-09-05 |
---|
A couple regressions were found in the 1.6 release. There was a performance issue when using bzr+ssh to branch large repositories, and some problems with stacking and rich-root capable repositories.
Released: | 2008-09-03 |
---|
Released: | 2008-08-29 |
---|
This release fixes a few regressions found in the 1.6 client. Fetching changes was using an O(N^2) buffering algorithm, so for large projects it would cause memory thrashing. There is also a specific problem with the --1.6-rich-root format, which prevented stacking on top of --rich-root-pack repositories, and could allow users to accidentally fetch experimental data (-subtree) without representing it properly. The --1.6-rich-root format has been deprecated and users are recommended to upgrade to --1.6.1-rich-root immediately. Also we re-introduced a workaround for users who have repositories with incorrect nodes (not possible if you only used official releases). I should also clarify that none of this is data loss level issues, but still sufficient enough to warrant an updated release.
Released: | 2008-08-25 |
---|
Finally, the long awaited bzr 1.6 has been released. This release includes new features like Stacked Branches, improved weave merge, and an updated server protocol (now on v3) which will allow for better cross version compatibility. With this release we have deprecated Knit format repositories, and recommend that users upgrade them, we will continue to support reading and writing them for the forseeable future, but we will not be tuning them for performance as pack repositories have proven to be better at scaling. This will also be the first release to bundle TortoiseBzr in the standalone Windows installer.
Released: | 2008-08-19 |
---|
Released: | 2008-08-18 |
---|
Released: | 2008-08-14 |
---|
Released: | 2008-08-13 |
---|
This release candidate has a few minor bug fixes, and some regression fixes for Windows.
Released: | 2008-08-06 |
---|
This release candidate for bzr 1.6 solidifies the new branch stacking feature. Bazaar now recommends that users upgrade all knit repositories, because later formats are much faster. However, we plan to continue read/write and upgrade support for knit repostories for the forseeable future. Several other bugs and performance issues were fixed.
Released: | 2008-07-17 |
---|
This release adds a new 'stacked branches' feature allowing branches to share storage without being in the same repository or on the same machine. (See the user guide for more details.) It also adds a new hook, improved weaves, aliases for related locations, faster bzr+ssh push, and several bug fixes.
Released: | 2008-06-10 |
---|
This release contains further progress towards our 1.6 goals of shallow repositories, and contains a fix for some user-affecting bugs in the repository layer. Building working trees during checkout and branch is now faster.
Released: | 2008-06-02 |
---|
Commands that work on the revision history such as push, pull, missing, uncommit and log are now substantially faster. This release adds a translation of some of the user documentation into Spanish. (Contributions of other translations would be very welcome.) Bazaar 1.6beta1 adds a new network protocol which is used by default and which allows for more efficient transfers and future extensions.
Released: | 2008-05-16 |
---|
This release of Bazaar includes several updates to the documentation, and fixes to prepare for making rich root support the default format. Many bugs have been squashed, including fixes to log, bzr+ssh inter-operation with older servers.
Released: | 2008-05-09 |
---|
Released: | 2008-04-28 |
---|
This release of Bazaar includes handy improvements to the speed of log and status, new options for several commands, improved documentation, and better hooks, including initial code for server-side hooks. A number of bugs have been fixed, particularly in interoperability between different formats or different releases of Bazaar over there network. There's been substantial internal work in both the repository and network code to enable new features and faster performance.
Released: | 2008-04-21 |
---|
Released: | 2008-04-11 |
---|
New -Dselftest_debug flag disables clearing of the debug flags during tests. This is useful if you want to use e.g. -Dhpss to help debug a failing test. Be aware that using this feature is likely to cause spurious test failures if used with the full suite. (Andrew Bennetts)
selftest --load-list now uses a new more agressive test loader that will avoid loading unneeded modules and building their tests. Plugins can use this new loader by defining a load_tests function instead of a test_suite function. (a forthcoming patch will provide many examples on how to implement this). (Vincent Ladeuil)
selftest --load-list now does some sanity checks regarding duplicate test IDs and tests present in the list but not found in the actual test suite. (Vincent Ladeuil)
Slightly more concise format for the selftest progress bar, so there's more space to show the test name. (Martin Pool)
[2500/10884, 1fail, 3miss in 1m29s] test_revisionnamespaces.TestRev
The test suite takes much less memory to run, and is a bit faster. This is done by clearing most attributes of TestCases after running them, if they succeeded. (Andrew Bennetts)
Released: | 2008-04-04 |
---|
Released: | 2008-03-20 |
---|
Bazaar has become part of the GNU project <http://www.gnu.org>
Many operations that act on history, including log and annotate are now substantially faster. Several bugs have been fixed and several new options and features have been added.
Released: | 2008-03-16 |
---|
Released: | 2008-02-13 |
---|
Released: | 2008-01-05 |
---|
Released: | 2007-12-14 |
---|
Released: | 2007-12-11 |
---|
Released: | 2007-12-07 |
---|
Released: | 2007-11-30 |
---|
The default repository format is now pack-0.92. This default is used when creating new repositories with init and init-repo, and when branching over bzr+ssh or bzr+hpss. (See https://bugs.launchpad.net/bugs/164626)
This format can be read and written by Bazaar 0.92 and later, and data can be transferred to and from older formats.
To upgrade, please reconcile your repository (bzr reconcile), and then upgrade (bzr upgrade).
pack-0.92 offers substantially better scaling and performance than the previous knits format. Some operations are slower where the code already had bad scaling characteristics under knits, the pack format makes such operations more visible as part of being more scalable overall. We will correct such operations over the coming releases and encourage the filing of bugs on any operation which you observe to be slower in a packs repository. One particular case that we do not intend to fix is pulling data from a pack repository into a knit repository over a high latency link; downgrading such data requires reinsertion of the file texts, and this is a classic space/time tradeoff. The current implementation is conservative on memory usage because we need to support converting data from any tree without problems. (Robert Collins, Martin Pool, #164476)
Released: | 2007-10-29 |
---|
Released: | 2007-09-26 |
---|
Released: | 2007-09-11 |
---|
Released: | 2007-09-11 |
---|
New option --author in bzr commit to specify the author of the change, if it's different from the committer. bzr log and bzr annotate display the author instead of the committer. (Lukáš Lalinský)
In addition to global options and command specific options, a set of standard options are now supported. Standard options are legal for all commands. The initial set of standard options are:
Unlike global options, standard options can be used in aliases and may have command-specific help. (Ian Clatworthy)
Verbosity level processing has now been unified. If --verbose or -v is specified on the command line multiple times, the verbosity level is made positive the first time then increased. If --quiet or -q is specified on the command line multiple times, the verbosity level is made negative the first time then decreased. To get the default verbosity level of zero, either specify none of the above , --no-verbose or --no-quiet. Note that most commands currently ignore the magnitude of the verbosity level but do respect quiet vs normal vs verbose when generating output. (Ian Clatworthy)
Branch.hooks now supports pre_commit hook. The hook's signature is documented in BranchHooks constructor. (Nam T. Nguyen, #102747)
New Repository.stream_knit_data_for_revisions request added to the network protocol for greatly reduced roundtrips when retrieving a set of revisions. (Andrew Bennetts)
Released: | 2007-08-28 |
---|
Released: | 2007-08-14 |
---|
Released: | 2007-07-10 |
---|
The --lsprof-file option now dumps a text rendering of the profiling information if the filename ends in ".txt". It will also convert the profiling information to a format suitable for KCacheGrind if the output filename ends in ".callgrind". Fixes to the lsprofcalltree conversion process by Jean Paul Calderone and Itamar were also merged. See http://ddaa.net/blog/python/lsprof-calltree. (Ian Clatworthy)
info now defaults to non-verbose mode, displaying only paths and abbreviated format info. info -v displays all the information formerly displayed by info. (Aaron Bentley, Adeodato Simó)
bzr missing now has better option names --this and --other. (Elliot Murphy)
The internal weave-list command has become versionedfile-list, and now lists knits as well as weaves. (Aaron Bentley)
Automatic merge base selection uses a faster algorithm that chooses better bases in criss-cross merge situations (Aaron Bentley)
Progress reporting in commit has been improved. The various logical stages are now reported on as follows, namely:
If there is no master branch, the 3rd stage is omitted and the total number of stages is adjusted accordingly.
Each hook that is run after commit is listed with a name (as hooks can be slow it is useful feedback). (Ian Clatworthy, Robert Collins)
Various operations that are now faster due to avoiding unnecessary topological sorts. (Aaron Bentley)
Make merge directives robust against broken bundles. (Aaron Bentley)
The lsprof filename note is emitted via trace.note(), not standard output. (Aaron Bentley)
bzrlib now exports explicit API compatibility information to assist library users and plugins. See the bzrlib.api module for details. (Robert Collins)
Remove unnecessary lock probes when acquiring a lockdir. (Martin Pool)
bzr --version now shows the location of the bzr log file, which is especially useful on Windows. (Martin Pool)
-D now supports hooks to get debug tracing of hooks (though its currently minimal in nature). (Robert Collins)
Long log format reports deltas on merge revisions. (John Arbash Meinel, Kent Gibson)
Make initial push over FTP more resilient. (John Arbash Meinel)
Print a summary of changes for update just like pull does. (Daniel Watkins, #113990)
Add a -Dhpss option to trace smart protocol requests and responses. (Andrew Bennetts)
Released: | 2007-06-18 |
---|
Released: | 2007-06-12 |
---|
The kind() and is_executable() APIs on the WorkingTree interface no longer implicitly (read) locks and unlocks the tree. This might impact some plug-ins and tools using this part of the API. If you find an issue that may be caused by this change, please let us know, particularly the plug-in/tool maintainer. If encountered, the API fix is to surround kind() and is_executable() calls with lock_read() and unlock() like so:
work_tree.lock_read() try: kind = work_tree.kind(...) finally: work_tree.unlock()
Released: | 2007-05-07 |
---|
Released: | 2007-04-30 |
---|
Released: | 2007-04-26 |
---|
Released: | 2007-04-01 |
---|
Released: | 2007-03-26 |
---|
Released: | 2007-03-14 |
---|
Released: | 2007-03-07 |
---|
Released: | 2007-01-23 |
---|
Released: | 2007-01-16 |
---|
New connection: bzr+http:// which supports tunnelling the smart protocol over an HTTP connection. If writing is enabled on the bzr server, then you can write over the HTTP connection. (Andrew Bennetts, John Arbash Meinel)
Aliases now support quotation marks, so they can contain whitespace (Marius Kruger)
PyCurlTransport now use a single curl object. By specifying explicitly the 'Range' header, we avoid the need to use two different curl objects (and two connections to the same server). (Vincent Ladeuil)
bzr commit does not prompt for a message until it is very likely to succeed. (Aaron Bentley)
bzr conflicts now takes --text to list pathnames of text conflicts (Aaron Bentley)
Fix iter_lines_added_or_present_in_versions to use a set instead of a list while checking if a revision id was requested. Takes 10s off of the fileids_affected_by_revision_ids time, which is 10s of the bzr branch time. Also improve fileids_... time by filtering lines with a regex rather than multiple str.find() calls. (saves another 300ms) (John Arbash Meinel)
Policy can be set for each configuration key. This allows keys to be inherited properly across configuration entries. For example, this should enable you to do:
[/home/user/project] push_location = sftp://host/srv/project/ push_location:policy = appendpath
And then a branch like /home/user/project/mybranch should get an automatic push location of sftp://host/srv/project/mybranch. (James Henstridge)
Added bzr status --short to make status report svn style flags for each file. For example:
$ bzr status --short A foo A bar D baz ? wooley
'bzr selftest --clean-output' allows easily clean temporary tests directories without running tests. (Alexander Belchenko)
bzr help hidden-commands lists all hidden commands. (Aaron Bentley)
bzr merge now has an option --pull to fall back to pull if local is fully merged into remote. (Jan Hudec)
bzr help formats describes available directory formats. (Aaron Bentley)
Released: | 2006-11-27 |
---|
Released: | 2006-10-30 |
---|
Released: | 2006-10-23 |
---|
Released: | 2006-10-02 |
---|
Released: | 2006-09-27 |
---|
Released: | 2006-09-25 |
---|
Released: | 2006-08-29 |
---|
Released: | 2006-08-11 |
---|
Released: | 2006-05-16 |
---|
Released: | 2006-05-08 |
---|
Release 0.8 of bzr introduces a new format for history storage, called 'knit', as an evolution of to the 'weave' format used in 0.7. Local and remote operations are faster using knits than weaves. Several operations including 'init', 'init-repo', and 'upgrade' take a --format option that controls this. Branching from an existing branch will keep the same format.
It is possible to merge, pull and push between branches of different formats but this is slower than moving data between homogenous branches. It is therefore recommended (but not required) that you upgrade all branches for a project at the same time. Information on formats is shown by 'bzr info'.
bzr 0.8 now allows creation of 'repositories', which hold the history of files and revisions for several branches. Previously bzr kept all the history for a branch within the .bzr directory at the root of the branch, and this is still the default. To create a repository, use the new 'bzr init-repo' command. Branches exist as directories under the repository and contain just a small amount of information indicating the current revision of the branch.
bzr 0.8 also supports 'checkouts', which are similar to in cvs and subversion. Checkouts are associated with a branch (optionally in a repository), which contains all the historical information. The result is that a checkout can be deleted without losing any already-committed revisions. A new 'update' command is also available.
Repositories and checkouts are not supported with the 0.7 storage format. To use them you must upgrad to either knits, or to the 'metaweave' format, which uses weaves but changes the .bzr directory arrangement.
SFTP paths can now be relative, or local, according to the lftp convention. Paths now take the form:
sftp://user:pass@host:port/~/relative/path or sftp://user:pass@host:port/absolute/path
The FTP transport now tries to reconnect after a temporary failure. FTP put is made atomic. (Matthieu Moy)
The FTP transport now maintains a pool of connections, and reuses them to avoid multiple connections to the same host (like SFTP did). (Daniel Silverstone)
The bzr_man.py file has been removed. To create the man page now, use ./generate_docs.py man. The new program can also create other files. Run python generate_docs.py --help for usage information. (Hans Ulrich Niedermann & James Blackwell).
Man Page now gives full help (James Blackwell). Help also updated to reflect user config now being stored in .bazaar (Hans Ulrich Niedermann)
It's now possible to set aliases in bazaar.conf (Erik Bågfors)
Pull now accepts a --revision argument (Erik Bågfors)
bzr re-sign now allows multiple revisions to be supplied on the command line. You can now use the following command to sign all of your old commits:
find .bzr/revision-store// -name my@email-* \ | sed 's/.*\/\/..\///' \ | xargs bzr re-sign
Upgrade can now upgrade over the network. (Robert Collins)
Two new commands 'bzr checkout' and 'bzr update' allow for CVS/SVN-alike behaviour. By default they will cache history in the checkout, but with --lightweight almost all data is kept in the master branch. (Robert Collins)
'revert' unversions newly-versioned files, instead of deleting them.
'merge' is more robust. Conflict messages have changed.
'merge' and 'revert' no longer clobber existing files that end in '~' or '.moved'.
Default log format can be set in configuration and plugins can register their own formatters. (Erik Bågfors)
New 'reconcile' command will check branch consistency and repair indexes that can become out of sync in pre 0.8 formats. (Robert Collins, Daniel Silverstone)
New 'bzr init --format' and 'bzr upgrade --format' option to control what storage format is created or produced. (Robert Collins, Martin Pool)
Add parent location to 'bzr info', if there is one. (Olaf Conradi)
New developer commands 'weave-list' and 'weave-join'. (Martin Pool)
New 'init-repository' command, plus support for repositories in 'init' and 'branch' (Aaron Bentley, Erik Bågfors, Robert Collins)
Improve output of 'info' command. Show all relevant locations related to working tree, branch and repository. Use kibibytes for binary quantities. Fix off-by-one error in missing revisions of working tree. Make 'info' work on branches, repositories and remote locations. Show locations relative to the shared repository, if applicable. Show locking status of locations. (Olaf Conradi)
Diff and merge now safely handle binary files. (Aaron Bentley)
'pull' and 'push' now normalise the revision history, so that any two branches with the same tip revision will have the same output from 'log'. (Robert Collins)
'merge' accepts --remember option to store parent location, like 'push' and 'pull'. (Olaf Conradi)
bzr status and diff when files given as arguments do not exist in the relevant trees. (Martin Pool, #3619)
Add '.hg' to the default ignore list. (Martin Pool)
'knit' is now the default disk format. This improves disk performance and utilization, increases incremental pull performance, robustness with SFTP and allows checkouts over SFTP to perform acceptably. The initial Knit code was contributed by Johan Rydberg based on a specification by Martin Pool. (Robert Collins, Aaron Bentley, Johan Rydberg, Martin Pool).
New tool to generate all-in-one html version of the manual. (Alexander Belchenko)
Hitting CTRL-C while doing an SFTP push will no longer cause stale locks to be left in the SFTP repository. (Robert Collins, Martin Pool).
New option 'diff --prefix' to control how files are named in diff output, with shortcuts '-p0' and '-p1' corresponding to the options for GNU patch. (Alexander Belchenko, Goffredo Baroncelli, Martin Pool)
Add --revision option to 'annotate' command. (Olaf Conradi)
If bzr shows an unexpected revision-history after pulling (perhaps due to a reweave) it can now be corrected by 'bzr reconcile'. (Robert Collins)
Released: | 2006-01-09 |
---|
WorkingTree.pull has been split across Branch and WorkingTree, to allow Branch only pulls. (Robert Collins)
commands.display_command now returns the result of the decorated function. (Robert Collins)
LocationConfig now has a set_user_option(key, value) call to save a setting in its matching location section (a new one is created if needed). (Robert Collins)
Branch has two new methods, get_push_location and set_push_location to respectively, get and set the push location. (Robert Collins)
commands.register_command now takes an optional flag to signal that the registrant is planning to decorate an existing command. When given multiple plugins registering a command is not an error, and the original command class (whether built in or a plugin based one) is returned to the caller. There is a new error 'MustUseDecorated' for signalling when a wrapping command should switch to the original version. (Robert Collins)
Some option parsing errors will raise 'BzrOptionError', allowing granular detection for decorating commands. (Robert Collins).
Branch.read_working_inventory has moved to WorkingTree.read_working_inventory. This necessitated changes to Branch.get_root_id, and a move of Branch.set_inventory to WorkingTree as well. To make it clear that a WorkingTree cannot always be obtained Branch.working_tree() will raise errors.NoWorkingTree if one cannot be obtained. (Robert Collins)
All pending merges operations from Branch are now on WorkingTree. (Robert Collins)
The follow operations from Branch have moved to WorkingTree:
add() commit() move() rename_one() unknowns()
(Robert Collins)
bzrlib.add.smart_add_branch is now smart_add_tree. (Robert Collins)
New "rio" serialization format, similar to rfc-822. (Martin Pool)
Rename selftests to bzrlib.tests.test_foo. (John A Meinel, Martin Pool)
bzrlib.plugin.all_plugins has been changed from an attribute to a query method. (Robert Collins)
New options to read only the table-of-contents of a weave. (Denys Duchier)
Raise NoSuchFile when someone tries to add a non-existant file. (Michael Ellerman)
Simplify handling of DivergedBranches in cmd_pull(). (Michael Ellerman)
Branch.controlfile* logic has moved to lockablefiles.LockableFiles, which is exposed as Branch().control_files. Also this has been altered with the controlfile pre/suffix replaced by simple method names like 'get' and 'put'. (Aaron Bentley, Robert Collins).
Deprecated functions and methods can now be marked as such using the bzrlib.symbol_versioning module. Marked method have their docstring updated and will issue a DeprecationWarning using the warnings module when they are used. (Robert Collins)
bzrlib.osutils.safe_unicode now exists to provide parameter coercion for functions that need unicode strings. (Robert Collins)
Released: | 2005-10-28 |
---|
Released: | 2005-10-12 |
---|
Released: | 2005-10-11 |
---|
Released: | 2005-09-23 |
---|
Released: | 2005-09-20 |
---|
Released: | 2005-09-02 |
---|
Released: | 2005-08-18 |
---|
Released: | 2005-06-15 |
---|
Released: | 2005-04-22 |
---|
Released: | 2005-04-06 |
---|
Codename: | "black cube" |
---|---|
Released: | 2005-03-31 |
Released: | 2005-03-26 |
---|
Released: | 2005-03-22 |
---|