SVN Best practice for a "branch" of your main product ?
Posted
by Steffen
on Stack Overflow
See other posts from Stack Overflow
or by Steffen
Published on 2010-05-03T09:33:09Z
Indexed on
2010/05/03
9:38 UTC
Read the original article
Hit count: 309
svn
|best-practices
At my job we develop websites - however now we're going to make a "whitelabelled" version of a site, which basically means it's the same site, however with a different logo and hosted on a different domain.
Also it'll have minor graphical differences, but overall the engine is the same.
My initial thought for keeping this in SVN, was to just make a branch for it - however I'm not quite certain if this could give me trouble later on.
Normally I keep my branches somewhat short lived - mainly used for developing a new feature, without disturbing trunk.
We need to be able to merge trunk changes into this "whitelabel" version, which I why I thought about branching it in the first place.
So what's the best way to archive this ?
© Stack Overflow or respective owner