[
https://issues.apache.org/jira/browse/THRIFT-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740909#comment-13740909
]
Roger Meier commented on THRIFT-6:
----------------------------------
It is still pain to update all Versions or add a build number to the Thrift
libraries ... a nightmare.
and the blocker for frequent releases.
We currently describe the process on versioning here:
http://thrift.apache.org/docs/committers/HowToVersion
I currently work on a shellscript to update all Version Info within Apache
Thrift source files.
Goal:
* shell script to be executed before build
** create the release: *sh contrib/updateversion.sh 0.9.1 release*
*** set release version
*** set git hash tag
** after a release, update source tree: *sh contrib/updateversion.sh 0.9.2*
*** set new development version
** do a regular build and add the git hash to the version: *sh
contrib/updateversion.sh*
*** set git hash tag
* provide info on debian/control, doap.rdf & co
Questions I like to discuss:
* replace -dev suffix always with "git rev-parse --short HEAD" ?
* use "git rev-parse --short HEAD" also for releases ?
* how do we version csharp and delphi with the quadruple pattern 0.0.0.0 ? I
triple allowed?
{noformat}
[assembly: AssemblyVersion("0.9.1.0")]
[assembly: AssemblyFileVersion("0.9.1.0")]
[assembly: AssemblyInformationalVersion("0.9.1.0-2ca9c20")]
{noformat}
* how to differentiate between release and development version?
release: 0.9.1.1 or
development: 0.9.1.0
please provide feedback, the script is ready very soon.
-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:
> 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
>
>
> 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
