Open TSC Meeting, Thursday 30th April 2020

[MikeRalphson]

NOTE: This meeting is on Thursday at 9am - 10am PT
Zoom Meeting link: https://zoom.us/j/975841675

In order to give some more visibility into the topics we cover in the TSC meetings here is the planned agenda for the next meeting. Hopefully this will allow people to plan to attend meetings for topics that they have an interest in. And for folks who cannot attend they can comment on this issue prior to the meeting. Feel free to suggest other potential agenda topics.

*Please submit comments below for topics or proposals that you wish to present in the TSC meeting

Topic	Owner	Decision/NextStep
Decide on 3.1/3.5/4.0 & SemVer -discussion/votes in #2212	@OAI/tsc

[handrews]

I filed #2219 with an idea of how to communicate the magnitude of change in the next release. It would work with any of the proposed version numbers including keeping SemVer and going to 4.0.

[darrelmiller]

3.1 - Drop Semver and make minor breaking change. (Full JsonSchema compat)

[darrelmiller]

4.0 - Not really major but semver compliant (Full JsonSchema compat)

[darrelmiller]

8.0 - for Ron. (Full JsonSchema compat)

[darrelmiller]

2020-05 - no correlation between identifier and significance of changes. (Full JsonSchema compat)

[miqui]

2020/05.patch-xx

[karenetheridge]

<peanut gallery>

does it make any sense to do a 3.1 release first that doesn't contain the semver-requires-us-to-do-4.0 changes first, and then follow up with a 4.0 (that does) later on?

</peanut gallery>

[handrews]

@karenetheridge the "almost but not quite JSON Schema compatible" approach is unsatisfying, and rather confusing because some of the incompatibilities are rather subtle.

The idea has come up, but as @lornajane has emphasized, we really need to focus on releasing useful changes (it's been three years since 3.0) and punting 4.0 out could delay compatibility for a long time.

The idea of simultaneous 3.1 + 4.0 releases was floated, but I think that will really confuse people over which to take and why, and didn't get a lot of traction.

[Jaesin]

Semantic versioning is an existing promise. Is this something you can really just drop? It affects thousands of API and tooling developers. Is there a real obligation to release 3.1?

I understand that there is probably a roadmap for 4.0 but I'm wondering what is the cost of changing a roadmap is vs breaking the promise of keeping promises.

If there is really no way to maintain BC in 3.1, I suspect most would rather see it released as 4.0.

[darrelmiller]

@Jaesin I will be writing a blog post to explain the reasoning for this. It was not a decision we made lightly.

[MikeRalphson]

As above: decision taken, 3.1-rc0 released and blog post published.