Re: Dir for latest stable release?
On 5/25/06, Alejandro Forero Cuervo <email@example.com> wrote:
> If I make a directory for a project with the standard layout, —trunk,
> branches and tags—, where can I place a directory that will always
> contain the latest release? Just like trunk will always contain the
> latest development code, I was looking for some standard directory
> that will always contain the latest stable release.
> This is important in part because I want to make it possible to write
> scripts that find the latest stable releases for all the modules
> inside a repository (that has multiple projects) without having to add
> intelligence to parse version numbers (for the files in the tags
> directory) to them. So I would standarize on always using a certain
> directory under each project's root.
> I'm quite aware that I can use whatever I want, but I'm looking for
> suggestions to see if there is some sort of standard practice for
> this. I looked at the Version Control with Subversion book but
> couldn't find anything on this. branches/stable doesn't look right,
> since no development is expected to take place on that "branch".
> Although tags/stable would feel slightly better, it doesn't look right
> neither, since the contents of that tag would be changing over time
> (whenever a new release is made).
> What would you recommend?
> To unsubscribe, e-mail: firstname.lastname@example.org
> For additional commands, e-mail: email@example.com
How about creating a releases directory where you always point to the most
recent/stable release tag of your project. Then all your scripts could refer
to <repos>/releases/stable/projectA for the most recent release.
ProjectA (which is 'svn cp <repos>/projectA/tags/Release1.0
Received on Thu May 25 12:31:36 2006
This is an archived mail posted to the Subversion Users