Re: question: should we move CVS?
Michael Flanagan <[email protected]>
| Newsgroups | gmane.comp.windows.devel.netwindows |
|---|---|
| Message-ID | <[email protected]> |
Alex Russell wrote: > Hey Everyone, > > We've been using SourceForge for a long time now to provide us with some > important services, with CVS being the most important of these. > > With our new server comming on line this weekend or next week, I'd like to get > your opinion of whether or not you think we should stay with SourceForge as > our CVS provider? I would support a transition to a project managed cvs server. > MDA would like for us to move to Perforce with burstlib, > and I'm supportive of that move (which we will host, since SF doesn't provide > p4 services). I don't want to see netWindows move to Perforce as our SCM system. > In terms of administration complexity, having to submit change > requests every time I'd like to change the name of a file or directory in CVS > without loosing version history is mighty annoying. The only aspect of code changes that I'm active in is with the stuff in winScripts/widgets. I havn't seen anything moved in there and am happy with the way it is. This is a non issue for me. > Also, the recent > anonymous checkout changes (now delayed from HEAD by ~12 hrs) make me very > unhappy with their service. While I can't really complain about something > they are providing for free, I can fix things I don't like. I personally know what a pita it is with SF's 12 hour delay w/ checkins to head. This and their apparent lag with mail sent to cvsnotify are my primary motivators to see us using our own server. I would also really like to see Bonsai set up as well if we're going to run our own server. I can see that being a handy thing to have up and running. If we move though, I don't want to see us remove the project from SF. People go to SF to search for active projects (say DHTML toolkits ;). I think it would still be benefiscial to update the code in the SF repository and keep the packaged release versions of the NW framework available for downloads. We can always put references on the SF site that point out our own managed server. > But I'm not going to move things unless the rest of the group thinks it's a > good idea. > > To migrate or not to migrate, that is the question. > So what say you? I'm in favour of the move. _______________________________________________ The netWindows developers list: [email protected] http://netwindows.org/mailman/listinfo/devel_netwindows.org