Skip to content

Document release process expectations #1030

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

Closed
joshuagl opened this issue May 6, 2020 · 1 comment
Closed

Document release process expectations #1030

joshuagl opened this issue May 6, 2020 · 1 comment
Labels
documentation Documentation of the project as well as procedural documentation

Comments

@joshuagl
Copy link
Member

joshuagl commented May 6, 2020

When looking at the POUF for the reference implementation I realised that we should probably make an effort as part of the release process to ensure it's up to date.

Furthermore we should document the release process and a pre-release checklist of tasks that should be completed before tagging a release.

Possible items for a pre-release checklist:

  • Ensure the TUF version number written to metdata files is correct and up-to-date
  • Ensure that POUF 1 is up-to-date
  • Ensure the CHANGELOG lists major changes
  • Bump the version number

Possible items for the release process:

  • tag the release with a signed tag
  • generate a Python wheel and upload to PyPI
  • generate archives for inclusion in the GitHub release
  • Add release information to GitHub with generated archives
@joshuagl joshuagl added the documentation Documentation of the project as well as procedural documentation label May 6, 2020
@joshuagl
Copy link
Member Author

joshuagl commented Sep 8, 2020

Documented in #1094

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation of the project as well as procedural documentation
Projects
None yet
Development

No branches or pull requests

1 participant