I definitely understand the motivation around updating things being a
positive, but it does break with the expectations set forth in the policy
http://mesos.apache.org/documentation/latest/versioning/#api-version-vs-release-version
We could create a v2 that follows the convention without the .json
Before we decide, I'd like to propose another view angle. Thanks to the
removal of the endpoint aliases, a widely used but only occasionally
maintained mesos-dns have been updated and a newer version will be released
soon [1] — thanks to jdef. I understand the frustration when software stops
I propose that we revert this change and keep the ".json" endpoints in
master branch and 1.8.x
My reasoning is that, we have ecosystem components (e.g., mesos-dns which
is yet to have a release with fix) and anecdotally a bunch of custom
tooling at user sites that depend on these ".json"
Folks,
The long ago deprecated '*.json' endpoints will be removed in Mesos 1.7.0.
Please use their non-'.json' counterparts instead.
Commit:
https://github.com/apache/mesos/commit/42551cb5290b7b04101f7d800b4b8fd573e47b91
JIRA ticket: https://issues.apache.org/jira/browse/MESOS-4509
Alex.
4 matches
Mail list logo