Order the changelog for its reader and call the tree 0.2.0 - #32
Merged
Conversation
The 0.2.0 list grew in merge order; a reader meets it in another one. The hash break and the TraceEvent change come first, then how failures explain themselves, then what the simulated world gained, then the evidence. Every entry moved verbatim, under a short paragraph saying what the release is about.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The 0.2.0 section grew in merge order; it now opens with a paragraph saying what the release is about, then leads with the two things upgrading actually costs — the trace-hash break and the TraceEvent type change — before how failures explain themselves, what the simulated world gained, and the evidence. Every entry moved verbatim. The version strings both say 0.2.0; the date replaces (unreleased) when the tag is cut.