Add guidelines to feature flag documentation for handling around backporting features

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Backporting features is generally discouraged. However there are specific times where it is approved and needed. In these situations engineers find themselves confused for what state to leave the feature flag in across the different branches. FCV_AND_FEATURE_FLAG_README should cover this and answer specific questions such as

      1. Should the feature flag itself be backported? Or should the backported contents come after the feature flag's removal?
      2. If the feature flag is backported, what version value should the feature flag be enabled in on the older branch?
      3. What version value should the feature flag be enabled in on the latest branch?
      4. Is it reasonable for a feature which is backported to an older branch to be using shouldBeFCVGated: true on the latest branch?

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Max Hirschhorn
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: