Philippe Bossut wrote: > Sorry to be thick but the semantic difference between "tags" and > "branches" is really lost on me, especially using SVN since there's no > real differences between the 2... > > So, why can't we have: > chandler/ > branches/ > 0.6/ > release-0.6/ > > IOW, what do we gain by adding one extra bifurcation in the tree?
You would have fewer subdirectories under branches/. And at least to me, a branch is a living thing, not a snapshot in time. > I infer from the threads that "tags" are "non modifiable" but is that > something actively enforced or just a convention we decided to adopt? In CVS a tag is real, but Subversion has no such thing. In practice, most software projects have specific releases, where you want to be able to recreate that specific release later if you needed to. The traditional way is to "tag" the source repository so that the specific versions of sources used for the release is clear. Clearly it is a requirement that whatever that tag is that it won't change over time. Some source control systems enforce this automatically, while others must rely on conventions or hacks. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
