alternate SCM. Was Re: [Asterisk-Dev] Linux leaves Bitkeeper: quite a dustup

[Steven Critchfield]

On Tue, 2005-04-12 at 14:15 -0700, Mike Taht wrote:
> > Good binary file handling (for handling sounds, iaxy firmware)

While a good idea, maybe we need to think about removing sounds from CVS
or other SCM and make it a nice rsync repository or tarball. This is
actually a very weak maybe.

> > Tagging & branching that can be understood by non-CVS gurus
> > Proper rename/remove support
> > Good merge support
> > Web interface for browsing source code repository

How often is this actually used? Nice addition, but maybe it could be
prioritized down a bit. 

> > Documentation (esp. a "new-cool-scm-tool for CVS converts" document)
> 
> Emailed commit logs

While important, this might not be very easy or very usable in a
distributed SCM environment. For instance, there may be branches you
don't care anything about, but having a central email distribution would
not be overly helpful. 

Then again, it is just an email filter away from not caring. 

Maybe that could be how we determine what is available to Digium as
disclaimed code. If you use the Digium sponsored commit log list, any
commits that are sent are available to Digium. 


> Interface to mantis bug tracker

Are we truly tied to Mantis? I haven't used it much, but didn't think it
was very useful.

I like trac, but I think it is too tightly coupled with SVN to be used
with another SCM. Specifically what I like about trac is the ability to
mark tickets as part of a milestone and work towards clearing all open
tickets in a milestone for release. Then again, I haven't seen any way
in trac to easily manage multiple trees. 

-- 
Steven Critchfield <critch at basesys.com>