[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: |
|
||||||||||||
| 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: |