Version 3 of Choice of SCM for the Tcl/Tk core

Updated 2003-07-16 15:23:52

Maintenance and development of Tcl's core is itself a substantial project, one which certainly benefits from disciplined use of SCM tools. As of July 2003, SourceForge has hosted this work (for several years?). There's sentiment to relocate Tcl's home to another technology and another site, because [enumerate reasons]. As CL understands matters, BitKeeper and CVSTrac are under consideration.

PT - Bugzilla provides an extremely good bug tracking system that is highly configurable and significantly better than the SourceForge trackers.

I don't see much need to move away from a CVS based version control system. Bitkeeper is more efficient but imposes a barier to new contributors (ie: it costs). The Tcl code base really isn't large enough to demand the increased efficiency over CVS.