From d141448fbe4af05114b3be4037e63480f9b533d2 Mon Sep 17 00:00:00 2001 From: Andreas Neumann Date: Wed, 30 Sep 2020 10:33:48 +0200 Subject: [PATCH] Clarify SemVer usage for app version (#1694) Signed-off-by: Andreas Neumann --- keps/0019-package-api-versioning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/keps/0019-package-api-versioning.md b/keps/0019-package-api-versioning.md index 86a6af67d..36003f6ed 100644 --- a/keps/0019-package-api-versioning.md +++ b/keps/0019-package-api-versioning.md @@ -117,7 +117,7 @@ The version of an _application_, e.g. 3.11.5 (for Apache Cassandra), 2.3.0 (for Even though this version will more commonly follow [SemVer](https://semver.org/) for operators managing popular applications, it is ultimately outside of our control and therefore cannot be assumed to be [SemVer](https://semver.org/). -Programs dealing with the application version can try to parse it as a structured specification like SemVer, but should be able to handle anything (i.e., fall-back to strings). +Even though the original app version may not be SemVer, we require operator developers to use a SemVer application version to ensure correct ordering. ## Summary