Repository navigation
Closed
Description
Migrated from Notion on 2026-05-07
Workflow
- Create PR to
next - PR’s build is green
- Cron job rebase and the PR against
next, and aggregate it with other open and green PRs tounstable - The package version must be at least 7 days old since release
- PR is approved by someone other than the author
- PR is merged into
next - Create PR to
stable - The PR’s build is green
- The package version must be at least 7 days old since release
- The PR dwells in
nextfor 7 days. This gives the community an opportunity to provide feedback about the package - PR is approved
- PR is merged into
stable
Promotion to next
- PRs are based on
next; - Manual approval from a Minimal staff other than the author is required;
- Smoke test coverage for all major functionality is required;
- These are standalone tests in buildspec that meaningfully test functionalities of the package. The package’s native tests (ie.
make test) cannot be used for this purpose.
- These are standalone tests in buildspec that meaningfully test functionalities of the package. The package’s native tests (ie.
- Version of the package must by >7 days.
Promotion to stable / main
- Inclusive of all criteria used for promotion to
next;- This requires a second PR approval
- Delve time >7 days;
- No negative community feedback.
Other Promotion Rules
- Trivial updates
- Trivial is defined as: no new features, no breaking changes. The judgement of this will need to be automated. 6D39
- Human approval based on green build in PR. No manual package execution / functional validation required.
- Mechanism: tag pr as #trivial
- Non-trivial CVE / vulnerability
- Goes through all validation criteria in
nextandstable - Manually expedited
- Goes through all validation criteria in
- Any branch that are user facing must have binary ready in the cache
- Need a mechanism to keep caches up to date for
nextandstable
- Need a mechanism to keep caches up to date for
Acceptance Criteria
- User is able to use
nextandstableas part of the[upstream]definition without the CLI throwing errors - Users are not waiting for packages to build when executing tasks while on
nextorstablebranch, unless they specify rebuild flags. - Binaries from the
nextbranch must be ≥7 days old since the release of the corresponding package version- The exception to this is in the case of non-trivial CVE / vulnerability.
- Binaries from the
stablebranch must be ≥14 days old since the release of the corresponding package version- The exception to this is in the case of non-trivial CVE / vulnerability.
Sub-tasks
- Discussion Pkgs workflow, gates, and releases
- Acceptance Criteria
- Technical design
- Task phasing
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Milestone
Relationships
Development
Issue actions
Open in GitHub Copilot app
Activity
norrietaylor commentedon Jun 1, 2026
Closing - bad routing.