Milestone 15.3 review and discussion
🚀
Milestone 15.3 Helpful links | Use this for |
---|---|
Functional breakdown | Viewing issues scheduled for the current and next several milestones. |
Milestone board | See how the planned issues are broken down by function. |
Workflow board | See how the milestone issues are broken down by their current status (workflow). |
List of P1 unweighted issues | A list of issues that are not yet weighted, which is a requirement for P1 issues. |
Issues that need refining | A list of issues that refinement |
Issue types by milestone | See the ratio of features, maintenance and bugs |
🌴
Holidays
Please order by From date
Person | From | To |
---|---|---|
Steve | July 16 | July 31 |
David | July 22 | July 29 |
Tim | July 25 | September 16 |
Steve | Aug 8 | Aug 8 |
David | Aug 8 | Aug 15 |
📦
Capacity
🕰
Past 3 milestone commitments Milestone | Deliverable issues planned | Deliverable issues delivered | Deliverable issues rescheduled | Average weight | Total weight |
---|---|---|---|---|---|
15.3 | 16 | 1.56 | 25 | ||
15.2 | 16 | 14 | 1.75 | 28 | |
15.1 | 16 | 10 | 1.68 | 27 | |
15.0 | 16 | 13 | 1.62 | 26 |
Please note that we have scheduled fewer items in 15.2 and 15.3 to help ensure that people can enjoy their vacations and that we don't overcommit.
🎯
Goals What are we doing, and why is it important?
- The number one priority is the Container Registry migration.
- The second priority is the performance improvements to the container registry cleanup policies.
- The third priority is resolving blocking issues for the dependency proxy.
P1 (Deliverable) Issues 🦊
Please remember to make time in each milestone for learning and personal projects in addition to the below list.
Security Issues
By prioritizing security-related issues, we can help reduce GitLab's threat landscape by:
- Reducing the likelihood of breach
- Reducing the exposure and severity of vulnerabilities
- Reducing the cost associated with service vulnerabilities
Container Registry
For the container registry, I'd like to continue with the focus on the migration and cleanup policies. For the latter, I'm excited about the expected performance improvements gained by adding the timestamp. In addition, we will continue the investigation into user-level data and make several usability improvements.
-
Migrate Paid tier images with more than 6000 tags to the new registry ~ 🚀 -
Migrate VIP customers to the new registry 🚀 -
Enable the use of Redis to cache database repository objects performance-refinement -
Update the GitLab Container Registry client to support the new API performance-refinement -
Introduce the new service with the new code path performance-refinement -
Investigate: How to add Container Registry User level data instrumentation -
Package project settings side-by-side layout usability -
Partial cleanup tooltip does not display time usability -
GlPopover component not displaying in all rows of the Container Registryusability
Dependency Proxy
There are two bugs that have been impacting the dependency proxy for the past several milestones. One is preventing users of Azure storage from using the feature and the other is blocking internal, dogfooding usecases.
Package Registry
For the Package Registry, I'm most excited about the RPM investigation, although this may come off the list if we don't get budget approval for the external contractor. Also, the settings UX improvements will help unblock many future improvements to the Package settings.
-
Cleanup policy objects + background job for execution -
Clean up package files MVC design/frontend issue -
Investigate how to add support for RPM to the Package Registry -
Investigate: Automated package imports (Artifactory) -
Give the job token access to the Packages API customer -
Package duplicate settings UI update for side-by-side layout usability -
Bulk delete package assets from the UI customer
Stretch goals
_Stretch goals are good to work on once you have finished or have time between your P1 issues. _
-
Introduce a switch (based on the repository migration status) -
[Feature Flag] Performance improvements for cleanup policies -
Investigate: Incorrect statistics for packages -
Some NPM packages published in multiple projects are inaccessible -
Move container registry cleanup policies to a single page
Quality & quad-planningcomplete-action
Reviewed issues with actions:
Issue Refinement
Each milestone we want to ensure that we allow time to review, discuss, and weight issues. The goal is to ensure that the issue is ready for development before planning it for a given milestone.
Research
Issue | Deliverable |
---|---|
Package Touchpoint research | Record 3 customer interviews |
Understand pain points of registries being tied to a project | Analysis complete |
Refine the package detail page | Analysis complete |
Design
Design work for this milestone is captured on design issue