Jesse Tilly
Track: Java
Date: Wednesday, July 24
Time: 5:15pm - 6:00pm
Location: Marina III
They're all out there and they want your money. Names and products of
popular configuration management tools include StarBase's StarTeam,
Merant's PVCS, IBM's CMVC, and TeamPlay's TeamTrack. Contrary to
popular belief, just because these products aren't open source, they
do, in fact, work. In fact they work well. The solution they deliver
is worth a lot of money (maybe not what they're charging, but a lot).
Now, you may be thinking, "But my software is free. I want what these
tools offer, but I just can't justify paying the money!" GOOD! At
least you're thinking.
The unfortunate part is that many people in the open source community
don't even get to the point of asking that question. The reason the
proprietary tools work is that they enforce a good development
process with their technology. They solve the problem of
issue-to-revision maintenance and couple that with release
management. By definition, the combination of issue maintenance,
source control and release management is configuration management.
Bugzilla, Ant, and CVS are good technologies in their own right, and
they do their individual jobs very well. But, these programs, by
themselves, don't enforce a configuration management process.
This presentation will give an overview of a configuration process
that works. No theory is involved, just battle-tested facts. Those
other systems work because they're built on time-tested methodologies
that manage projects well. The same can be said with this
methodology.it's just that -this- particular implementation costs a
lot less.
Download presentation file
