Repository navigation
Conversation
This branch has not been deployed
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.
Summary
Add a checklist for publishing the next RustiFlow release as GitHub's Latest while preserving WTMC as the last fully handwritten version.
docs/ + release-plan.mdThe plan covers candidate selection, Linux runtime validation, release packaging, compatibility notes, and publication checks. Version and date remain open until the readiness review.
Evidence
Before this change, the repository had no dedicated next-release plan. The new document links the existing workflows and records two concrete gaps: they do not publish standalone release binaries, and the engineering notes still list live realtime validation as outstanding.
Checked all relative links and plain punctuation.
git diff --checkpassed. Rust tests were not run because this change only adds documentation.Merge danger
This documentation change is reversible. Its scope is the release checklist. Merging it does not publish a release or change the WTMC tag or assets.