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.
