curator release versions should be populated from the project expansions

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.4.16, 3.6.6, 4.0.0-rc5, 4.1.1
    • Affects Version/s: None
    • Component/s: Build
    • None
    • Fully Compatible
    • v4.0, v3.6, v3.4
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      we should change the value of curator_release in the server evergreen.yml to use a project expansion, in the form of: 

      ${curator_release|<default_value>)

      which will let us move forward and try releases across branches and make the process of updating and experiment with evergreen deploys much easier, particularly during release season.

            Assignee:
            Ramon Fernandez Marina
            Reporter:
            Sam Kleinman (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: