docs: refine downstream onboarding workflow
This commit is contained in:
@@ -1,22 +1,23 @@
|
||||
# Minion Template Version
|
||||
|
||||
Current version: 1.3.0-1.0.0
|
||||
Current version: 1.3.1-1.0.0
|
||||
|
||||
Version format for downstream repos: `<base-template-version>-<downstream-version>`
|
||||
|
||||
Example downstream version: `1.3.0-1.0.0`
|
||||
Example downstream version: `1.3.1-1.0.0`
|
||||
|
||||
## Downstream Onboarding Method
|
||||
|
||||
- Keep the initial template snapshot in `.minions-template/`.
|
||||
- Keep the initial export-ready template snapshot in `.minions-template/`.
|
||||
- Use [docs/downstream-onboarding-playbook.md](docs/downstream-onboarding-playbook.md) and [docs/export-manifest.md](docs/export-manifest.md) to perform the first controlled export into the live downstream repo.
|
||||
- Treat `INIT.md`, `MEMORY.md`, `docs/operator-onboarding-checklist.md`, and `minion-version.md` as onboarding merge files, not blind copies.
|
||||
- Exclude `.git/` and `do-not-export` files such as `.mm.md` from the vendored snapshot.
|
||||
- Commit the vendored snapshot and exported live files together so later upgrades have a stable comparison base.
|
||||
|
||||
## Downstream Upgrade Method
|
||||
|
||||
- Keep the currently approved template snapshot in `.minions-template/`.
|
||||
- During upgrade, stage the incoming template in a temporary path such as `.minions-template.next/`.
|
||||
- Keep the currently approved export-ready template snapshot in `.minions-template/`.
|
||||
- During upgrade, stage the incoming export-ready template in a temporary path such as `.minions-template.next/`.
|
||||
- `PM` owns the downstream merge/migration unless the Operator assigns another owner.
|
||||
- Use [docs/downstream-upgrade-playbook.md](docs/downstream-upgrade-playbook.md) and [docs/export-manifest.md](docs/export-manifest.md) to compare:
|
||||
- old vendored template
|
||||
|
||||
Reference in New Issue
Block a user