I think this discussion perfectly describes current situation :-) a) There is a large group of developers who use TW everyday, and don't want to use CVS or SVN because ... (see mails above for details). b) There is another group of developers who use CVS and don't want to use TW or SVN because ... (see mails above for details). c) There is another group of developers who use SVN and don't want to use TW or CVS because ... (see mails above for details). d) There are suggestions to consider other tools that support really distributed work, eg. arch/bazaar, monotone, svk, ...
Also there are requirements and restrictions: 1. All sources, that are available from CVS repository http://cvs.opensolaris.org/source/ are just a snapshot of files from TW workspace. The development is going on under TW, and there is no plan to change it right now, because ... (I suppose there are many reasons not to change it right now). 2. Technically it is easy to put TW workspace on web server and provide a special version of bringover (RemBo), that can get updates from web parent workspace. But the existing SCCS history is not supposed to be open. 3. External developers are supposed to send patches, so it does not really matter what code management system they use. The important thing is to have synchro- nization points: this patch is for revision 1.x, which is identical to delta 1.y IMHO if we will try to select an existing CMS and force everybody to use it - this will not help. It will more destroy than improve the community. We should not force CVS users to stop using CVS and to start using SVN or TW. We should not force SVN users to stop using SVN and to start using CVS or TW. We should not force TW users to stop using TW and to start using SVN or CVS. I think we should build bridges between these systems, and using these bridges we can get a new combined CMS, that will satisfy most part of developers. CVS and SVN repositories will be used to deliver the latest sources. TW will be used as a rich client, which allows to synchronize developer's workspace with a CVS or SVN repository, and also allows to create intermediate local deltas, and to have local child workspaces. Nikolay Molchanov P.S.: As I said, we already have a TW-CVS bridge, and it can be easy modified to work with SVN, or with any other CMS, which provides command line utilities for basic actions. So if we provide these bridges and TW binaries, external developers will be able to use the same CMS as used by internal developers, or use CVS or SVN directly. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
