Reconcile the docs with the 0.0.4 release - #32
Merged
Conversation
Two statements that cutting 0.0.4 made false. The roadmap said no release or tag was scheduled. One was cut, so the file now names 0.0.4 as the current baseline while keeping the same standing instruction: no further release is scheduled. The README and the landing page both said PyPI releases "lag main". At the moment 0.0.4 shipped they were identical, so anyone reading right after the announcement sees a claim the repository contradicts. "Can lag" is the durable form — it stays true the moment the next commit lands and it stays true today.
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.
Two statements that cutting 0.0.4 made false.
The roadmap said no release or tag was scheduled. One was cut. It now names 0.0.4 as the current baseline while keeping the same standing instruction: no further release is scheduled.
The README and the landing page both said PyPI releases "lag
main". At the moment 0.0.4 shipped they were identical, so anyone reading right after the announcement sees a claim the repository contradicts. "Can lag" is the durable form — true today, and still true the moment the next commit lands.Found by sweeping for anything the release invalidated, not by noticing it in passing. The same sweep confirmed what is not stale: no doc references the removed
mlx_cv.parity,sitemap.xml'slastmodmatches the last commit touchingsite/, and the__pycache__left behind by the parity removal is gitignored and untracked.