...
These dates occur during several different development cycles, but all affect the Quesnelia OST page.
| Date | Triggering Event | Date Listed on | OST Page Action |
|---|---|---|---|
| 2023-04-10 | Orchid (X - 2) becomes GA. | The Orchid (X-2) release page | TC creates the DRAFT page for Quesnelia |
| 2023-09-08 | Quesnelia (X) release scope composition deadline | The Poppy (X-1) release page | TC transitions Quesnelia from DRAFT to ACCEPTED |
| 2024-03-15 | Quesnelia (X) feature development freeze | The Quesnelia release page | TC transitions Quesnelia from ACCEPTED to ACTIVE |
| 2024-late | Sunflower (X + 2) becomes GA | The Sunflower release page | TC transitions Quesnelia from ACTIVE to ARCHIVED |
Example TC Actions during Quesnelia ('X') Release Cycle
These dates are all listed on the Quesnelia page & occur during its development cycle, but affect several different OST pages.
| Date | Triggering Event | OST Page Action |
|---|---|---|
| 2024-02-16 | Ramsons (X + 1) release scope composition deadline | TC transitions Ramsons (X + 1) from DRAFT to ACCEPTED. |
| 2024-03-15 | Quesnelia (X) feature development freeze | TC transitions Quesnelia (X) from ACCEPTED to ACTIVE |
| 2024-04-29 | Quesnelia (X) becomes GA | TC transitions Orchid (X - 2) from ACTIVE to ARCHIVED and TC creates the DRAFT page for Sunflower (X + 2) |
Open Questions:
- Timelines - What are the relevant milestones in the release cycle for moving a page from one status to another?
- Do we want a single status for the current release + releases still in support periods? Or do we want multiple status for these?
- Do we even need status at all? Can we instead lean on the approval/review dates?
- What exactly does the process look like?
- In terms of "communicating changes to the TC
- wrt workflow/state transitions
- etc.