There are diverse solutions of the companies:
perforce (perforce)
serena (dimensions, version manager)
Or opensource:
Subversion
cvs
combined with the client Tortioise.
Bug management can be done with mantis.
There are some methods to integrate cvs/subversion with mantis:
http://www.mkgnu.net/?q=scmbug
http://alt-tag.com/blog/archives/2006/11/integrating-mantis-and-subversion/ (to be sure this is save I copied it to
Integration Mantis Subversion )
Allthough there are in many companies already solutions implemented for incident management, problem management, change management, release management and it might be good to consider to integrate SCM with the existing systems, because introducing another system like mantis might cause overlap in functionality and that is not very efficient to have 2 methods for same functionality and you have to maintain 2 software solutions.
SUBVERSION EVALUATION
Compared to version manager and cvs is subversion great in most aspects.
disadvantages:
a. the performance could be better
b. integration with bugtrackers are not standard
c. integration with ms visual basic scripts within word templates are not yet known. An option is ofcourse to put the whole template/library as one file in the release, but then it is much harder to detect which source lines are changed because those are binary files instead of sourcefiles.
d. integration with bugtrackers (mantis, bugzilla, ...), helpdesk applications, .... are much
Tips:
– good preparation before your start saves you lot of maintenance issues
– subversion had no standard promotion model, but with the right configuration it can be created very easily and is much more flexible, because you can enhance it with adding easily logfiles of the installation and with a simple scripts you are able to promote it quickly too.
– integration with bugtrackers (mantis, bugzilla, ...), helpdesk applications, .... are possible but don't underestimate the effort which is need to realise this.
