On Thu, Jan 11, 2007 at 08:35:43PM -0800, Doug Hardie wrote:
On Jan 11, 2007, at 18:28, Norberto Meijome wrote:
On Thu, 11 Jan 2007 11:35:38 -0800
Doug Hardie [EMAIL PROTECTED] wrote:
Any suggestions on these approaches will be appreciated.
Thanks,
I suggest you read the CVS Red
I have a medium sized application where the source is all in a CVS
repository. Basically it works great as I am able to retrieve any
previous version of a module when needed. Most of the changes to the
application are quickly resolved, CVS committed and the production
system updated in
On 1/11/07, Doug Hardie [EMAIL PROTECTED] wrote:
one for the new development or the other way around. Will it be
easier to merge the fixes to the production branch back in to the new
system later or should those fixes be made to both branches at the
same time? Any suggestions on these
branch and keep the main one for the new development or the
other way around.
There are two 'models' of work you can use with CVS:
* The mainline model.
* The promotion model.
In the mainline model, all development happens in the HEAD branch
of CVS, and when you are about to release
afaik, branching off for the minor changes would be thest way to go. so you
could merge back these changes into main line easily. that is the way normal
devel cycle
or you could establish minor and major and merge them upon completion.
On 1/11/07, Doug Hardie [EMAIL PROTECTED] wrote:
I have a
On Thu, 11 Jan 2007 11:35:38 -0800
Doug Hardie [EMAIL PROTECTED] wrote:
Any suggestions on these approaches will be appreciated.
Thanks,
I suggest you read the CVS Red book, in particular the section on branch
management and merging.
http://cvsbook.red-bean.com/cvsbook.html
I agree with
On Jan 11, 2007, at 18:28, Norberto Meijome wrote:
On Thu, 11 Jan 2007 11:35:38 -0800
Doug Hardie [EMAIL PROTECTED] wrote:
Any suggestions on these approaches will be appreciated.
Thanks,
I suggest you read the CVS Red book, in particular the section on
branch
management and merging.
