Develop labels for automated release notes

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Go Drivers
    • 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

      Context

      PR #2047 suggests creating automated release notes. The labels determined in the PR may not be the ones we actually use.

      Definition of done

      1. Determine if we should start labeling pull requests for automated release notes
      2. Should we create a JIRA automation rule to label pull requests: e.g. bug, enhancement, breaking-change. If we decide manual is best, we should update the pull request template to note this as a TODO: master/docs/pull_request_template.md

      We should also update CONTRIBUTING.md.

              Assignee:
              Andreas Braun
              Reporter:
              Preston Vasquez
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: