On Oct 1, 2007, at 03:25, Gonzalez Diaz, Xoan wrote:
> We're looking for the best organization of the repositories to suit
> our needs.
>
> By now, we're thinking to adopt the classical trunk, branches,
> tags plus one new directory called production.
>
> The motivation for this directory is that we need, at any time, be
> able to obtain, automatically, without reviewing the project
> history, the latest release version of our projects. We're thinking
> in having always in the HEAD of production the latest release
> version. Perhaps some programmers have commited several changes to
> trunk but in production is always the latest release version. In
> this way, in production there will be the sucesive release
> versions of our projects without intermediate commits that exist in
> trunk.
>
> I know the most common way is to have tags, but as far as I know,
> we can't obtain automatically the latest production version of our
> projects automatically from there.
>
>
>
> Since we are going to integrate Subversion with our own project
> management software we need to automate, the most we can, this
> interaction.
>
>
>
> I don't know if my explanation is clear enough (I have to improve
> my english) :-)
>
> What do you think about this? Are there another options?
I think it wouldn't be difficult to write a small script that gets
the name of the latest tag of a given project and checks it out. When
you want to release to production, you just make a new tag.
Optionally, if you want to use tags for things other than just
releasing to production, you could introduce a naming scheme where
e.g. every production tag starts with the string "prod-" and the
simple script knows to look for this.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 1 11:22:45 2007