Hi!
"Jung , Dr. Christoph" wrote:
> sorry if I missed substantial decisions on jboss-devel, but I would like to
> take the opportunity to convince you of an increased use of cvs-tags and
> branches ....
>
> IMHO, branching and tagging allows us to easily (i.e., not via bloody
> e-mail) share and coordinate coden changes that are not already bullet-proof
> at an early stage of development --- without polluting the current
> "mainline".
>
> We at infor use a model where the "official" source release (that serves as
> the basis for developing any extensions) has no tag and lies on the root
> branch. I.e., if someone simply checks out the module without additional
> revision annotations, he automatically receives this release.
>
> Branches and symbolic tags are used to manage tiny and quite local
> sub-projects (our devel cycles for features are typically 1-2 weeks long).
> An example would be that I would start a new branch in the
> org/ejb/deployment package named "generalApplicationDeployment".
>
> Everybody interested/participating in this project could then checkout the
> directory (or the root) using the sticky tag name for the branch with the
> option "If no matching revision is found, use the most recent one", e.g.,
> from WinCVS (sorry, don�t know the commandline switch ...) ...
>
> When the sub-project is finished or has provided a bug-fix for some problem
> in the mainline that should be incorporated ASAP, the project manager is
> responsible for merging the branch(the fix) into the mainline ...
>
> Any opinions about this proposal?
I'm all for it.
How do I do it? (Using WinCVS here)
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
