• 0
    • Not Needed
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Use Case

      As a node engineer
      I want to reuse the new release workflow for releases from main
      So that I can make backports available easily and swiftly

      User Impact

      • None

      Dependencies

      • None

      Unknowns

      • Does any of the scripting need to be merged to 4.x?

      Acceptance Criteria

      Implementation Requirements

      • Duplicate the release workflow used for releasing from main
        • Use composite shared actions when possible
        • Change the target branch to 5.x & 4.x
      • Ensure the release_notes workflow works against a release PR targeting a non-main branch
        • Manually trigger the action, direct it at the "5.x release" PR

      Testing Requirements

      • Manual verification mentioned above

      Documentation Requirements

      • Update release instructions if any salient details are different for releasing from non-main

      Follow Up Requirements

      • None

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Durran Jordan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: