... | ... | @@ -213,15 +213,15 @@ The stages of the Roadmapping Process at the Roadmap phase are: |
|
|
|
|
|
##### Roadmap.Communication
|
|
|
|
|
|
* The initiative is moved and adapted to become a part of the Release Roadmap.
|
|
|
* The issue is moved to a different repository, containing only the Approved Initiatives for the next release.
|
|
|
* The initiative is promoted as Epic so it can be coppied into the corresponding project roadmap automatically.
|
|
|
* The initiative is adapted and promoted to become part of the Oniro Platform Release Roadmap.
|
|
|
* The issue is moved from the initiative-incubation repository by promoting it (Gitlab terminology) as Epic to the subgroup initiative-release-roadmap.
|
|
|
* The initiative is adapted to be part of the Release Roadmap so it is consistent with other initiatives and it gets ready to be copied automatically into the engineering-roadmap subgroup at oniro-core project.
|
|
|
* The new initiative is communicated widely across the community through both mailing lists, oniro-wg and oniro-dev.
|
|
|
|
|
|
##### Roadmap.Backlog
|
|
|
|
|
|
* The newly promoted initiative as epic is copied to the project roadmap automatically, so it can be described and decomposed in tasks/issues (roadmap items) by tech leads/participants/committers.
|
|
|
* These roadmap items are owned by the projects.
|
|
|
* The newly promoted initiative as epic is copied automatically to the engineering-roadmap subgroup at oniro-core project, so it can be described and decomposed in roadmap items (user stories, engineering tasks) by committers and participants.
|
|
|
* These roadmap items are owned by the projects.
|
|
|
|
|
|
## Default cadence
|
|
|
|
... | ... | |