[SERVER-58285] Disallow inaccurate MONGO_VERSIONs Created: 06/Jul/21  Updated: 29/Oct/23  Resolved: 22/Jul/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Xuerui Fa Assignee: Ryan Egesdahl (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Dev Platform 2021-07-26
Participants:

 Description   

On the master branch (which will become 5.1), we will need to disallow setting MONGO_VERSION to inaccurate values. While we could try something more complex, the best answer is probably to just disallow setting it to 0.0.0.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 22/Jul/21 ]

Author:

{'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'}

Message: SERVER-58285 Disallow MONGO_VERSION=0.0.0

Developers have commonly set MONGO_VERSION=0.0.0 in the past to avoid
having to set one explicitly for every build. However, there are better
and widely-available ways to set this automatically now, and in upcoming
releases, it will be important for MONGO_VERSION to be set to an
accurate value. From now on, we will specifically disallow setting it to
0.0.0 as a way of signaling to developers that they should stop setting
it explicitly. In the future, we may do further checking to ensure the
variable is set to an accurate value.
Branch: master
https://github.com/mongodb/mongo/commit/d8a447aaa333d984f56bfab3d13ba94555a209b2

Generated at Thu Feb 08 05:44:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.