We discussed this at a weekly meeting a few weeks ago and I believe agreed that
work should be done against wix4 and back ported to wix3 (if appropriate). Of
course, bugs only in wix3 should only go there. <smile/>
Bob, Sean, Jacob, correct me if I'm remembering that wrong.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
From: Heath Stewart [mailto:hea...@outlook.com]
Sent: Monday, September 29, 2014 10:06 AM
To: wix-devs@lists.sourceforge.net
Subject: [WiX-devs] Dual check ins?
I seem to recall at some past meeting that post-3.9 we should start doing dual
check ins. Is that correct? Even if not, I see after a weekend of doing so that
the tool chain code has diverge quite a bit so I'm sure Rob probably
appreciates the help...but hopefully I'm not screwing up your process*. So I
don't mind doing it, just wondering if there's any reason we shouldn't at this
point (especially with 3.x development supposed to be winding down).
* BTW, what is that process? I added wix3 as a remote of wix4 and tried
cherry-picking but, of course, the code was so different (namely, in
src\tools\wix) it didn't really offer any benefit. Additionally - and this was
weird - 'git diff -- history.md' showed what appeared to be a complete diff
with wix3 (i.e. all lines changed) while running 'git difftool -g' with kdiff
configured showed me just a conflict in the line I wanted to add. Since kdiff
gets temporary files made by 'git' I thought this was really weird.
Heath Stewart
Software Design Engineer
Visual Studio, Microsoft
http://blogs.msdn.com/heaths
------------------------------------------------------------------------------
Slashdot TV. Videos for Nerds. Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
