[
https://issues.apache.org/jira/browse/THRIFT-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914253#action_12914253
]
Roger Meier commented on THRIFT-274:
------------------------------------
What about the SemVer approach? => simple & clear!
{code}
# The API version (NOT the product version), composed as a dot delimited
# string with major, minor, and patch level components.
#
# - Major: Incremented for backward incompatible changes. An example would
# be changes to the number or disposition of method arguments.
# - Minor: Incremented for backward compatible changes. An example would
# be the addition of a new (optional) method.
# - Patch: Incremented for bug fixes. The patch level should be increased
# for every edit that doesn't result in a change to major/minor.
#
# See the Semantic Versioning Specification (SemVer) http://semver.org.
const string VERSION = "0.4.0"
{code}
This snippet comes from
http://svn.apache.org/viewvc/cassandra/trunk/interface/cassandra.thrift?view=co
no more magic *1.0*! every digit has a clear and simple definition
> Towards a working release/versioning process
> --------------------------------------------
>
> Key: THRIFT-274
> URL: https://issues.apache.org/jira/browse/THRIFT-274
> Project: Thrift
> Issue Type: Bug
> Reporter: Luke Lu
>
> The current thrift version is virtually useless because it's not getting
> updated when backward compatibility is broken (it's always 20080411-exported
> on all the snapshots,) I can't just tell people to use the trunk and not
> breaking things due things like namespace changes etc. Many projects maintain
> a reasonable versioning scheme even when system is in alpha state.
> Thrift overall is stable enough to warrant a working versioning scheme. Can
> we at least start to discuss a version scheme, e.g., major.minor.patch or
> major.minor.micro.patch, where patch number changes are bug fixes and minor
> or micro are backward compatible changes and major changes indicate breaking
> backward compatibility or just marketing hype.
> I propose that we call the current thrift version 1.0.0.0 after all the
> namespace changes and stick to a reasonable scheme instead of using suffixes
> (like beta<n>/rc<n> etc.) as it's much friendlier to other components that
> uses thrift.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
