-
Notifications
You must be signed in to change notification settings - Fork 110
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
Set up versioned releases #200
Comments
Note: We have a PR for releases via goreleaser and goreleaser can handle pre-releases + generate changelogs. It really makes sense to have a closer look on my PR here and maybe get this done for the first release: |
If needed I can provide a test release in my fork, so that you can have a look at it and we discuss changes etc |
Cross-referencing an older issue where the need for releases is discussed #114 |
Glad to see that this has been addressed! Thank you! |
We are still pre-1.0, but we need to give users a way to know when breaking changes are made and upgrade accordingly.
As discussed in the TUF community meeting, we intend to version pre-1.0 releases as v0.x.y, where x is incremented for breaking changes.
We will build release notes from a changelog file, updated in each PR as necessary. Changes will be tagged by sub-system, like
[client]
,[cli]
, or similar.A PR review checklist may help with the process.
The text was updated successfully, but these errors were encountered: