Re: release process for 1.1 libraries?

On Wed, Feb 7, 2018 at 2:03 PM, Gregg Kellogg <gregg@greggkellogg.net> wrote:
>
> > On Feb 7, 2018, at 10:46 AM, David I. Lehn <dil@lehn.org> wrote:
> >
> > What do people think about releasing libraries with 1.1 draft spec support?  Gregg Kellogg has done some great work adding 1.1 support to jsonld.js and pyld.  We'd like to release that code for people to use but I'm unsure on how to best do it.  Once the code is out there people will start using and depending on the features.  If changes need to be made before 1.1 is final, it would be nice to be able to change anything as needed.
> >
> > Libraries can use a semantic versioning scheme, and if the spec changes, that will bump up the version.  But how do we deal with the JSON-LD data itself?
> > ...
>
> People have been using my Ruby JSON-LD library for a while, which has these issues released. Indeed, semantic versioning is a way to introduce a breaking change to the library, but you have a point about people creating data which relies on this.
>
> Not sure about putting more semantics in @version. If the eventual WG decides to break compatibility with CG 1.1 issues, then they would likely need to signal this with a different version number.
>

Yeah, adding more versioning complexity doesn't seem worth it alone.
It might be worth it if it was via some mechanism that had other uses.

If the WG *or* CG makes breaking changes then it could invalidate data
marked today as 1.1 as libs get updated.  I guess I'm asking about
some extra patch versioning to be used as development goes along.


> > The easiest thing to do is release the libs, and document that all 1.1 features are for draft specs and subject to change.  User beware.
>
> In whatever state, I think the libraries need to be released, if only as a pre-release, as people do rely on features such as id maps now, and likely other features.
>

>From a maintainer viewpoint it's easiest to just push forward and
release as new features.  Old branches can get fixes as needed if
people want to use older versions.  Luckily the 1.1 libs pretty much
handle the 1.0 syntax just fine in any case.

-dave

Received on Wednesday, 7 February 2018 21:28:00 UTC