[B.A.T.M.A.N.] Clarification of version number in batctl/main.h

[B.A.T.M.A.N.] Clarification of version number in batctl/main.h

[Sven Eckelmann]

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

Hi,
I just wanted to ask how to interpret the current version number of batctl. 
Does it mean that the current version in svn is before or after a possible 
0.2-beta release? Is it important for me because debian differentiates between 
before and after something. For example 0.2~beta would mean that there is a 
beta version before the 0.2 release. So I wanted to know if should call a svn 
snapshot of the current batctl 0.2~beta~svn1317 (svn1317 snapshot before a 
possible 0.2~beta release) or 0.2~beta+svn1317 (svn1317 snapshot after the 
beta phase has started - no beta version will ever be made available or has 
been released already).
It seems that the 0.2~beta~svn1317 is the more "correct" version as it has 
less extra rules than 0.2~beta+svn1317. For example there must not be an extra 
rule for events like the release of 0.3.1 of batman when Simon changed the 
version string to 0.3.1 in 1177 which was before the release of 0.3.1 and thus 
shouldn't be called 0.3.1+svn1177.
Can this be interpreted the same way for all other on open-mesh.net published 
hosted projects? So if I would create a snapshot version of batman it would 
have the version number 0.4~beta~svn1309?

Regards,
Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

Re: [B.A.T.M.A.N.] Clarification of version number in batctl/main.h

[Marek Lindner]

Hi,

> Can this be interpreted the same way for all other on open-mesh.net
> published hosted projects? So if I would create a snapshot version of
> batman it would have the version number 0.4~beta~svn1309?

that s perfectly fine with me. If the version string contains an "alpha" it 
means we are going towards the alpha release. The last commit before the 
renaming to "beta" is the final alpha.

Regards,
Marek