Bazaar VCS 1.8 RC1 / 1.7.1
Bazaar VCS 1.8 RC1 / 1.7.1 Ranking & Summary
Bazaar VCS 1.8 RC1 / 1.7.1 description
Bazaar is a distributed version control system available under the GPL that reduces barriers to participation in your project.
Bazaar is designed to support Mac OS, GNU/Linux, UNIX, Windows. In summary, Bazaar gives you fast, distributed revision control that "Just Works", supporting renames of directories and files smoothly. Bazaar is designed to maximise the level of community participation in your project.
Bazaar branches can be published on any web server, and uploaded over sftp, ftp, or rsync. If you want the fastest possible network performance, there is a smart server.
Bazaar supports flexible work models: centralized like cvs or svn, commit offline, enforced code review when desired, and automatic regression testing.
Decentralized revision control systems give people the ability to collaborate more efficiently over the internet using the bazaar development model and have many other advantages.
When you use Bazaar, you can commit to your own local branches of your favourite free software projects without needing special permission.
Features of "Bazaar VCS":
Good performance:
· Bazaar status in a tree of 5,000 files takes just 0.5 seconds, so almost every open source project can get the advanced features of Bazaar without slowing down its developers. Bazaar is robust in the face of radical tree restructuring, saving you time when it comes to merging from your community.
Safe with your data:
· There have not been any data loss bugs in a Bazaar release in the past two years. Bazaar has a huge test suite that ensures that new file formats can be tested automatically. The development process follows best practice with code review of all core and community code landings.
Friendly:
· Bazaar "Just Works" (which is why the Ubuntu team chose it for their project). Bazaar has a natural feel, you can publish your code on any web server or use a custom server for performance. Bazaar has perfect support for renaming files AND directories, which means you can unleash your community and merge efficiently even from contributors who are radically restructuring the tree.
Free:
· Bazaar is available under the GPL v2 or later.
Easy to integrate:
· Bazaar is designed as a Python API with a plugin system, so it is easy to embed in your tools and projects and easy to extend or integrate with existing infrastructure. Whether you are managing your development, or keeping track of configuration files, or building a new content management system, Bazaar is a great choice if you like to work in Python.
Requirements:
·
Changes from previous version
· ``bzr log file`` has been changed. It now uses a different method for determining which revisions to show as merging the changes to the file. It now only shows revisions which merged the change towards your mainline. This simplifies the output, makes it faster, and reduces memory consumption. (John Arbash Meinel)
· ``bzr merge`` now defaults to having ``--reprocess`` set, whenever ``--show-base`` is not supplied. (John Arbash Meinel)
· ``bzr+http//`` will now optionally load plugins and write logs on the server. (Marius Kruger)
· ``bzrlib._dirstate_helpers_c.pyx`` does not compile correctly with Pyrex 0.9.4.1 (it generates C code which causes segfaults). We explicitly blacklist that version of the compiler for that extension. Packaged versions will include .c files created with pyrex >= 0.9.6 so it doesnt effect releases, only users running from the source tree. (John Arbash Meinel, #276868)
· bzr is now compatible with python-2.6. python-2.6 is not yet officially supported (nor released, tests were conducted with the dev version of python-2.6rc2), but all known problems have been fixed. Feedback welcome. (Vincent Ladeuil, #269535)
· ``bzr annotate`` will now include uncommitted changes from the local working tree by default. Such uncommitted changes are given the revision number they would get if a commit was done, followed with a ? to indicate that its not actually known. (Robert Collins, #3439)
· ``bzr branch`` now accepts a ``--standalone`` option, which creates a standalone branch regardless of the presence of shared repositories. (Daniel Watkins)
· ``bzr push`` is faster in the case there are no new revisions to push. It is also faster if there are no tags in the local branch. (Andrew Bennetts)
· File changes during a commit will update the tree stat cache. (Robert Collins)
· Location aliases can now accept a trailing path. (Micheal Hudson)
· New hooks ``Lock.hooks`` when LockDirs are acquired and released. (Robert Collins, MartinPool)
· Switching in heavyweight checkouts uses the master branchs context, not the checkouts context. (Adrian Wilkins)
· ``status`` on large trees is now faster, due to optimisations in the walkdirs code. Of particular note, the walkdirs code now performs a temporary ``chdir()`` while reading a single directory; if your platform has non thread-local current working directories (and is not windows which has its own implementation), this may introduce a race condition during concurrent uses of bzrlib. The bzrlib CLI will not encounter this as it is single threaded for working tree operations. (Robert Collins)
· The C extensions now build on python 2.4 (Robert Collins, #271939)
· The ``-Dhpss`` debug flag now reports the number of smart server calls per medium to stderr. This is in addition to the existing detailed logging to the .bzr.log trace file. (Andrew Bennetts)
· Avoid random failures arising from misinterpreted ``errno`` values in ``_readdir_pyx.read_dir``. (Martin Pool, #279381)
· Branching from a shared repository on a smart server into a new repository now preserves the repository format. (Andrew Bennetts, #269214)
· ``bzr log`` now accepts a ``--change`` option. (Vincent Ladeuil, #248427)
· ``bzr missing`` now accepts an ``--include-merges`` option. (Vincent Ladeuil, #233817)
· Dont try to filter (internally) .bzr from the files to be deleted if its not there. (Vincent Ladeuil, #272648)
· Fix _in_buffer AttributeError when using the -Dhpss debug flag. (Andrew Bennetts)
· Fix TooManyConcurrentRequests errors caused by a connection failure when doing ``bzr pull`` or ``bzr merge`` from a ``bzr+ssh`` URL. (Andrew Bennetts, #246233)
· Fixed ``bzr st -r branch:PATH_TO_BRANCH`` where the other branch is in a different repository than the current one. (Lukáš Lalinský, #144421)
· Make the first line of the manpage preamble a comment again. (David Futcher, #242106)
· Remove use of optional parameter in GSSAPI FTP support, since it breaks newer versions of Python-Kerberos. (Jelmer Vernooij)
· The autopacking logic will now always create a single new pack from all of the content which it deems is worth moving. This avoids the repack a single pack bug and should result in better packing overall. (John Arbash Meinel, #242510, #172644)
· Trivial documentation fix. (John Arbash Meinel, #270471)
· Explain revision/range identifiers. (Daniel Clemente)
· ``CommitBuilder.record_entry_contents`` returns one more element in its result tuple - an optional file system hash for the hash cache to use. (Robert Collins)
· ``dirstate.DirState.update_entry`` will now only calculate the sha1 of a file if it is likely to be needed in determining the output of iter_changes. (Robert Collins)
· The PackRepository, RepositoryPackCollection, NewPack classes have a slightly changed interface to support different index types; as a result other users of these classes need to supply the index types they want. (Robert Collins)
· ``bzrlib.tests.repository_implementations`` has been renamed to ``bzrlib.tests.per_repository`` so that we have a common structure (and it is shorter). (John Arbash Meinel, #239343)
· ``LocalTransport.abspath()`` now returns a drive letter if the transport has one, fixing numerous tests on Windows. (Mark Hammond)
· PreviewTree is now tested via intertree_implementations. (Aaron Bentley)
· The full test suite is passing again on OSX. (Guillermo Gonzalez, Vincent Ladeuil)
· The full test suite passes when run with ``-Eallow_debug``. (Andrew Bennetts)
· A new hook, ``Branch.open``, has been added, which is called when branch objects are opened. (Robert Collins)
· ``bzrlib.osutils._walkdirs_utf8`` has been refactored into common tree walking, and modular directory listing code to aid future performance optimisations and refactoring. (Robert Collins)
· ``bzrlib.trace.debug_memory`` can be used to get a quick memory dump in the middle of processing. It only reports memory if ``/proc/PID/status`` is available. (John Arbash Meinel)
· New method ``RevisionSpec.as_tree`` for representing the revision specifier as a revision tree object. (Lukáš Lalinský)
· New race-free method on MutableTree ``get_file_with_stat`` for use when generating stat cache results. (Robert Collins)
· New win32utils.get_local_appdata_location() provides access to a local directory for storing data. (Mark Hammond)
· To be compatible with python-2.6 a few new rules should be observed. message attribute cant be used anymore in exception classes, sha and md5 modules have been deprecated (use osutils.[md5|sha]), object__init__ and object.__new__ dont accept parameters anymore. (Vincent Ladeuil)
Bazaar VCS 1.8 RC1 / 1.7.1 Screenshot
Bazaar VCS 1.8 RC1 / 1.7.1 Keywords
Bookmark Bazaar VCS 1.8 RC1 / 1.7.1
Bazaar VCS 1.8 RC1 / 1.7.1 Copyright
Want to place your software product here?
Please contact us for consideration.
Contact WareSeeker.com