[wix-devs] v4 extension versioning

Sean Hall r.sean.hall at gmail.com
Thu Jan 17 08:12:50 PST 2019

What I meant was that there are some packages we would never put breaking
changes into, for example Data or Extensibility. If we were still going by
v3 guidelines, we wouldn't put breaking changes into any of the packages.
I'm still surprised we're considering taking breaking changes into
extensions in v4.

On Wed, Jan 16, 2019 at 10:33 PM Rob Mensching <rob at firegiant.com> wrote:

> I don't know if we know right now which ones would have breaking changes
> so it seems like we'd want to name them consistently upfront.
> -----Original Message-----
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean
> Hall via wix-devs
> Sent: Monday, January 7, 2019 10:44 AM
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Cc: Sean Hall <r.sean.hall at gmail.com>
> Subject: Re: [wix-devs] v4 extension versioning
> I would think we would only apply the v4 naming to the ones we would
> consider adding breaking changes to.
> On Mon, Jan 7, 2019 at 12:01 PM Rob Mensching <rob at firegiant.com> wrote:
> > It's funny. I originally thought about adding a "v4" to the namespace
> > before then realized the core tools probably didn't need it and promptly
> > forgot about it as an option.
> >
> > It's an interesting option for WixExtensions. The question is would we
> > need to use it everywhere for consistency sake?
> >
> > Something like: "WixToolset.v4.Data" (or "WixToolset.Data-v4" or
> > "WixToolset.Data.v4" or whatever) and "WixToolset.v4.Extensiblity"?
> >
> > For the record, I don't like that... but namespace versioning the
> > extensions namespace should work.
> >
> >
> > PS: The reasons I don't like semver are less about its rules and more
> > about the mechanics of setting semver versions. Due to those mechanical
> > issues, I find semver less sacrosanct than others.

More information about the wix-devs mailing list