Repository navigation
Conversation
… get, check and write the pre-release and where the instructions are, a diagram of how the parts fit together with the file each box lives in, and the tag and production-release paths named beside the build steps
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.
Docs only. The README gains a "Get it" section (download, verify against the anchor, write the USB stick, where the instructions are), a "How it fits together" section with the Mermaid diagram of the zone runtime, the desktop isolation, the zone services and the boot and update path, each box naming its file, and a paragraph that walks the diagram. The status paragraph names the v0.1.0 pre-release and stays honest about QEMU and the build's keys. The building section names the tag path and the production-release document; the documentation list gains the releases page.
Two edges of the diagram as drafted were wrong and are fixed: EFI boot entries are armed by
kryptik-updatefor the trial boot, not tied to the update channel, so that tool is a box of its own; theclicklines are dropped since GitHub renders Mermaid with clicks disabled.