[SERVER-60209] Add option of persisting old multiversion constants after upgrade Created: 24/Sep/21  Updated: 29/Oct/23  Resolved: 04/Apr/22

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

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

Issue Links:
Depends
Related
related to SERVER-65394 Ensure that old LTS constants are gen... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2022-03-21, Repl 2022-04-04, Repl 2022-04-18
Participants:

 Description   

After PM-2091, we will not generate any FCV constants older than lastLTS. This will need to be modified so that we can temporarily have references to these older FCVs after upgrading FCV constants. We can potentially do this by adding a new value to releases.yml that determines whether or not to generate old FCV constants.

 

This ticket will let us delay removing old FCV constants until a later period after upgrading, making the window between branch cut and updating FCV constants much smaller.



 Comments   
Comment by Githook User [ 04/Apr/22 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-60209 Add option of persisting old multiversion constants after upgrade
Branch: master
https://github.com/mongodb/mongo/commit/6abfb1f99e65c451b233bce7e1b941d74669a7b5

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