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

Re: [Subclipse-users] Subversion workflow

From: John Crisp <john_at_reetspetit.net>
Date: Mon, 16 Apr 2012 16:48:45 +0200

On 16/04/12 00:33, Mark Phippard wrote:
> Google for "SVN Vendor branch" and there is a lot of good info, blogs and examples.

One more question.... :-)

We have a number of sites using various systems such as Joomla, ZenCart etc.

We usually use the base code and then make modifications on a per site
basis, though some sites will share some of the modifications (e.g
various additional plugins that are commonly used).

Is it better to have separate repositories for each site or would it be
better to have one repo with several branches, one for each site ?

How do we cope with Vendor updates ?

I would presume that we should make the generic modifications 'site
wide' in which case we ought to bring the Vendors code into a repo, add
change any mods, and then export it/import it into the 'clients' repo.
before merging to their branches.

Or is there an easier/better way ?

B. Rgds


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2012-04-16 16:49:01 CEST

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

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