[MONGOCRYPT-206] Adjust GetVersion.cmake to produce dev versions recognizable by curator Created: 07/Nov/19  Updated: 28/Oct/23  Resolved: 08/Nov/19

Status: Closed
Project: Libmongocrypt
Component/s: cmake
Affects Version/s: None
Fix Version/s: 1.0.0-rc2

Type: Task Priority: Major - P3
Reporter: Roberto Sanchez Assignee: Roberto Sanchez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to MONGOCRYPT-192 Document package installation from PPA Closed

 Description   

The curator tool, which we use to publish libmongocrypt packages into a PPA for users to be able to install, recognizes version numbers in the following way:

  • contains 'rc' -> is a release candidate (testing)
  • contains '-' and is not a release candidate -> is a development build
  • all others -> is a release build

The way that GetVersion.cmake produces version numbers needs to be adjusted so that non-release and non-rc builds are always recognized as development builds by curator. That is, a version strategy is required where development builds take the last release version, increment the patch component, append '-dev', and then append the additional build information we prefer to have (currently build date and git commit hash).



 Comments   
Comment by Githook User [ 08/Nov/19 ]

Author:

{'name': 'Roberto C. Sánchez', 'username': 'rcsanchez97', 'email': 'roberto@connexer.com'}

Message: MONGOCRYPT-206 implement curator-compatible dev versioning
Branch: master
https://github.com/mongodb/libmongocrypt/commit/29727d87c154acb7720bb0b628ce1751afb89a6b

Generated at Thu Feb 08 09:08:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.