Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release issue for v0.12.0 #457

Closed
18 tasks done
foresterre opened this issue Jun 1, 2020 · 0 comments
Closed
18 tasks done

release issue for v0.12.0 #457

foresterre opened this issue Jun 1, 2020 · 0 comments

Comments

@foresterre
Copy link
Owner

foresterre commented Jun 1, 2020

RELEASE PR: #458


Notable changes from 0.11 to 0.12:

  • Added draw-text image operation which can be used (for example) to watermark an image

Release checklist

Initialize release

  • Create release issue. Already a step complete! 😉
  • Create release branch

Update version number

  • Define update version number as described here.
  • Update the version number in all Cargo.toml files (i.e. all workspace crates).
    • Specifically, for the pre-1.0 versions the versioning strategy is currently as follows:
      • The minor version number is the same for all workspace crates, and incremented
        for each release.
      • The patch version is increased on a as-needed basis, separately per crate.
  • The Clap App version number in src/main.rs will be equal to the version number in the root Cargo.toml.

Update the dependency licenses to be included in the binary as per their licenses

  • Run cargo run --example update_dep_licenses to update the licenses of dependencies, which will be included in a binary build.

Create Release PR

  • Create release PR

Verify

  • Verify formatting with cargo +nightly fmt.
  • Does cargo test succeed?
  • Verify image output of images produced with cargo test --features output-test-images.
  • Do all CI runs complete successfully?
  • Are the versions indeed updated for all packages?
  • Is the application version updated?
  • Are the dependency licenses updated?

Completed!

Merge Release PR

If no blocking issues are detected and this checklist is complete,
we can move on to the next step.

Publish & Upload

  • Run cargo package and check the resulting .crate
  • Run cargo publish and verify the result

Release, Tag & Binaries

  • Write release notes

  • Create a release with a version tag on the github release page

    • tags are equal to crate version number and prefixed with v, e.g. v0.5.1
    • release title is sic-<version> e.g. sic-0.5.1
  • Add Windows and Linux binaries to the release

    • compile with cargo build --release and strip afterwards

Release steps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant