BK/Pro is a scalable configuration management system that runs on
most Linux and Unix varieties, Windows 98/NT/W2K/ME/XP.
Some of the features which make BK/Pro stand out in the crowded
SCM market are:
-
Inherently reliable and scalable through replication
-
Change sets provide reproducibility, accountability, and aid in
debugging
-
Powerful GUI tools shorten development time and remove human error
-
Excellent merging tools save engineering time and increase
productivity
-
Repositories as branches allows controlled development
-
Geographically distributed development works as well as local
development
-
Disconnected operation with no loss of functionality
-
Compressed repositories reduce disk space and increase performance
-
Excellent file rename support allows flexibility as projects grow
-
Scalable to 1000's of developers
-
Multi-protocol (FS/RSH/SSH/HTTP/BKD/SMTP) connectivity: work how
and where you want
BK/Pro is a scalable configuration management system, supporting
globally distributed development, disconnected operation,
compressed repositories, change sets, and repositories as
branches.
Distributed means that every developer gets their own personal
repository, complete with revision history, and the tool handles
moving changes between repositories.
SSH, RSH, BKD, HTTP, and/or SMTP can all be used as communication
transports between repositories;
or, if both are local, the system just uses the file system.
For example, this updates from a remote system to a local file
system using ssh:
 |
bk pull bitmover.com:/home/bk/bk-3.0.x
|
Change sets are a formalization of a patch file, i.e., one or more
changes to one or more files.
Change sets also provide built-in configuration management - the
creation of a change set saves the entire state of your
repository, both what changed and what didn't, in less than a
second.
Other features: file names are revisioned and propagated just like
contents;
graphical interfaces are provided for merging, browsing, and
creating changes;
changes are logged to a private or public change server for
centralized tracking of work;
bug tracking is in the works and will be integrated.