14.5 planning - Composition Analysis (October-November)
🔗
Helpful Links Click to expand...
- How we work
- Slack channel: #g_secure-composition-analysis
- Bug Board
- Performance Indicators
-
Planning Board for checking Deliverable/
Stretch/"Next Patch Release" - Dev workflow Board for checking workflowscheduling and workflowready for development
- Backend Board
- SCA Categories Board
- All Secure Issues
- All CA Issues
- All Backend CA issues
- All Frontend CA issues
- CA priorities for the year 2021
- 14.3 Planning Issue
Context
Capacity variations
nicole aim for like 15 issues (assuming spillover or high priority finds)
This includes planned OOO, internships, conferences and other initiatives outside of groupcomposition analysis.
-
backend => ~ 45%
- Fabien: 75% (allocating ~4 days for security issues refinement)
- Igor: 0% (Manage:Import Headcount Reset)
- Tetiana: 25% (reaction rotation + allocating ~4 days for security issues refinement)
- Adam: 75% (allocating ~4 days for security issues refinement)
-
frontend
Items slipping from the previous release
This is a rough list of the items that may have a significant impact on that release (no need to be an exhaustive list).
...
Product Goals in priority order
Q3 Direction - GitLab Hosted First - which we have taken on to mean a variety of improvements related to Performance, Reliability, Availability |
Q4 - finish up bugs and performance improvements, finish up auto remediation, do display dependency path mvc and re-test CMS, and start on LF replacement and SBOM
Implement as follows
Feature | Links | Notes |
---|---|---|
Reaction rotation | triage incoming bugs, security, customers, community contributions. use timeboxing. | |
|
must do within SLO | |
|
must do within SLO, start with P1, if none move to P2, if none move to P3. P3 can miss SLO for now | |
|
filled in as we have space | |
|
pickup query | please allot 4 days |
|
Unification of backend for CE & EE | high priority - partner with frontend |
|
Security Configuration page never shows info alert about Auto DevOps, and Configuration history link is erroneously shown | high priority - should be backend only |
|
update and scan our tools as updates are available | high priority - update tools if applicable and desired (we have intentionally decided against some specific updates) |
15.0 Deprecations and Removals - SCA | ||
OKR-Personal Growth project | please try to put some time against this | |
OKR-hiring | please prioritize this is you are tapped to help | |
OKR-psychological safety training | here and here | try to make some time for this |
OKR-UX | TBD | TBD |
OKR-QA | TBD | TBD |
OKR-error budget | TBD | TBD |
FILL IN (if room)
Click to expand...
| Feature | Links | Notes | | ------ | ------ | ------ | |- P3 Low priority
- P4 Low priority
- security no priority triage
Please work the above in order. If something of a higher category comes in you can feel free to swap it for a lower item (cc Nicole and Oliver). If it does not fall into one of the above and you think it can wait please place in %Backlog - if you feel it should be strongly considered for an upcoming release please place in %Next 1-3 releases
Feel free to use the following message Product has determined that for Q3 our priority is related to the Direction [GitLab Hosted First](https://about.gitlab.com/direction/#gitlab-hosted-first) and as a result, we are only focusing on reliability, performance, and availability related items. Unfortunately, this issue does not qualify and will have to be evaluated after Q3 when we begin populating Q4. Upvoting and commenting on issues is the best way to make sure it is considered high priority as backlog items begin to be brought back in.