On 4/6/07, Hendrik Schober <SpamTrap@gmx.de> wrote:
> > If you can modify shared code during release of any of the sharing
> > project, I believe you will see many other problems that have nothing
> > to do with the version control software.
I've worked in two environments that did this. Both ended up changing
to a better managed approach to modifying shared code. The problem is
that it is very, very easy to make bad changes to shared code when it
is embedded into project source trees. The problems come in a number
of ways, such as project-specific code slipping into the shared area
or incompatible changes being made to the shared API that isn't found
until much later (during an unrelated project build).
Overall, it is a lessening of the boundaries between modules and makes
it easy for too many and incorrect dependencies to develop.
Given that it is the way you're set up, however:
> > Tagging isn't an issue. If you chose to not maintain separate release
> > cycles for shared code, that works fine by using global repository
> > tags across a single repository containing all the source (shared
> > modules and individual projects). That way you can tag the repository
> > using project-specific tags to pull back both the state of the project
> > as well as that of the shared code.
> So far, so good.
> > There is no reason to delete anything from the tags.
> Except that nobody wants to checkout the whole
> repository if all they need is "project1" at
> tag "X", you mean? AFAIK, ATM that's several GB,
> so this is not going to work.
Why would you check out the whole repository? You can tag the
repository without having it checked out. You can then check out only
the project you want, under a given tag. There is no need to pull the
svn copy -r 123 svn://repo/trunk svn://repo/tags/projectA/release3
svn co svn://repo/tags/projectA/release3 projectA-release3
> > Thank you,
> Well, I'm not sure what for. :)
Too many years writing emails at work. It's a well-formed habit.
Thank you, (see?)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Apr 9 17:06:00 2007