Advice re. implementing Mercurial
David Capps
dcapps at keystonesoftware.co.uk
Mon Feb 9 13:40:39 UTC 2015
-----Original Message-----
From: BOGGESS Rod CORE [mailto:Rod.Boggess at tenova.com]
Sent: 09 February 2015 13:24
To: David Capps; Martin Geisler
Cc: mercurial at selenic.com
Subject: RE: Advice re. implementing Mercurial
> You don't maintain separate repos or branches for different customers?
Not as such, no - we have well over a hundred active customers, and probably 95%+ of the code is common between the apps we deploy to each customer, so maintaining a separate repo or branch for each customer would be an awful lot of work. The majority of the development goes into the shared core code too; customer-specific changes do happen but aren't that common, we prefer to roll any new features into the main app so they're available should another customer need a similar feature.
The end result is that the majority of bugfixes would need to apply to all customers, so if we maintained a separate branch per customer, we'd just end up needing to apply most bugfixes to every single customer-specific branch.
Cheers,
--
David Capps
More information about the Mercurial
mailing list