[SERVER-46166] Enumerate and remove Execution-related FCV 4.2-dependent code and tests Created: 14/Feb/20 Updated: 29/Oct/23 Resolved: 01/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Dianna Hohensee (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: | Execution Team 2020-03-23, Execution Team 2020-04-06 | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Description |
|
The following tasks need to be completed once we branch for 4.6: 1. Create a list of tickets with code and tests to remove, add them to the 4.6 Upgrade/Downgrade Epic, and mark them as "is depended on by" this ticket. This will assist the Upgrade/Downgrade team in tracking progress. If there is an insufficient amount of work to warrant multiple tickets, then the work can be done under this ticket directly. 2. Complete all necessary tickets promptly. 3. Update |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 01/Apr/20 ] |
|
All the FCV tickets this work depends upon have been completed. |
| Comment by Jason Chan [ 10/Mar/20 ] |
|
dianna.hohenseeI agree trying to traverse the git history will be difficult. I believe in most cases, it would work to assume ownership of the FCV code based on where the code is located.
|
| Comment by Dianna Hohensee (Inactive) [ 10/Mar/20 ] |
|
jason.chan I think it will be difficult to track down which team added what FCV code that is intended to remain across binary versions. The git history becomes a mess to look through because the code gets updated to the new FCV values every release. Instead, I recommend the upgrade/downgrade team look at each remaining reference after the teams have finished removing what belongs to them. Each remaining reference should ideally have a comment explaining that the FCV handling must remain across versions. If there is no explanation on the code, then it will need to be investigated because no team thought it belonged to them, and either removed because it was missed or updated with such a comment for future clarity. |
| Comment by Jason Chan [ 10/Mar/20 ] |
|
dianna.hohensee |
| Comment by Dianna Hohensee (Inactive) [ 10/Mar/20 ] |
|
jason.chan can you clarify what |