Personally, I'd vote for killing "master". There is an illusion around master
being something special, when in reality it's just a name.
Have an ancient repo and a 4x repository, but don't squash the ancient repo
before moving it. I can live with 3x (ancient) and 4x being separate.
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: Thursday, February 06, 2014 5:01 PM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] The Great GitHub Discussion
On 2/6/2014 3:43 PM, Rob Mensching wrote:
More importantly, I think separate repos would follow the typical dev work flow
better where master is the latest version and other branches support the master
or the next version.
On the various projects I've worked on, trunk/head/master has always been the
latest in-development code, with branches for releases and bug fixes. People on
http://stackoverflow.com/questions/153812/subversion-is-trunk-really-the-best-place-for-the-main-development
seem to agree, but maybe since it's about SVN it's outdated nowadays?
--
Bruce
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
