Repositories organization

Hi again,

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?

Thanks in advance,

Xoan

 Xoan González Díaz

 Área de Arquitectura

 E-mail: g2485 (at) caixagalicia.es <mailto:%20g2485@caixagalicia.es>

 xoan.gonzalez (at) tecnocom.es <mailto:xoan.gonzalez@tecnocom.es>