Thank for the replies ...
I think the idea from Ryan could be a solution ... but I am thinking in
the case that we have to modify the latest release version due to a
critical error, while some programmers have working copies with some
changes (perhaps on the same files that the modified ones on the latest
release) not commited to trunk. If we modify directly the latest version
to solve that critical error, then we could merge the changes into
trunk. But how the other programmers would be affected?
Respect to John's solution I am not sure to understand.
Since SVN::Notify::Mirror "Keep a mirrored working copy of a repository
path" I suppose we lost history of release versions. Isn't it?
I will investigate more SVN::Notify:Mirror since I am a bit lost about
its operation.
-----Mensaje original-----
De: John Peacock [mailto:john.peacock@havurah-software.org]
Enviado el: lunes, 01 de octubre de 2007 12:56
Para: Ryan Schmidt
CC: Gonzalez Diaz, Xoan; users@subversion.tigris.org
Asunto: Re: Repositories organization
Ryan Schmidt wrote:
> 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.
Actually, this is exactly what I do in SVN::Notify::Mirror, available
from CPAN:
http://search.cpan.org/search?query=SVN::Notify::Mirror
It is really very easy to configure a post-commit script (using
SVN::Notify::Config, also on CPAN) so that all development happens on
trunk,
with a test server kept in sync with all trunk commits. Then when a tag
is
created that matches a preconfigured regex, a completely different
production
server is updated (switched actually) to the latest tag.
HTH
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 1 15:41:05 2007