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