[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

best practices for framework based projects

From: Adam Kempler <akempler_at_kemplergroup.com>
Date: 2006-02-09 21:23:40 CET

I was wondering what the best practice is for using svn with projects
based on a common framework.
Please let me know if I should be addressing a different list with this

I have a framework that I use for all client sites.
When I create the client site, I add a lot of new modules to the
existing framework, specific to the project.
I also tend to make a lot of adjustments/improvements to the framework

Should I create a branch for each project so that I can merge changes
back into the main framework line?
Or does that become too complicated if I start branching the project
branch, etc?

Should I just tag the trunk with the new project name, export the
framework and then create a new module?

I'm fairly new to version control.
I searched the mailing list archives and didn't see anything on this
topic, so if it's been discussed and answered already please just point
me in the right direction.


Adam Kempler

To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Feb 9 21:24:06 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.