There are private branches, and there are private branches. In the context that you describe, the integration branch is private to the builders who gate the release of the product. Jim refers instead to a branch that's private to the developer performing the work.
Branches are a general tool for isolating work. The nature of that work can vary from user to user. --- Forwarded mail from [EMAIL PROTECTED] I have a question on Jim's statement "Private branches are never considered candidates for releases or for builds". I have always understood that a company would always release from a private branch. This assumes when a release process begins a release branch is created and final testing begins on the release branch's code while development for succeeding releases continue on the trunk. Any problems found on the release branch are fixed and retested. Only approved bug fixes are checked into the release branch. When the release branch is stable the release is made from the branch and all changes are merged into the trunk. Is this concept incorrect or is there a difference between within cvs between a private branch and a non-import branch? --- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
