>What tools and support does Sun currently provide in terms of software
>configuration management? I have used several CM tools in the past
>(i.e., RCS, SCCS, etc.) and am wondering what the current status of
Quote:>The initial project requirement is to manage the development of a small
>project of 100k-200K lines of code with 6-10 developers. However, it is
>anticipated that CM will be used for a variety of projects.
>Any information would be apprecicated.
Summary: no commercial SW package offered, but rather the knowledge
plus free software...
Sorry, I cannot offer you a shrink-wrapped product here, but the
following may nevertheless be of use to you or others.
We have run a number of large fixed price projects during the last
years and we realised how important a good configuration management
environment is. The first thing here to get right is not buying a
tool, but the systematics behind CM.
We succeeded in developing a good CM method and added a home-brewn
suite of CM tools to make the method more usable in daily life. The
*tool* is not a commercial product, so please do not accuse me of
commercial adverti*ts here :-). What we normally do is advise
our customers (Ok, *now* you could accuse me) and help them to set
up a CM environment (incl. organisational aspects etc.) and give
away the toolkit for free.
Briefly, the tool (and hence the method) provides the following (of
course besides version registration and archiving):
- runs on SunOS 4.1.x, HP-UX 7 and 8, SGI IRIX 4, Linux 99pl12 (!)
and -I think- Solaris 2.1.
- allows you to create baselines (BLs). A BL defines a specific
version of the whole system or of a sub-system.
- a set of make rules to allow you to completely automatically
build any specified version of any (sub) system at any time from
the CM archive. In one occasion we even supported multiple
target platforms. BL's are really powerful: you can say (type, in
fact) things like:
- run simple metrics e.g. to count approved components
Anyway, contact me if you want to know more.
Regards, Remco Bruijne
#include <stddisclaimer.h> This might not be the view of my employer.