Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> I agree, but what about develpers' sandboxes? (please read > http://www.cvsnt.org/wiki/Upgrading) Hmm, I don't know what should be the reason for that recommendation.... neither the clients nor the sandboxes are affected by the upgrade at all... > I'm unnable to force 70 developers to commit their changes at the same time. > So I will migrate them to the new server in a by project (module) basis. ?? I thought the repository was to remain on the same machine? Or do your developers have got their sandboxes on network shares? If so, stop doing that yesterday. Look here: http://cvsgui.sf.net/newfaq.htm#remoteSandbox . I'm probably grossly misunderstanding you.... > This way each development group can plan a different migration date that > better suits their cronograms. A server upgrade usually isn't something that the clients and especially their working copies are affected by at all. Nothing changes at that end. The repository format stays the same and the interface to access it stays the same as well. The only thing that changes are the server binaries which after the update will support a few more bells and whistles than before. That's all. Hope this helps. P.S.: Note that the cvsnt-list uses a somewhat uncommon reply-policy. Simple replies will go only to the original sender. In order to reply to the list you have to hit ReplyAll and then remove the original sender's address again. Alternatively use the NNTP relay at news://news.cvsnt.org/support.cvsnt . Oliver ---- ------------------ JID: ogiesen at jabber.org ICQ: 18777742 (http://wwp.icq.com/18777742) ----- Original Message ----- From: "Luiz Daniel Lapolla" <luiz.lapolla at sfw.com.br> To: "Oliver Giesen" <ogware at gmx.net> Sent: Thursday, April 01, 2004 8:20 PM Subject: Re: Two CVSNT servers on same machine > I agree, but what about develpers' sandboxes? (please read > http://www.cvsnt.org/wiki/Upgrading) > > I'm unnable to force 70 developers to commit their changes at the same time. > So I will migrate them to the new server in a by project (module) basis. > This way each development group can plan a different migration date that > better suits their cronograms. > > Thanks > Daniel > > ----- Original Message ----- > From: "Oliver Giesen" <ogware at gmx.net> > Newsgroups: support.cvsnt > Sent: Thursday, April 01, 2004 12:13 PM > Subject: Re: Two CVSNT servers on same machine > > > > Daniel Lapolla wrote: > > > Can two CVSNT servers coexist on the same machine? I'm planning an > upgrade > > > from 1.11.1.3 to 2.0.34, but want to migrate the modules one at a time. > This > > > way most of developers will be using 1.11.1.3 and the others will be > using > > > 2.0.34 until all the modules are migrated to 2.0.34. > > > > Just out of interest: What exactly do you want to migrate? No changes > > have to be made to the repository files at all for the upgrade. Just > > shut down the old server, upgrade and start up the new server. That's it. > > > > Cheers, > > > > -- > > Oliver > > ---- ------------------ > > JID: ogiesen at jabber.org > > ICQ: 18777742 (http://wwp.icq.com/18777742) > >