[SERVER-46167] Enumerate and remove Storage-related FCV 4.2-dependent code and tests Created: 14/Feb/20  Updated: 12/Mar/20  Resolved: 12/Mar/20

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Jason Chan Assignee: Susan LoVerso
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Storage Engines 2020-03-23
Participants:
Story Points: 5

 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. Create a ticket identifying Storage-related generic upgrade/downgrade references that the Upgrade/Downgrade team should update now that the 4.2-dependent references have been removed.



 Comments   
Comment by Susan LoVerso [ 12/Mar/20 ]

Storage Engines/WiredTiger does not have any FCV issues to solve.

Comment by Eric Milkie [ 11/Mar/20 ]

I don't remember if there is anything remaining from the Unique Indexes project that Neha and Sulabh worked on, but if there is, we can take care of it in our Execution ticket for this same work. Other than that I don't believe there is anything else you are missing.

Comment by Susan LoVerso [ 11/Mar/20 ]

milkie Alex suggested I ask you for clarification, but we don't think WiredTiger/Storage Engines has any work to do here. We don't really manage things in the same way with FCV. So I believe we can just call this done. Do you know of anything I should be considering?

Comment by Jocelyn del Prado [ 06/Mar/20 ]

brian.lane, I've added this to the next sprint for you to consider.

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