|
|
|
|
Sun Teamware
|
|
"We migrated from Teamware to BitKeeper and saved thousands of
hours by doing so.
With BitKeeper and changesets, we could easily check previous
versions of our source base and find the entry point of a
regression.
Doing the same thing in Teamware forced us to manually sift though
weeks of changes by hand." -- Bill Moore, 3pardata
|
|
-
BitKeeper has changesets, Teamware does not.
Changesets guarantee that the tree is reproducible, Teamware can
not.
-
BitKeeper rollback always works, Teamware rollback rarely works.
-
BitKeeper can import/export diff-style patches for the entire
tree.
-
Many of the BitKeeper graphical tools are substantially better
than the ones in TeamWare.
The BitKeeper file merge is easier to use, works better, and
merges faster.
Citool is a graphical checkin tool which reduces human errors
(missed files) and produces better checkin comments.
There are no analogous tools in TeamWare for citool, difftool,
renametool, csettool or helptool.
-
All of your TeamWare knowledge transfers over -- conceptually,
BitKeeper is similar to TeamWare.
-
BitKeeper has better event triggers (more fine grained control).
-
BitKeeper has much better rename support for files and
directories.
Renames in Teamware are not an undo-able event.
-
BitKeeper uses much less bandwidth when synchronizing with remote
repositories over the WAN or dial-up (null updates take less than
a second over an SSH connection regardless of repository size).
-
BitKeeper has compressed repositories.
In one import of 19 years of Teamware managed data the size of the
resulting repository was slightly more than 2 times the size of
the checked out files.
In other words, BitKeeper was able to store 19 years of changes in
the same space as the flat, checked out files.
No other SCM system comes close.
| |
|
Home 
Comparisons