[
https://issues.apache.org/jira/browse/THRIFT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742750#comment-13742750
]
Jens Geyer commented on THRIFT-6:
---------------------------------
{quote}
I spend more time when making a release on fixing all the missed files and
flags within the source/makefiles/scripts/jenkins/automated tests/etc [...]
{quote}
I see, you created a lot of tickets in the last two days. How can we streamline
this process? How can we make sure that the missing things are recognized
early?
> Thrift libraries and compiler lack version number
> -------------------------------------------------
>
> Key: THRIFT-6
> URL: https://issues.apache.org/jira/browse/THRIFT-6
> Project: Thrift
> Issue Type: Bug
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
