Document the existing release steps #207
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
nwneisen
changed the title
nwneisen
force-pushed
the
205-release-process
branch
from
0f50034
to
94bccd6
Compare
neersighted
approved these changes
Jun 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
What type of PR is this?
馃敡 Task (no product change)
What this PR does / why we need it:
This documents the current release process and adds a make comment to make it easier to generate the release artifacts.
I deliberately kept the release command very basic because I could see it being deleted in the future in favor of the work for #206
Issue(s) this PR fixes:
#205
How has this been tested?
make cleanto remove everythingmake releaseto build everythingbuild/releaseNotes for reviewer(s):
I added a docs folder because I think the docs are lacking for the project they needed a place to grow 馃尡