Note that we can merge or cherry-pick across repositories. We're already in
double check in territory, it's just I do the merges from wix39 to wix40
regularly and no one really notices. It's becoming increasingly difficult to do
such merges in some areas as wix40 advances. So eventually, I might have to
stop doing it automatically and have people double develop changes themselves.
At that point in the past there usually wasn't much going on in the old
branches excepted targeted bug fixes. Hopefully, the same happens here.
From: Heath Stewart [mailto:hea...@outlook.com]
Sent: Monday, February 24, 2014 6:51 PM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] One repo or many repos - the WiX toolset code
organization question.
In general I like the idea. The only problem is when we do want to migrate
code, and presumably - at least burn code - will be migrated regularly. So that
either means dual check ins or patching files sans history (unless someone
would patch files for every commit, but that's the same as dual check ins then).
If that's not a big deal, having standard branch names would be less confusing
when you're used to working in lots of different git repos. It just feels more
natural then.
Heath Stewart
Software Design Engineer
Visual Studio, Microsoft
http://blogs.msdn.com/heaths
________________________________
From: r...@robmensching.com<mailto:r...@robmensching.com>
To: wix-devs@lists.sourceforge.net<mailto:wix-devs@lists.sourceforge.net>
Date: Tue, 25 Feb 2014 01:10:39 +0000
Subject: [WiX-devs] One repo or many repos - the WiX toolset code organization
question.
Based on feedback, we'll be moving to GitHub sooner than later (in the next few
weeks).
I originally raised this question when I asked the move to GitHub question but
didn't get a clear feeling for preferences. So I'm back looking for further
thoughts and opinions.
With GitHub we get the option to have many repositories under a single
"organization". You can see that I've already split out the website here:
https://github.com/wixtoolset/site
That ability means we could create separate repositories for different major
versions of the WiX toolset. Doing so would allow us to use more "standard"
names for branches in the repo. For example, in the `wix3` repo the `master`
could be the latest released version like `v3.8` and `develop` could be the
next version like `v3.9`. A separate repo would have `wix4`.
I've thought about this for a while now and I'm inclined to break the WiX
toolset into repositories like this and I'm looking for feedback on the idea. I
can add this to the agenda for this weeks' meeting as well if desired.
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool. Monitor
traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your
own dashboards, set traffic alerts and generate reports. Network behavioral
analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________ WiX-devs mailing list
WiX-devs@lists.sourceforge.net<mailto:WiX-devs@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
