|
From: | Gyetvan Andras |
Subject: | How to proceed ? |
Date: | Fri, 21 Mar 2003 07:03:51 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312 |
Hi all !It is not exactly a CVS issue, but... So our team will release the project's first version (1.1) soon. We will continue to develop to add 1.2 functionality to the code. The 1.1 version will be put in field, so we expect a few modification in 1.1 (small bugfixes, minor modifications). With CVS I can do a branch for 1.1 source and maintain the merging between 1.1 and 1.2 (if needed).
My questions are the following :- what is the best practice to do this ? Create a new module to 1.2 and maintain the code merging manually between versions ? Create a branch for 1.1 (or 1.2) to maintain the same.
- if I decide to create a new module for 1.2 instead of a branch, is there a possibility to diff, merge between modules ?
- is there a way to specify automatically the name of the directory where CVS will checkout the source ? I mean, if I have a module in the repository named "app.code". This module has a branch called "rev-1-1". It vould be fine when I checkout the "rev-1-1" branch, then CVS put the source into a directory called "app.code.rev-1-1" (or something different than "app.code") instead of "app.code".
Thanks, Andras
[Prev in Thread] | Current Thread | [Next in Thread] |