A "branch" will eventually reach an end-of-life where it can be removed
(i.e. when everything is merged or over and done with).
A "tag" will never change under any circumstances.
A "release" will change under certain circumstances. This is actually
the reason there were two tags earlier, one before any such changes and
one after. I.e. if there is some small problem that needs to be fixed in
the release. As an example, I could have the version changed from PRE-XX
to XX for each release only in the release and never in trunk. In trunk
it could go from PRE-XX to PRE-YY directly. Releases never reach
end-of-life. Once we have made release 0.21.3, release 0.21.3 will
always be release 0.21.3.
/Linus
> -----Original Message-----
> From: Tom Morris [mailto:[EMAIL PROTECTED]
> Sent: den 23 september 2006 22:57
> To: [email protected]
> Subject: RE: [argouml-dev] Structure in the subversion repository
>
> > Each release will get a copy in the releases directory.
> > It works a something in between branches and tags but it
> > is only updated while making a release and after the release
> > never again.
>
> Something which gets set at a particular instant in time sounds like a
tag
> to me.
>
> How do the semantics of a "release" differ from those of a "tag" or
> "branch"?
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
