I would like to make a few changes to how Mesos handles version numbers: (1) Mesos versions (e.g., as defined in `configure.ac`) must be parseable as valid SemVer (see http://semver.org/).
This has always been the case with version numbers assigned by the Apache Mesos project, but if your organization maintains a private fork or snapshot of Mesos with a custom version number, please ensure that it follows SemVer. (2) Mesos 1.2.1, 1.3.1, and 1.4.0 masters will now ignore registration attempts from pre-1.0 Mesos agents. We never explicitly guaranteed compatibility between pre-1.0 agents and 1.0+ masters, but we didn't explicitly disallow this situation either. As of the Mesos releases listed above, masters will now ignore registration attempts by pre-1.0 Mesos agents. Previous discussion: https://lists.apache.org/thread.html/f5e15f6d7a3f3b08d29e27455e2e1c801775418a148dded953c568e7@%3Cdev.mesos.apache.org%3E (3) The version number for "in development" versions of Mesos will now have a "-dev" prerelease label. In the past, when we created a release branch for Mesos 1.3.x, the code in the master branch was updated to use the version number "1.4.0". To clarify that this in-development version of Mesos is not the final release of Mesos 1.4.0, we'll use a "-dev" prerelease label in the future. For example, the current code in the master branch will have the version "1.4.0-dev". Previous discussion: https://lists.apache.org/thread.html/6e291c504fd44b79e452744b80073cb33adc1be85c17e22bbca35a6c@%3Cdev.mesos.apache.org%3E Please let me know if you have concerns about any of these changes. Thanks, Neil
