Draft: 15.10 Manage:Organization Planning - Version 2.0
15.10 Planning for ~"group::organization"
Internal Milestone 15.10 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 | 22 |
frontend | 9 |
OOO
Objectives
typefeature list (@lohrc)
Product prioritized- Any %15.9 carryover
- Not started
- item
- At risk of slipping
- item
- Not started
- New feature work
- Namespace migration
- Organization buildout
- Other
typemaintenance list (@mksionek)
Engineering prioritized- Any %15.9 carryover
- Not started
- item
- At risk of slipping
- item
- New maintenance work
- Namespace migration
- item
- Other
- Namespace migration
typebug list (@vburton)
Quality prioritizedKey Dates:
-
By 4th of the month
, Quality provides PM with prioritization input for typebug issues per cross-functional prioritization -
Between 4th - 10th of the month
, quad discusses planned release items
Current Dashboard Metrics:
Click to expand
Dashboard link: https://app.periscopedata.com/app/gitlab/1037965/Bug-Prioritization
The dashboard has been adjusted to only consider customer labeled bugs with no S3 burndown plan at this time (see discussion below)
List of Prioritized Bugs:
Click to expand
Based on the plan to burndown S1 and S2 customer bugs while also allocating enough capacity for feature work, we should aim to complete at least 5 S2 customer bugs (see discussion below)
Bugs were prioritized in the following order:
- All customer / severity2 bugs at potential risk of slipping from 15.9
- Additional customer / severity2 bugs by age
- severity2 bugs at potential risk of slipping from 15.9
- Other severity2 bugs by age
- I've included more than 5 bugs in the list in case any of the bugs at risk of slipping do get complete in 15.9
Other notes:
- A group that someone is added to by way of memb... (gitlab-org/gitlab#331529 - closed) is currently blocked and has not been added to this list (see comment on MR)
- GroupMembersFinder returns elevated role for th... (gitlab-org/gitlab#377922 - closed) is blocking a severity2 customer bug API members/all missing some inherited members. (gitlab-org/gitlab#337623 - closed), so I've added this blocker to be prioritized in its place
- Group member access assignment to empty groups ... (gitlab-org/gitlab#267996) has not been included in this list as this POC would need to be completed first to identify a fix, which could also be a breaking change
- Error budget and performance issues not related to the Projects List API improvements have not been included, per our discussion below
typebug list
Finalized prioritized- Any %15.9 carryover
- Not started
- item
- At risk of slipping
- item
- New bugs
- Security
- item
- Namespace migration
- item
- Improve on error budget
- Other
-
1️⃣ Cross-site scripting in "Maximum page reached" ... (gitlab-org/gitlab#377970 - closed) milestonep1 -
1️⃣ Parent group is not shown first in search resul... (gitlab-org/gitlab#370771 - closed) milestonep2 -
3️⃣ Remove namespaces that have visibility levels a... (gitlab-org/gitlab#384358 - closed) milestonep2
-
- Security
Design preparation
- Organization proposal items
- Feature improvements
Release Post Items
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