[SERVER-85955] Consider relaxing latest assert in releases.h.tpl Created: 30/Jan/24  Updated: 05/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Xuerui Fa Assignee: Xuerui Fa
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Sprint: Repl 2024-02-19
Participants:

 Description   

This assertion in the releases template file may cause compile to fail if the release steps are performed out of order and the git tag is added ahead of the changes to releases.yml. We can be more defensive about this and set latestFCV to the most recent version in releases.yml that is <= the current git tag. This will allow developers to still compile in this situation.

If this situation happens, we can log a warning that this is an unintended scenario to help debugability too.


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