Skip to content

RELEASING.md

Latest commit

 

History

History
33 lines (26 loc) · 1.81 KB

RELEASING.md

File metadata and controls

33 lines (26 loc) · 1.81 KB
Raw

Releasing

Preparing a new release

  • Close the release milestone if there is one.
  • Run opentelemetry.io workflow against semantic-conventions submodule as a smoke-test for docs. Fix broken links, if any.
    • If there are failures you can't resolve, notify #otel-comms and corrdinate fixing them.
  • Run the prepare release workflow.
    • Review and merge the pull request that it creates.
    • Note: the PR will need to be closed and the workflow re-run if any non-chore PRs are merged to main while the PR is open.

Making the release

  • Create a new release:
    • Set title and tag to v{version}
    • Set target to the commit of the merged release PR
    • Copy changelog to the release notes
      • First click the generate release notes button and keep only the bottom sections under "New Contributors"
    • Verify that the release looks like expected
    • Publish release

New release is then auto-discovered by opentelemetry.io pipelines which (via bot-generated PR) eventually results in new version of schema file being published.

After the release

  • Publishing a release triggers the post-release workflow, which opens a pull request against main bumping the development schema_url in model/manifest.yaml to the {major}.{minor+1}.0-unreleased version. Review and merge that pull request.