[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Dir for latest stable release?

From: Nico Kadel-Garcia <nkadel_at_comcast.net>
Date: 2006-05-25 13:36:28 CEST

You seem to be mixing the concept of the "latest release" with the problem of "always get the same release for this build environment". You cannot hope to do both!

It's easy to set an "external" property for a Subversion directory, to always get a specifrc branch or tag of software at a specific revision number and download it locally. That's what I'd be inclined to do: if you want that to be updated regularly, then you'll need to pick some branch or tag and say "OK, project/tags/current will always be the current release", or to say "we will neightly generate a project/branches/project-data will be generated nightly, and people can refer to that".

  ----- Original Message -----
  From: Alex
  To: Alejandro Forero Cuervo
  Cc: users@subversion.tigris.org
  Sent: Thursday, May 25, 2006 6:29 AM
  Subject: Re: Dir for latest stable release?

  On 5/25/06, Alejandro Forero Cuervo <azul@bachue.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: users-unsubscribe@subversion.tigris.org
    For additional commands, e-mail: users-help@subversion.tigris.org

  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 <repos>/releases/stable/projectA)

Received on Thu May 25 13:37:45 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.