doc: add maintainers doc for releasing #39
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
pothos
reviewed
Feb 1, 2024
| git tag -d latest | ||
| git tag -as latest | ||
| git push origin --force latest | ||
| ``` |
There was a problem hiding this comment.
Or maybe we can change the CI to re-release on every main change, plus weekly. It would also update the tag.
There was a problem hiding this comment.
Would make sense to me. I'm working on a build automation feature to build releases based on a list of versions in a text file, and include all sysexts from the previous "latest" release. Your proposal would be a great follow-up task to that PR.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Everything is in the title.