Advice re. implementing Mercurial

BOGGESS Rod CORE Rod.Boggess at tenova.com
Mon Feb 9 13:24:06 UTC 2015





Tenova: advanced technologies for the metals and mining industries
Visit our website at www.tenova.com
------------------------------------------------------------------
Confidentiality Notice : This message, together with its attachments, contains strictly confidential information and is intended only for the addressee identified above,who is the sole party authorized to use
 and copy it and, assuming any related liability , to forward it to others. Anyone receiving this message by mistake or reading it without authorization is hereby notified that storage, reproduction, disclosure or distribution of the message to persons other than the addressee is strictly forbidden. They are asked to return the message immediately to the sender and to erase the original message received.
Thank you.


-----Original Message-----
Thanks for the comments ... the problem is that I don't think all-or-nothing will work for us; if we released less frequently, perhaps, but as it is we release an updated version every[0] week[1]. So we really can't be in a position where we've pushed 15 bugfixes into Development and none of them go out until all 15 pass QA - the option has to be there for QA to approve 11 of the fixes and hold back the other 4 for a future release.  If we separated bugfixes into urgent / high / low priority branches I suppose that would potentially let us get around that - bugs already get classified on importance, of course - but I think we'd still have the same issue when a bug changed priority?


 [1] and unfortunately we probably can't get away from that - we sell software into small businesses and it's not uncommon for them to tell us things like "our supplier has changed their EDI file format without any warning! We need the new format integrated by next week!", or similar. In an ideal world we'd say "get a better supplier", but in practice, the answer has to be "well, that's chargeable work, but we'll get right on it and have a new version out shortly."

-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-

You don't maintain separate repos or branches for different customers?


More information about the Mercurial mailing list