on
Sent: 05 April 2009 16:28
To: opensim-dev@lists.berlios.de
Subject: Re: [Opensim-dev] On Revisions, tags and branches
> However, given that this means source releases magically appear
> shortly after tags, I'd recommend just tagging off 0.6.4.1-release,
> 0.6.4.2-release, etc
> However, given that this means source releases magically appear
> shortly after tags, I'd recommend just tagging off 0.6.4.1-release,
> 0.6.4.2-release, etc when fixes go in that should release to the world.
Good call, Sean; I think that should be how we do it. At least, we could tag it
on
@lists.berlios.de
Subject: Re: [Opensim-dev] On Revisions, tags and branches
Stefan Andersson wrote:
> Now on to tags - trunk, branches and tags are really all one thing: paths.
The only real difference is by convention: there is a certain path called
/trunk that serves a certain purpose, nemaly to
Great summary and a really useful addition to build. ++
-tommi
___
Opensim-dev mailing list
Opensim-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/opensim-dev
Stefan Andersson wrote:
> Now on to tags - trunk, branches and tags are really all one thing: paths.
> The only real difference is by convention: there is a certain path called
> /trunk that serves a certain purpose, nemaly to be the focal point for
> developers. There is a certain name used for
Esteemed colleagues,
a couple of good-to-know points about SVN versioning;
In an SVN repo, the 'revision' is a discrete version of the software. But; the
revision _number_ is _not_ an indication of sequential functional increment.
Revisions are based on the revision before it, but tha
