Jim Hyslop a écrit :
There really is no "correct" way. Some approaches are better than
others, when specific results are required.
Ok.
One important factor that will affect your decision is whether or not
versions will be intermixed. I.e. will you be working on versions 1.3,
1.4 and 1.5 at the same time? If so, then you will need to post more
detailed information about your release strategy.
The versions are not so much intermixed and I can manage the changes
with few merge operations.
On the other hand, if version X.Y does not begin until version X.(Y-1)
is (mostly) complete, then your release and version management strategy
is much easier: keep all new version development on the trunk. When you
are ready to begin working on version X.Y, create a branch and move
development of X.(Y-1) onto that branch.
That's it. It's the way we work here.
I wondered whether there were no performances problems working with a
version wich is a branch of a branch of a branch of a branch etc.
How can V3 "replace" head ?
Search the archives for various discussions on this topic (there was one
within the last two weeks). See the auto-appended link for the archives.
Ok, thank you very much.
JL
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
