docs: add v0.1.2 release notes - #32
Merged
Merged
Conversation
Curated notes for the 0.1.2 release body: complete runs only, the headline-first order and BaseRT's 4K headline reservation, the unmodified llama-bench path and what it records instead, signed host environment boundaries, and the explanation for previously deleted benchmarks.
The headline-first path and same-run telemetry are selected by what the installed harness advertises, and BaseRT 0.2.5 is the first release that advertises them. Say so, say how to upgrade BaseRT, and say that the client does not announce a newer BaseRT by itself.
The notes said the client does not tell you when a newer BaseRT exists. With #33 it does: before the plan, in the printed session, and above the full-screen menu with an update key.
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.
Summary
docs/release-notes/0.1.2.md. The release workflow uses it as the body of thev0.1.2GitHub release instead of generated notes (seedocs/releasing.md).rc-0.1.2sincev0.1.1: the headline-first order (feat: headline-first benchmarks with explicit context and telemetry metadata #28), BaseRT's 4K headline reservation andcomputearena-throughput/3, the unmodified llama-bench path and what the report records instead, signed host environment boundaries, and previously deleted benchmarks (fix(cli): explain deleted benchmark submission failures #29). The CI smoke-test change is internal and left out.Validation
rc-0.1.2(process layout inadapters/llama_cpp.rs, the capability gate and validation inadapters/basert.rs,docs/telemetry.md,docs/benchmark-profiles.md) and against fix(cli): submit only runs with the full default sweep #31 for the submission rule