This is more of a generalist question to validate my
proposal for a new repository layout - I hope that it
is not misplaced.
I have installed Subversion 1.2.3 using Apache 2.0-
WebDAV as the repository/server.
I am working on a project that is a relatively complex
system integration exercise involving a number of
different vendors' products, and also some custom
bespoke development. In some cases third party vendor
products require customisations. The architecture of
the project is an n-tier web based system.
We want to be able to store vendor releases in the
repository, so I have proposed having separate
repositories for each vendor, and using the 'tagging'
concept described in the Subversion manual to create
immutable versioned releases.
All customisations and bespoke development work will
go into a separate repository (call it CUSTOM for
Where there are custom developed components for a
third party product I am proposing that an SVN
external definition should be used to reference, and
incorporate core product artefacts. This would enable
a local working copy to contain a hybrid of core
product artefacts and also customisations (the idea
being that a single deployable unit could be built for
One issue that I still have to resolve is the fact
that there are a number of these components that I
have described above that need to be baselined into a
single coherent release.
One strategy that I came up with was the concept of an
integration project within the CUSTOM repository. At
first I was thinking of using SVN external dependcies
yet again to point to the various other projects in
the CUSTOM repository. However now I am not so sure
whether this is goin a bit over the top, and it would
be adequate to just perform a copy of each of the
projects into the integration project.
I would appreciate any tips/pointers that any people
Thanks and regards,
Do you Yahoo!?
The New Yahoo! Movies: Check out the Latest Trailers, Premiere Photos and full Actor Database.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Oct 12 00:14:36 2005