Uploaded image for project: 'Evergreen'
  1. Evergreen
  2. EVG-12690

Implement new versioning scheme

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: current_quarter
    • Component/s: platform
    • Labels:
      None

      Description

      This should ideally be a separate implementation from the legacy versioning scheme, whose logic should preferably not change.

      For this, we should just implement the existing methods on the mongodb version object, but with their new meanings. This new versioning scheme should only apply for versions 4.5.0 and above.

      For example, development series do not exist anymore, but a release that goes into the development repo should be denoted by any non-LTS version which has major.quarter.patch format and is not followed by -rcN (special for release candidates).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kimberly.tao Kim Tao
              Reporter:
              kimberly.tao Kim Tao
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: