Skip to content

Latest commit

 

History

History
25 lines (24 loc) · 1.43 KB

RELEASE.md

File metadata and controls

25 lines (24 loc) · 1.43 KB
Raw

Release checklist

  1. Release a new version of btf-rs and/or sub-crates if needed.
  2. Release a new version on GitHub.
    1. Make sure the README is up-to-date (collectors, build instructions, etc).
    2. Add new authors to the authors file if needed, by running ./tools/authors.sh and committing the changes.
    3. Update the version in Cargo.toml, retis-events/Cargo.toml and retis-derive/Cargo.toml.
    4. Open a PR and get it merged. This must have runtime tests enabled!
    5. Tag the right commit in the vx.y.z form and push it.
  3. Release binaries.
    1. Build a new set of packages on copr.
      1. Update the spec file in our copr repository.
      2. Make sure the right set of distributions is enabled for the group. If not that can be set in the project settings.
      3. Packages > Rebuild.
    2. Build and upload the python bindings.
      1. podman run --rm --env MATURIN_PYPI_TOKEN=$(cat ~/.my_pypi_token) -v $(pwd):/io:z ghcr.io/pyo3/maturin publish -m retis-events/Cargo.toml -F python-lib
  4. Write and publish a release notes in the GitHub interface. This must be done once the rpm and the image successfully built to allow pushing last minute build fixes.
    1. Make sure "Set as the latest release" is checked only for y-stream releases and z-stream releases of the latest major version.