[
https://issues.apache.org/jira/browse/THRIFT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585256#comment-14585256
]
Roger Meier edited comment on THRIFT-6 at 6/14/15 8:29 PM:
-----------------------------------------------------------
What about using [semantic versioning | http://semver.org/] consequently and
closing this issue?
e.g. 1.0.0 will require C++11 compiler
was (Author: roger.meier):
What about consequently use [semantic versioning | http://semver.org/] and
closing this issue?
e.g. 1.0.0 will require C++11 compiler
> Thrift libraries and compiler lack version number
> -------------------------------------------------
>
> Key: THRIFT-6
> URL: https://issues.apache.org/jira/browse/THRIFT-6
> Project: Thrift
> Issue Type: Bug
> Components: Build Process
> Affects Versions: 1.0
> Reporter: Bryan Duxbury
> Assignee: Roger Meier
> Fix For: 1.0
>
> Attachments:
> 0001-THRIFT-6-Thrift-libraries-and-compiler-lack-version-.patch,
> ASF.LICENSE.NOT.GRANTED--v1-0001-THRIFT-6.-Add-a-Makefile-rule-to-print-the-version-f.patch,
> THRIFT-6_align_version_and_description_to_0.6.0-dev.patch, updateversion.sh
>
>
> Right now it's impossible to tell which version of Thrift you have installed.
> If you're depending on features that have recently been added (and that
> subtly don't exist), you can spend a lot of time chasing your tail trying to
> figure out what the problem is.
> This may be something that has to be implemented piecemeal on each client
> library (ruby gem, java classes, etc). Thoughts?
> While we're at it, let's add a --version switch or something to the compiler
> so you know what version of stuff you're actually generating.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
