[
https://issues.apache.org/jira/browse/IGNITE-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062322#comment-15062322
]
Igor Sapego commented on IGNITE-2185:
-------------------------------------
Ok, for autotools versioning is [a bit
complicated|http://www.gnu.org/software/libtool/manual/html_node/Release-numbers.html].
To put it short: there are two approaches to versioning and they both have
their shortcomings:
1. Use libtool's API version system ({{-version-info}} flag). The shortcoming
of this approach is that this version consists of only 3 numbers and is not
recommended to use for a package version (which I believe is our case).
2. Include release version in library name ({{-release}} flag). The drawback of
this approach is that it breaks backward compatibility of the libraries,
meaning no new libraries would be suitable to be used in place of old ones.
> CPP: Investigate version policies for autotools.
> ------------------------------------------------
>
> Key: IGNITE-2185
> URL: https://issues.apache.org/jira/browse/IGNITE-2185
> Project: Ignite
> Issue Type: Task
> Components: interop
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Igor Sapego
> Priority: Critical
> Fix For: 1.5
>
>
> Starting from this release we gave different version scheme - suffix is
> added. E.g.: 1.5.0-b1, 1.5.0-GA, etc.
> We need to understand how to properly handle this case with autotools. Can we
> simply set this string as version?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
