release-26.08 content - #9
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
2 participants
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.
This PR establishes the initial release candidate for EM•porium [26.08] on the upstream staging branch.
The repository has been deliberately reduced to the content intended for the first public release: Tour Groups 100 — Getting Oriented and 101 — Basic Examples, the supporting core/example/target/Pico content, and the normal Emporium infrastructure required to provision and run the environment.
The Basic Examples have already been built and run successfully on the Raspberry Pi Pico simulator.
Before promotion to main, review should focus on two broad areas:
Distribution QA — verify that the retained examples and supporting content continue to build and run cleanly in the reduced environment. The combo examples can also be exercised as a broader stress test.
On-ramp and tour QA — review Tours 100/101 and the installation/onboarding documentation against the new minimal release surface; refresh screenshots where useful; and verify that tour source markers and narrative remain aligned with the current source files and tooling.
Issues found during this release-bash period can be corrected directly on staging before the final release-26.08 promotion to main.