Sounds like a very good idea. See http://semver.org/ and 
http://marlowa.blogspot.com/2015/07/the-wonders-of-semantic-versioning.html 

On Wednesday, 7 September 2016 20:29:25 UTC+1, Jeffrey Walton wrote:
>
> Hi Everyone,
>
> I think a few folks have experienced this problem. Someone says "I'm using 
> Crypto++ 5.6.3 ...", and we are left wondering if its (1) the 5.6.3 ZIP, or 
> (2) 5.6.3 Master. We don't really know what they are using without follow 
> up questions, and we don't have a policy to deal with the problem.
>
> After the next release, I'd like to disambiguate by immediately bumping 
> the revision number after a release. The revision is the third value - its 
> 3 for 5.6.3; its 4 for 5.6.4; its 0 for 5.7, etc. As an example, say we 
> just released 5.6.4. The first check-in after the release would change the 
> version to 5.6.5. As another example, say we just released 5.7. The first 
> check-in after the release would change the version to 5.7.1.
>
> Are there any objections to the new policy after the next release?
>
> Jeff
>
>

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to