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

Consider relaxing latest assert in releases.h.tpl

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Replication
    • Fully Compatible
    • Repl 2024-02-19, Repl 2024-03-04, Repl 2024-03-18, Repl 2024-04-01, Repl 2024-04-15, Repl 2024-04-29, Repl 2024-05-13

      This assertion in the releases template file may cause compile to fail if the release steps are performed out of order and the git tag is added ahead of the changes to releases.yml. We can be more defensive about this and set latestFCV to the most recent version in releases.yml that is <= the current git tag. This will allow developers to still compile in this situation.

      If this situation happens, we can log a warning that this is an unintended scenario to help debugability too.

            Assignee:
            xuerui.fa@mongodb.com Xuerui Fa
            Reporter:
            xuerui.fa@mongodb.com Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: