Release v1 0 - AnnabiGihed/RaidManager GitHub Wiki
Generated from
docs/planning/releases/v1.0.md. Edit that file in the repository: changes made in the wiki are overwritten.
The planning record of release v1.0, Rosters and raid night, kept as the Work Management and Delivery
Specification requires (§6, §14).
Draft awaiting owner approval. The owner asked the agent to split release 1 and set its dates (#339); the goal, criteria and scope below were drafted from Product scope and workflows and the epics. None of them is agreed until Gihed Annabi approves it.
| Field | Value |
|---|---|
| Version | v1.0 (repository milestone v1.0) |
| State | Draft: Planned once the owner approves it (§6) |
| Target date | 2027-03-19 (last day of Sprint 16, its stabilization sprint) |
| Actual delivery date | Not delivered |
| Approval | None yet |
Goal (draft)
Officers build, publish and run rosters through raid night, completing the version 1 product scope.
Acceptance criteria (draft)
- An officer creates a recurring raid, reviews candidates and lockout reasons, publishes one character per player, and later replaces an absent participant from the bench without rebuilding the raid (journey 4).
- At raid time, the officer checks attendance and exports the current roster to the addon for in-game invitations (journey 6).
- Before raid time, the player receives one reminder and can see boss assignments; afterwards, the officer can review attendance history and gear-readiness warnings for future planning (journey 7).
The repository's quality gates pass on the released version, and the stabilization sprint records its release checks below.
Scope (draft)
8 open outcome items, 41 Story Points estimated:
- #29 (user story) Review and filter raid candidates: 3 points
- #30 (user story) Build alternative compositions and a bench: 8 points
- #31 (user story) Show coverage and composition conflicts: 5 points
- #32 (user story) Review and publish one roster to Discord: 5 points
- #33 (user story) Check attendance and manage raid-night swaps: 5 points
- #34 (user story) Plan and copy boss-specific assignments: 5 points
- #35 (user story) Export the current roster to the WoW addon: 5 points
- #36 (user story) Review gear warnings and attendance history: 5 points
Their tasks share this milestone. Features and epics that also hold work of other releases carry no milestone (§15, A2).
Sprint sequence
| Sprint | Dates (Europe/Brussels) | Purpose |
|---|---|---|
| Sprint 13 | 2027-01-23 to 2027-02-06 (end exclusive) | Delivery |
| Sprint 14 | 2027-02-06 to 2027-02-20 (end exclusive) | Delivery |
| Sprint 15 | 2027-02-20 to 2027-03-06 (end exclusive) | Delivery |
| Sprint 16 | 2027-03-06 to 2027-03-20 (end exclusive) | Stabilization |
The dates assume 20 Story Points per two-week sprint, a conservative assumption until velocity exists (§9): 41 points fit in three delivery sprints, with time left for spikes, improvements and bugs.
Stabilization plan
Sprint 16: blocking defects, regressions, end-to-end validation of the acceptance criteria, documentation, release
notes, deployment and rollback preparation, planned as concrete items (work-stabilization-and-release-closure).
Scope decisions
| Date | Decision | Recorded on |
|---|---|---|
| 2026-10-02 | Release 1 split; the agent drafted this release's scope, sprints and target date at the owner's request. | #339 |
Readiness evidence
None yet.