Repository navigation
Version 0.5.1 - #45
Merged
Merged
Conversation
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
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 changes
Version 0.5.1, following #40's files:
Cargo.toml,Cargo.lock(the four workspace crates),CITATION.cff(version and date), the app manifest (0.5.1.0), the bug report placeholder..github/workflows/windows.ymlpublishesdocs/releases/v0.5.1.mdas the release notes.CHANGELOG.md, the release notes,README.mdandinstaller/README.md(asset names and the executable size),docs/ARCHITECTURE.md(version named),PROGRESS.md(Make a zoom step change only the rows and paint once #43, Draw thin theme-coloured scroll bars and fit the shortcut list #44 and this PR).SECURITY.mdand the format tables name the 0.5 line and stay as they are.Measured
The numbers in the notes come from one run on the maintainer's laptop: a local build of 0.5.0 (d323dbf, the 0.5.0 code) and this branch, measured the same way with the harnesses from #43 and #44, saved zoom set to 100% for the runs and put back.
The first zoom run on the 10M-row file had single steps of up to 0.7 s on 0.5.0 and 1.1 s on 0.5.1 (0.5.0 median 133.5 ms, 0.5.1 median 23.2 ms); the notes use a second run (115.4 and 21.0 ms). Start times in this run were about 15 to 80 ms higher on both versions than in the #44 runs; the two versions were within 4 ms of each other.
Checks
cargo test --workspace: 273 passed. One test failed once in five runs on this branch and passed in the other four; the run did not keep its name. No test changed in this PR.What the merge and the tag start
Windows quality and releaseon main.pages.ymldoes not run (nosite/change).v0.5.1on the merge commit runsWindows quality and releasefor the tag, which publishes the GitHub release with the unsigned ZIP and its.sha256, andstore-msix.yml, which builds the Store package.Rollback
Revert this commit. No data or settings format changes. A published tag and release would need deleting by hand.
Not in this PR
site/,store/listing.mdanddocs/VALIDATION_STATUS.md.store-msix.ymlstill givesv0.5.0as its example tag.