design: add release process design doc#657
Conversation
Defines a modified GitHub flow release strategy for Scion with: - Two-channel model: RC (preview) and stable releases - Weekly cadence (aspirational, not mandated) - release/vX.Y branches cut from main, SemVer tags - Starting at v0.3.0 (v0.2.x reserved for homebrew tap) - CI changes to build-release.yml for automatic channel routing
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
This is a repo management document, not an application design doc. It belongs in docs-repo/ alongside contributing.md and code-of-conduct.md.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a formal release process for Scion, defining a two-channel model (preview and stable) and outlining the associated branch, tag, and CI/CD workflow strategies. The reviewer correctly identified that the proposed GitHub Actions tag filter syntax uses incorrect glob wildcards and provided a corrected suggestion to ensure the workflow triggers as intended.
I am having trouble creating individual review comments. Click here to see my feedback.
.design/release-process.md (110-111)
The + character is not a standard glob wildcard in GitHub Actions workflow tag filters. Using [0-9]+ will likely fail to match version tags as intended. Please use [0-9]* instead to match one or more digits correctly.
- 'v[0-9]*.[0-9]*.[0-9]*' # Stable: v0.1.0, v1.2.3
- 'v[0-9]*.[0-9]*.[0-9]*-rc.*' # Preview: v0.1.0-rc.1
|
fixes ptone#334 |
1 participant
Adds a project design document for the release process: branching taxonomy (main, release/vX.Y, rc and stable tags), weekly stabilization cadence, cherry-pick strategy for hotfixes, and GitHub Actions integration