[THRIFT-274] Towards a working release/versioning process

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.1
• Assignee: Jake Farrell
• Reporter: Luke Lu
• Created: 16/Jan/09 23:43
• Updated: 08/Jun/13 03:16
• Resolved: 08/Jun/13 03:16

Description

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.

Issue Links

• is depended upon by: THRIFT-1259 Automate versioning
• is related to: THRIFT-6 Thrift libraries and compiler lack version number