SVN Best practice for branching your main product?
At my job we are developing websites, however now we are going to make a "whitelabelled" version of the site, which basically means the same site but with a different logo and hosted on a different domain.
In addition, it will have minor graphical differences, but overall the engine is the same.
My initial thought for keeping this in SVN was to just create a branch for it - however I'm not entirely sure if this might cause problems later.
I usually keep my branches a little short - mostly used to develop a new feature without breaking the trunk.
We need to be able to merge the changes to the chests into this version of the "whitelabel" and so I thought about forking it first.
So what's the best way to archive this?
a source to share
When I was working on the white lettering website before, it was built from one source per brand, with a configuration parameter telling you which branding to use at runtime. However, you can also provide shared functionality and resources in a module that is imported into each of the branded version branches using external svn, so that changes to shared code can be automatically tracked in each branding. Thus, the affiliate for each brand simply contains the brand-specific resources.