Labeling issues in WiX

During our last WiX Online Meeting, I talked myself into volunteering to study how other projects use labels in their issues. Here’s what I came up with:

  • Some repos prefix their labels to sort them into “namespaces,” like resolution and area. Generally prefixes are common in repos with many dozens of labels. WiX doesn’t have that many issue labels so I propose that we don’t need them. Instead, we should just document the labels we use. Now, who can we get to volunteer to write some documentation? Dammit. OK, I’ll write up that documentation.
  • We have some near-duplicate labels, like compiler and candle. We decided in general to consolidate the labels, preferring a form like compiler (candle).
  • We have some probably-too-precise labels, like burn-acquisition. We decided in general to consolidate those labels as well.
  • One technique some repos use is to tag their issues with labels that indicate a swag at the complexity of resolving it. Two we agreed are useful would be wip-required, when we believe a WIP is necessary, and up-for-grabs, to indicate a relatively simple issue that nobody is yet claiming.

WiX v3.11 released

On Cinco de Mayo 2017, we released WiX v3.11. WiX v3.11 RTM is v3.11.0.1701.

You can download the WiX Toolset v3.11 build tools and Visual Studio extensions here.

The primary goal of the WiX v3.11 development cycle was to support Visual Studio 2017. We met that goal, with more than the usual number of challenges, due to the scope of changes in Visual Studio 2017.

In previous versions of WiX v3.x, Votive, the Visual Studio extension for WiX, was part of the WiX installer. Due to Visual Studio 2017’s changes to support multiple instances, WiX v3.11 now comes in two parts:

  • The WiX build tools, MSBuild support, extensions, and SDKs. These are delivered in the WiX v3.11 bundle.
  • The Visual Studio extension, one for each supported version of Visual Studio (2010, 2012, 2013, 2015, and 2017). These are available from the Visual Studio Marketplace.

Plenty of other stuff happened in the WiX v3.11 cycle, too. For details on bug fixes, new features, and other changes, please see the release notes on GitHub.

Rob also wrote about the WiX v3.11 release, if you’d like other words on the topic.

WiX v3.10.3 released

On 4 July 2016, the 240th anniversary of the approval and publication of the United States Declaration of Independence, the Juno spacecraft is scheduled to enter polar orbit around Jupiter and WiX v3.10.3 was released.

WiX v3.10.3 contains fixes for the regressions introduced in WiX v3.10.2 by the “clean room” technique that mitigates against Windows vulnerabilities that affect bundle executables.

Download WiX v3.10.3.

The following bugs were fixed:

Universe willing, WiX v3.10.3 is the final release of the WiX v3.10 series. Up next is WiX v3.11.

Rob also had words on this release.

WiX v3.10.2 released

An unpleasant first: We had to release a security update for the WiX Toolset. Here’s the recipe:

That’s it, really. Bake and serve and suddenly every executable is potentially a carrier for malware.

WiX v3.10.2 contains mitigations for Burn that avoid the vulnerability. If you ship bundles, you really really need to upgrade to v3.10.2 so you can ship safe bundles.

More details about the release are available in the Setup Matters blog post I wrote.

Download WiX v3.10.2 here.

WiX Toolset v3.10.1 Released

WiX v3.10.1 is a maintenance release of WiX v3.10 with the following important fixes:

Download it here.

As you can see, we had a couple of problems with Windows XP support. Though I ran a few manual tests on XP during and at the end of v3.10, that wasn’t sufficient to uncover the bugs. Next time, I’ll put out an explicit call for testing support from folks still supporting Windows XP and Windows Server 2003. We’re going to need your help to keep bitrot at bay!

Here’s what Rob had to say about this release.