| SCM feature: | Bazaar |
Add to comparison:
+CVS +AccuRev +Aegis +AllChange +Arch +BitKeeper +ClearCase +CM+ +CMSynergy +Co-Op +Darcs +Git +LibreSource Synchronizer +Mercurial +Monotone +OpenCM +Perforce +PureCM +SourceAnywhere +Subversion +Superversion +Surround SCM +svk +Team Foundation Server +Vesta +Visual SourceSafe |
|---|---|---|
|
Atomic Commits |
Yes. Commits are atomic. | |
|
Files and Directories Moves or Renames |
Yes. Renames are supported for files and directories. | |
|
Intelligent Merging after Moves or Renames |
Yes. Renames are intelligent. | |
|
File and Directories Copies |
No. Copies are not supported. | |
|
Remote Repository Replication |
Yes. | |
|
Propagating Changes to Parent Repositories |
Yes. | |
|
Repository Permissions |
Basic access control can be implemented through a contributed hook script. ACL support for the Bazaar server is planned. | |
|
Changesets' Support |
Yes. Changesets are supported. | |
|
Tracking Line-wise File History |
Yes. (bzr annotate). | |
|
Ability to Work only on One Directory of the Repository |
For checkouts: No. For checkins: Yes. | |
|
Tracking Uncommited Changes |
Yes, using "bzr diff". | |
|
Per-File Commit Messages |
With respect to pure Bazaar: No. At least one plugin (bzr-gtk) supports it though. | |
|
Documentation |
Excellent. Apart from online help in the command line client there exist tutorials, a reference card ("Quick Start Guide"), several full fledged guides and references, and documents on specialized topics, such as migration from other VCS systems and different workflows. The documentation comes in html and plain-text formats. The API of the underlying library is fully documented. In the UI design of the command line client special attention was paid to make it easy to get started with Bazaar. | |
|
Ease of Deployment |
Very easy. Bazaar has an installer for MS Windows and packages for some major Linux distributions, FreeBSD, and Mac OS X. The dependencies for manual installation are listed on the Bazaar website. | |
|
Command Set |
Tries to follow CVS conventions, but deviates where there is a different design. | |
|
Networking Support |
Excellent. Works natively over HTTP (read-only), FTP and SFTP without having Bazaar installed at the remote end. Works over HTTP, SSH and a custom protocol when talking to a remote Bazaar server. Supports RSYNC and WebDAV (experimental) through plugins. | |
|
Portability |
Works on MS Windows, Linux, Mac OS X, FreeBSD, UNIX, and basically on any system that has a recent Python port. With case-insensitive file systems there are some issues that can be avoided by using a graphical frontend. On MS Windows there is a plugin to support tracking of symlinks even if they are not supported natively by the file system. | |
|
Web Interface |
Yes, several: Loggerhead, Webserve, Bzrweb, and Trac. | |
|
Availability of Graphical User-Interfaces. |
There are several graphical frontends in development, see the Bazaar Plugins page and the Third-party Tools page. Notable are QBzr (Qt) and bzr-gtk (GTK+), which can be considered beta quality. Work is also being done on integrating Bazaar with Windows Explorer, Eclipse, Nautilus, and Meld. | |
|
Information taken from Better SCM Initiative website by Shlomi Fish (shlomif@iglu.org.il). Reorganized for usability by Alexey Mahotkin (Version Control Blog) in 2008. |
|