Update release documentation and scripts to record flushed-out steps #52
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
djc
reviewed
Jan 4, 2024
cpu
approved these changes
Jan 4, 2024
complexspaces
force-pushed
the
release-process-improvements
branch
from
13d5ca0
to
53d8d17
Compare
|
Thanks for catching all my typos again @djc 😆. This should be ready for another review pass. |
cpu
approved these changes
Jan 4, 2024
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.
This PR updates the release documentation, and associated scripts, to account for the updated release steps and requirements that were discovered in the process of publishing the initial
0.1release yesterday (#49).I believe that the documentation could definitely use some more smoothing out regarding the order of preparation PRs, commits, and
cargo publishoperations but I've yet to think of anything that would make it markedly better.