[SERVER-65400] Remove generating 'kFullyDowngradedTo...' constants from releases.h Created: 08/Apr/22 Updated: 29/Oct/23 Resolved: 01/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Luxi Liu (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-2821-milestone-1, pm-2821-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Repl 2022-06-27, Repl 2022-07-11 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We should stop generating the last LTS constant as kFullyDowngradedTo...}, since this will cause redness upon branching. For example, before the 6.0 release, we referenced the 6.0 FCV enum as kVersion_6_0. However after branching, if we want to immediately add the new git tag to upgrade FCV constants, the last LTS will be kFullyDowngradedTo_6_0. This will cause the old kVersion_6_0 references to break, leading to unavoidable redness on evergreen. In order to immediately upgrade after branching without redness, we should stop generating last LTS as kFullyDowngradedTo... |
| Comments |
| Comment by Githook User [ 01/Jul/22 ] |
|
Author: {'name': 'Luxi Liu', 'email': 'luxi.liu@mongodb.com'}Message: |