Re: Source Control Strategies for working with Frameworks

Have you looked at what the book says about "Vendor Branches"? It might
help.

http://svnbook.red-bean.com/svnbook/ch07s04.html

Mark

      To&nbsp;&nbsp; <users@subversion.tigris.org>
      cc&nbsp;&nbsp;
      bcc&nbsp;&nbsp;
      Subject&nbsp;&nbsp; Source Control Strategies for working with
Frameworks
"Bryan Andrews" <bandrews@trendinfluence.com>

04/11/2004 11:38 AM AST
            <font size=-1></font>

We work with a couple of open source frameworks that we extend and are
trying to determine the best way to work / develop against the frameworks
with subversion.

Most of our development we do as private assemblies that reference the
frameworks, but sometimes its impossible to not change the framework
itself.

What I am wondering is how others might setup the dir structure effectively
in this situation.

Currently we have the release versions of the framework in the trunk and
tagged on each release, then we have a main branch that we dev on.

I am wondering if our main dev should be in the trunk (like normally).

I guess the main needs are to be able to diff between each version of the
framework and then diff our development against the new release of the
framework.

Any recommendations are appreciated here as we are new to this scenario.

Thanks!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Apr 11 17:58:58 2004