Re: question: should we move CVS?

> I don't want to see netWindows move to Perforce as our SCM system.

because it is proprietary, because it has no distributed repository support,
or for some other reason?

it is free as in beer for open source projects, FYI.

while i've got strong feelings about SCM (i was principal engineer at
Rational in years gone by), i'm not actually all that fired up about
the particular one NW/burst uses, as i expect that the nature of the
usage we'll put to it (basically, not much above rsync) means that
most of CVS's inadequacies won't be too punitive.

it is certainly possible to use multiple SCM systems and gateway
among them. Though for that to fly you want the most featureful
SCM system to have the master repository.
Only committers would need to know anything but CVS.

-mda



_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org