Honestly, not squishing is reasonable. It’s good to see all the changes
necessary to get to the end goal. It’d be most ideal to have a branch per
change then merge those branches back, much like we do for each change accepted
to WiX toolset. The merge commit shows each set of changes in the history.
From: Heath Stewart [mailto:hea...@outlook.com]
Sent: Wednesday, December 18, 2013 9:39 AM
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] A number of port requests for bugs and features from
Microsoft
Okay. I'll only squash where there were bug fixes on new code (there's a couple
places where after thorough, practical testing we found a couple of issues I
fixed in new code).
- Heath from his Surface Pro
From: Bob Arnson<mailto:b...@joyofsetup.com>
Sent: Wednesday, December 18, 2013 9:36 AM
To: Windows Installer XML toolset developer mailing
list<mailto:wix-devs@lists.sourceforge.net>
I'd rather see (at least) one commit per fix, so that issues with multiple
fixes get multiple commits.
On 18-Dec-13 11:36, Heath Stewart wrote:
That's correct for that one. I'll add more information where needed. I was
mostly working off the brief changelist descriptions and 'tagging’ them with
the changelist numbers, as you no doubt guessed. �
Would you prefer 1 commit per issue? I may do 1 commit per checkin in my local
branch (there's some ordering necessary) but cold squash before pushing.
- Heath from his Surface Pro
From: Rob Mensching<mailto:r...@robmensching.com>
Sent: Tuesday, December 17, 2013 9:18 PM
To: Windows Installer XML toolset developer mailing
list<mailto:wix-devs@lists.sourceforge.net>
Next triage is Thursday at 9am PST. Can you please add as much information as
possible to the features. For example the “Merge directories correctly when
linking” is really short but it sounds like it allows duplicate rows to
overwrite each other (which is a really questionable feature of the past). So,
more information would be good.
But it looks like there are lots of good features here.
From: Heath Stewart [mailto:hea...@outlook.com]
Sent: Tuesday, December 17, 2013 5:38 PM
To: wix-devs@lists.sourceforge.net<mailto:wix-devs@lists.sourceforge.net>
Subject: [WiX-devs] A number of port requests for bugs and features from
Microsoft
It's been a while, but I've been cleared to push out various bug fixes and the
fixes/DCRs/features to complete the ref-counting and sticky patching features.
http://wixtoolset.org/issues/search/?filter=user:heaths&filter=status:Untriaged
I'm assuming we're not meeting next Tuesday. When is the next meeting? It'll
take some time to manually port a lot of these changes but they shouldn't take
long to ready.
Heath Stewart
Software Design Engineer
Visual Studio, Microsoft
http://blogs.msdn.com/heaths
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&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
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
