[ 
https://issues.apache.org/jira/browse/THRIFT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roger Meier updated THRIFT-6:
-----------------------------

    Attachment: updateversion.sh

here is an initial version of the [^updateversion.sh] script.
Might be an option to merge it with bootstrap.sh and do these version updates 
with additional command line parameters.

I'm a big fan of having 1.0.0-c3b2e24 instead of 1.0.0-dev especially for local 
release and jenkins builds.

the source shall always keep 1.0.0-dev or right now probably better 0.9.0-dev 
because a 0.9.1 release is planned, I suggest this:
{noformat}
release:     0.9.0
source code: 0.9.0-dev
local build: 0.9.0-c3b2e
release:     0.9.1
source code: 0.9.1-dev
local build: 0.9.1-a8b9e
{noformat}

-roger

                
> 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

Reply via email to