You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@thrift.apache.org by jk...@apache.org on 2019/07/11 10:55:36 UTC
[thrift] branch master updated: Update the versioning description
[ci skip]
This is an automated email from the ASF dual-hosted git repository.
jking pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/thrift.git
The following commit(s) were added to refs/heads/master by this push:
new 49aab65 Update the versioning description [ci skip]
49aab65 is described below
commit 49aab657b95e0b0955cb487fefb794ae2f83fd98
Author: James E. King III <jk...@apache.org>
AuthorDate: Thu Jul 11 06:55:28 2019 -0400
Update the versioning description [ci skip]
---
doc/ReleaseManagement.md | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/doc/ReleaseManagement.md b/doc/ReleaseManagement.md
index ce0744b..362fd83 100644
--- a/doc/ReleaseManagement.md
+++ b/doc/ReleaseManagement.md
@@ -8,12 +8,13 @@ It is important to note here that Apache Thrift is designed for version interope
### Versioning
-Apache Thrift and the vast majority of package management systems out there conform to the [SemVer 2.0](https://semver.org/spec/v2.0.0.html) version numbering specification.
+Apache Thrift and the vast majority of package management systems out there conform to the [SemVer 2.0](https://semver.org/spec/v2.0.0.html) version numbering specification. Apache Thrift uses the following versioning rules:
-In terms of releases, the important version numbers for Apache Thrift are the major and minor. The patch number is used in the following cases:
+- *major* is currently always zero;
+- *minor* is increased for each release cycle;
+- *patch* is increased for patch builds between release cycles to address critical defect, security, or packaging issues
-1. There were language-specific critical defects or packaging issues.
-1. There was something horribly and fundamentally wrong with a x.x.0 release.
+Further, if there are only packaging changes for a single third-party distribution point to correct an issue, the major.minor.patch may remain the same while adding a suffix compatible with that distribution point, for example "0.12.0.1" for nuget, or "0.12.0-1" for maven.
#### External Package Patches