...
STATUS | CHANGES | APPLIES TO NEW MODULES | TARGET RELEASE |
|---|---|---|---|
DRAFTYES | Security, 1st party, third party | NO | Future |
ACCEPTED | Security Only?, 1st party only | NO | Future |
ACTIVE | Security Only?, 1st party only | YES | Current Flower Release (In support)
|
ARCHIVED | NO | NO | Past Flower Release(Out of support) |
...
| Page Properties Report | ||
|---|---|---|
|
Timing of Upkeep Activities
- When release cycle milestones are published, the TC should plan the following activities
- When a release is GA, the TC should create the DRAFT for the release after the next
- E.g. at Poppy GA, the TC should create the DRAFT for Ramsons. The Quesnelia page would have been created when Orchid went GA.
- The TC should accept the draft for the next release prior to the release scope refinement deadline
- The TC should start reviewing the draft in the weeks leading up to this milestone
- The TC should transition ACCEPTED pages to ACTIVE when development begins on that release
- Roughly around the feature development freeze for the current release cycle.
- ACTIVE transitions to ARCHIVED when the release goes out of support
- E.g. at Poppy GA, Nolana is no longer supported, and should be ARCHIVED.
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.