Skip to content

Latest commit

 

History

History
15 lines (12 loc) · 821 Bytes

RELEASE.md

File metadata and controls

15 lines (12 loc) · 821 Bytes
Raw

Releasing

CI based

The release process is also automated in the way any specific commit, from the master branch ideally, can be potentially released, for such it's required the below steps:

  1. Checkout the commit to be released
  2. Create a tag with the format [0-9]+.[0-9]+.[0-9]+, i.e.: 1.0.2
  3. Push the tag to the upstream.
  4. Then, the CI pipeline will trigger a release.
  5. Wait for an email/slack to confirm the release is ready to be approved, it might take roughly 20 minutes.
  6. Login to apm-ci.elastic.co
  7. Click on the URL from the email/slack.
  8. Click on approve or abort.
  9. Then you can go to the https://packagist.org/packages/elastic/ecs-logging and GitHub releases to validate that the bundles and release notes have been published.