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 firstname.lastname@example.org.
cvsnt-bounces at cvsnt.org wrote on 23/01/2007 16:53:32: > > From: Dries Feys > > And a second question : is it actually possible to go to > > version 2.x ? I > > don't see an way to "finalise" version 1.x and starting the > > 2.x branch. > > You make a branch and call it myproduct_2_0 (or you branch > myproduct_1_23 for maintenance and do the 2.0 development on HEAD, which > would probably be my choice). That's indeed a nice idea, which I'll keep in mind for my development (we integrated the tortoise-cvs-client into our Progress development environment) (Are there actually still other people around here using cvs to maintain their progress / openedge source files? You probably don't want to "finalise" > anything in case you need to go back and fix a showstopper on 1.23. Indeed, I wouldn't, but I was just wondering the possibility. > > If you're currently reading anything into CVS's internal revision > numbers for files, don't. They're CVS-internal magic numbers and should > have nothing to do with your organisation's product revisions, even if > both happen to have the same n.nn.nn structure. If you need to > represent your organisation's product revisions, use tag and branch > labels. I started to realise that when reading the cvs manual, just wanted to be sure :-) Thanks a lot!! **** DISCLAIMER **** <A HREF="http://www.tvh.be/newen/pages/emaildisclaimer.html"> http://www.tvh.be/newen/pages/emaildisclaimer.html </A> "This message is delivered to all addressees subject to the conditions set forth in the attached disclaimer, which is an integral part of this message."