Release process should require a PR review

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Unknown
    • 4.13
    • Affects Version/s: None
    • Component/s: greenerbuild
    • None
    • None
    • Python Drivers
    • 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?
    • None
    • None
    • None
    • None
    • None
    • None

      It would be great if pymongo's release process required a PR review prior to tagging the final commit. This would help because it gets a second person to review the docs/changelog/etc.. before a release is published.

      For example the changelog 4.11.2 says "Changes in Version 4.11.2 (YYYY/MM/DD)": https://pymongo.readthedocs.io/en/4.11.2/changelog.html#changes-in-version-4-11-2-yyyy-mm-dd

            Assignee:
            Steve Silvester
            Reporter:
            Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: