Post-cut playtest feedback path #59

New issue

Closed

opened 2026-08-04 19:26:53 +00:00 by TheAnachronism · 1 comment

TheAnachronism commented

2026-08-04 19:26:53 +00:00

Owner

Part of #41
Blocked by: #58

Question

After the readiness doc exists (and later when beta is cut), how should playtest findings feed back — update the readiness criteria in place, open ordinary tracker issues, or another path?

Part of #41 Blocked by: #58 ## Question After the readiness doc exists (and later when beta is cut), how should playtest findings feed back — update the readiness criteria in place, open ordinary tracker issues, or another path?

TheAnachronism added the

wayfinder:grilling

label

2026-08-04 19:26:59 +00:00

TheAnachronism self-assigned this

2026-08-04 19:32:23 +00:00

TheAnachronism commented

2026-08-04 19:35:32 +00:00

Author

Owner

Resolution

Playtest feedback path for the readiness artifact / beta cut:

Pre-cut (before first `beta/<semver>` publish)

Always open ordinary Forgejo issues (triage labels as usual).
Also update docs/1.0-beta-readiness.md when a finding is:
- a new Blocker / core-loop break, or
- a Known issues inventory change (Document ↔ Ignore, add/remove Document rows).
Eng / packaging must-line changes are not quiet doc edits — reopen criteria / wayfinding if a locked eng or packaging Must proves wrong.
Plain bugs that don’t change those bars stay issue-only.

Post-cut (after first `beta/<semver>` APK is published)

Freeze the readiness doc.
New findings are tracker issues only — do not append to the Known issues table.
Document/Ignore classification for new surprises happens via ordinary triage, not readiness edits.

Recorded as section Playtest feedback path in docs/1.0-beta-readiness.md.

## Resolution **Playtest feedback path** for the readiness artifact / beta cut: ### Pre-cut (before first `beta/<semver>` publish) 1. **Always** open ordinary Forgejo issues (triage labels as usual). 2. **Also update** [`docs/1.0-beta-readiness.md`](../src/branch/master/docs/1.0-beta-readiness.md) when a finding is: - a **new Blocker / core-loop break**, or - a **Known issues inventory** change (Document ↔ Ignore, add/remove Document rows). 3. **Eng / packaging must-line** changes are **not** quiet doc edits — **reopen criteria / wayfinding** if a locked eng or packaging Must proves wrong. 4. Plain bugs that don’t change those bars stay **issue-only**. ### Post-cut (after first `beta/<semver>` APK is published) - **Freeze** the readiness doc. - New findings are **tracker issues only** — do **not** append to the Known issues table. - Document/Ignore classification for new surprises happens via ordinary triage, not readiness edits. Recorded as section **Playtest feedback path** in `docs/1.0-beta-readiness.md`.

TheAnachronism closed this issue

2026-08-04 19:35:32 +00:00

TheAnachronism referenced this issue

2026-08-04 19:35:33 +00:00

1.0 beta release readiness #41