|
6
by mbp at sourcefrog
import all docs from arch |
1 |
Compared to Sun Teamware |
2 |
************************ |
|
3 |
||
4 |
(**note**: I have never used Sun Teamware, so this document is just |
|
5 |
based on public documentation and information from other people. |
|
6 |
Corrections would be appreciated.) |
|
7 |
||
8 |
http://docs.sun.com/app/docs/doc/806-3573 |
|
9 |
||
10 |
Needless to say bazaar-ng is currently far less mature, and some of |
|
11 |
the advantages listed below don't work in the current pre-1.0 code. |
|
12 |
But they are accounted for in the design. |
|
13 |
||
14 |
TeamWare has file locking. Distributed systems can't easily support |
|
15 |
file locking because you can't prevent people diverging. But perhaps |
|
16 |
we can have scripts or a higher-level tool to communicate that changes |
|
17 |
to a particular file are in train. (One possibility: there is a |
|
18 |
development branch where that file has been changed, but not yet |
|
19 |
checked in. Or if Bob can see Alice's work area, he can see that a |
|
20 |
particular file has been fetched read/write.) |
|
21 |
||
22 |
parent/child workspaces. |
|
23 |
||
24 |
Advantages of bazaar-ng: |
|
25 |
||
26 |
* Free / open source software |
|
27 |
||
28 |
* Prior tree revisions are always exactly reproducible (atomic |
|
29 |
changesets, etc) |
|
30 |
||
31 |
* Can get whole-tree diff |
|
32 |
||
33 |
* Versioned, mergeable renames. |
|
34 |