docs(adr): classify zpmod as class 2 - #498
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates org policy documentation (ADRs, runbooks, and contributor instructions) to explicitly classify zpmod as a class 2 (versioned tool/package) repository with trunk-based development on main, and to record the expected release/publication boundary and exact-tag functional testing obligations.
Changes:
- Adds
zpmodto class-2 enumerations across the release/testing/branching ADRs and runbooks. - Clarifies that
zpmodreleases are bounded by annotatedvX.Y.Ztags from reviewed, greenmaincommits, with functional testing on the exact tag commit. - Aligns testing instructions and references to the owning audit/issues (#497, z-shell/zpmod#70).
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| runbooks/release.md | Adds zpmod as an example of a class-2 repo in the release runbook. |
| decisions/0013-repository-settings-baseline.md | Updates class-2 repo enumeration to include zpmod. |
| decisions/0009-testing-ci-strategy.md | Extends class-2 testing guidance to include zpmod exact-tag functional suite requirements and adds references. |
| decisions/0008-branching-model.md | Adds zpmod to the trunk-on-main set and to the canonical branch model table. |
| decisions/0007-release-publication-flow.md | Adds zpmod to class-2 release/publication policy and per-repo application notes. |
| .github/instructions/testing.instructions.md | Updates contributor-facing testing instructions to include zpmod as class 2 and clarifies exact-tag suite expectations. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
zpmodas class 2 with trunk-based development onmain.vX.Y.Zrelease tags from reviewed, greenmaincommits, exact-tag functional testing, and Pages publication from reviewedmaincommits only.Closes #497
Related: z-shell/zpmod#70
Verification
trunk check --filter=markdownlint,git-diff-checkon all six changed filespython3 -m unittest scripts/test_validate_agent_policy.py -v(70 tests)python3 scripts/validate-agent-policy.pyAgent handoff
No handoff needed.