Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-27355

Avoid hard-coding 3.2 and 3.4 featureCompatibilityVersion in JS

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Sharding

      It would be great to be able to write something like 'latestFeatureCompatibilityVersion' and 'previousFeatureCompatibilityVersion', similar to 'latest' and 'last-stable' bin versions, instead of hard coding "3.2" and "3.4" everywhere in our JS code.

      The code changes committed in SERVER-26828 should be considered in the solution. That code would benefit from a way to further determine whether the current release has a new feature compatibility version, because right now it's just a manual change between true and false.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: