Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Thrift Wiki" for change 
notification.

The "HowToVersion" page has been changed by RogerMeier.
http://wiki.apache.org/thrift/HowToVersion

--------------------------------------------------

New page:
This page should describe the versioning of libraries. '''It's a DRAFT'''!

goal is to solve the following issues:
 * https://issues.apache.org/jira/browse/THRIFT-6
 * https://issues.apache.org/jira/browse/THRIFT-274

||'''Language'''|| '''via configure.ac''' || '''File(s) containing Version 
Information''' || '''Open Issues / Questions''' ||
||as3 || || || no version available||
||cocoa || || || no version available||
||cpp || yes || config.h (generated) || none ||
||csharp || no ||lib/csharp/ThriftMSBuildTask/Properties/AssemblyInfo.cs || how 
to automate? people do not use configure scripts on Windows!||
||erl || yes ||lib/erl/src/thrift.app.src || none, is configure anyway 
required?  ||
||hs || no || lib/hs/Thrift.cabal|| automate via lib/hs/Makefile.am ? is 
configure anyway required? ||
||java || no ||lib/java/ivy.xml ||how to automate? Java people do not use 
configure scripts! ||
||javame || || || no version available||
||js || || || no version available||
||ocaml || || || no version available||
||perl || ||lib/perl/lib/Thrift.pm || it seems, that lib/perl/Makefile-perl.mk 
does not use version info from configure scripts ||
||php || || || ?||
||py || || lib/py/setup.py || automate via lib/py/Makefile.am ? is configure 
anyway required? ||
||rb || || lib/rb/Rakefile|| automate via lib/py/Makefile.am ? is configure 
anyway required? ||
||st || || ||  no version available||

General Questions:
 * which version string should be used on trunk? 0.6.0-dev or 0.6.x or 
0.6.0-SNAPSHOT

== Versioning Concept ==
Semantic Versioning Specification (!SemVer) http://semver.org
 * Major: Incremented for backward incompatible changes. An example would be 
changes to the protocol.
 * Minor: Incremented for backward compatible changes.
 * Patch: Incremented for bug fixes

Reply via email to