[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ximbiot FAQ wiki & a new FAQ

From: Todd Denniston
Subject: ximbiot FAQ wiki & a new FAQ
Date: Fri, 21 Oct 2005 13:33:40 -0500

 I am not greatly into editing wiki's so I decided to follow the advice at
and post my suggestions here.
I also noted in that section both of the text indicators
"info-cvs@nongnu.org" have url's pointing at
perhaps the text indicators should be "bug-cvs@nongnu.org"?

1) The links in
perhaps should point to 
as these copies still exist.

Also I think references to 
would be good general purpose CM links for best practices.

2) In Larry's answer to "Re: Best practices for initial import and
versioning" this morning, I recognized a question that I think has become
reasonably FAQ.

I think it belongs either under 
"3 General Repository Administration" or "8 Other Questions and Unsorted
Questions with answers"

Q. What is the best branching practice to use with CVS?
A. It is generally said on the mailing list that "it less painful if
development is done on the trunk and releases are branched for maintenance. 
This way, the merge-backs are fewer when main development is going on.  You
will have to merge fixes from the maintenance branches to the main trunk
after a release but this is less of a headache because these are generally
smaller and easier to manage than merging all the changes that would be made
on a development branch." [Russ Sherk] 

But the correct branching practice also depends on the way you want to
development, so you should also consult documentation that discusses code
management branching in a general way, such as "Streamed Lines: Branching
Patterns for Parallel Software Development"

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]