Create a skill for handling the mechanical parts of upgrading FCV constants

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2026-08-31
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      To add a new FCV release (e.g. SERVER-129707), an engineer has to perform a series of mechanical tasks, which include:

      •  adding the new constant in the releases.yml files
      • adding the requires_fcv_XXX tag as the list of excluded tags
      • upgrading the hardcoded version numbers in a few specific files

      I am purposefully limiting the scope of this ticket to just the mechanical parts, as activities like the above include also running tests, excluding the ones which need to be changed/removed due to the upgrade of FCV constants, and cutting tickets to the owning teams. 

            Assignee:
            Marco Bizzarri
            Reporter:
            Marco Bizzarri
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: