Sérgio Paulo Barbosa wrote:
> It’s the first time I’m posting an e-mail in this mailing list.
> I work in a software enterprise, in Portugal, and I belong to a work
> group that is working in a project that pretends to define an automatic
> process to install and control software.
> My task is to define and document an SVN repository to keep C source code.
> Does anyone know an example or typical structure to use, that I can
> study and start from, instead of creating the wheel again?
> Documentation about this theme can also help.
There are comments about layout here: http://svnbook.red-bean.com/.
The main thing you need for release management is to come up with a naming
convention for the tags (and branches, if you branch for each release version).
You also need to decide whether you'll have a separate repostory per project and
whether you'll keep a 'clean' trunk by making branches for changes or do active
development on the trunk with branches near each release. Or, with an automated
wrapper to control release revisions, you could probably make release tags
directly from the trunk and only branch if maintenance updates had to be done
for an earlier release. By the way, you might like Hudson:
http://wiki.hudson-ci.org/display/HUDSON/Meet+Hudson to automate builds - and it
has plugins for other tasks like deployment.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-20 14:59:22 CEST