[SERVER-32461] Determine and remove featureCompatibilityVersion-dependent Query code behavior that is only relevant to the 3.4-3.6 transition Created: 26/Dec/17 Updated: 30/Oct/23 Resolved: 02/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Bernard Gorman |
| 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: | Query 2018-01-29, Query 2018-02-12 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
As part of the 3.8 upgrade/downgrade project, all upgrade/downgrade behavior that was specific to the transition between 3.4 and 3.6 should be removed. The storage team will oversee that all teams remove 3.4 to 3.6-specific upgrade/downgrade behavior in their respective projects. To facilitate this removal, the storage team would like each team to determine which upgrade/downgrade behavior is specific to the 3.4 to 3.6 transition and which is generic upgrade/downgrade behavior that should be preserved between releases. The storage team will update the generic upgrade/downgrade behavior locations to use the most up-to-date featureCompatibilityVersion values. |
| Comments |
| Comment by Githook User [ 02/Feb/18 ] |
|
Author: {'email': 'bernard.gorman@gmail.com', 'name': 'Bernard Gorman', 'username': 'gormanb'}Message: |