Draft: 16.0 Manage:Organization Planning
16.0 Planning for ~"group::organization"
Internal Milestone 16.0 Review & Discussion
Boards
- Planning board
- Build board
- Validation board
- Cross-functional prioritisation board
- Bug board
- Milestone priorities
- Release posts
Goal for this milestone
- Improve on error budget: focus on Projects List API
- Progress further on Consolidate memberships (gitlab-org&8010)
@mksionek)
Capacity (Team | Weight |
---|---|
backend | |
frontend |
Please take into consideration that several people will be out and one of the maintainers will be out for the whole milestone.
OOO
Objectives
typefeature list (@lohrc)
Product prioritized- Any %15.11 carryover
- Not started
- item
- At risk of slipping
- item
- Not started
- New feature work
- Namespace migration
- item
- Usability
- item
- Other
- item
- Namespace migration
typemaintenance list (@mksionek)
Engineering prioritized- Any %15.11 carryover
- Not started
- item
- At risk of slipping
- item
- New maintenance work
- Namespace migration
- item
- Other
- item
- Namespace migration
typebug list (@vburton)
Quality prioritized- Any %15.11 carryover
- Not started
- item
- At risk of slipping
- item
- New bugs
- Security
- item
- Namespace migration
- item
- Improve on error budget
- item
- Other
- item
- Security
Design preparation
- Organization proposal items
- item
- Feature improvements
- item
Release Post Items
Status | Issue | Release Post MR |
---|---|---|
Actions
-
Define an approximate scope for the coming release. - Apply appropriate labels to issues:
-
Priority -
Department -
Pricing Tier -
Direction
-
-
Review the proposed scope with Engineering. -
Review design objectives with UX. -
Get feedback and estimates from Engineering, confirming scope for the release. -
Final verification of issues scheduled for the release. -
Present selected issues in the Manage Kickoff on the 17th!
Edited by Christina Lohr