Determine and remove featureCompatibilityVersion-dependent Sharding code behavior that is only relevant to the 3.4-3.6 transition

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.2
    • Affects Version/s: None
    • Component/s: Upgrade/Downgrade
    • None
    • Fully Compatible
    • Sharding 2018-01-15, Sharding 2018-01-29
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Jack Mulrow
            Reporter:
            Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: