Milestone 16.10 review and discussion (Package stage)
🚀 (FEB 15 - MAR 21)
Milestone 16.10
🎯
Goals - Complete the integration with Google Artifact Registry on schedule.
- Continue to roll out the new list tags API for the container registry to improve UX.
- Advance the npm dependency proxy.
- Unblock self-managed customers from migrating to the new container registry.
- Tackle breaking changes in preparation for %17.0.
P1 (Deliverable) Issues 🦊
Please remember to make time in each milestone for learning and personal projects in addition to the below list.
Security Issues
There are no current security issues. Nice job everyone!
Breaking changes
_We've learned from previous major milestones that it's important to work proactively to ensure breaking changes are removed smoothly. We have two issues planned for this milestone from the epic.
-
Migrate packages and registries graphql to add ... (#390754 - closed) -
Dependency proxy can be accessed with PATs that... (#426887) -
Change the npm package upload from sync to async (#433009 - closed)
🔍
Investigations This month we have an investigation for a confidential
issue.
Container Registry
_This milestone, we'll continue to make progress on our main projects.
-
GraphQL: get GAR artifact details query (#425150 - closed) -
Refactor Artifact Registry integration to depen... (#439206 - closed) -
GAR integration documentation (#425158 - closed) -
confidential -
confidential -
Use new container registry API for `Get details... (#432471 - closed) -
Container Registry: allow setting database conf... (gitlab-org/charts/gitlab#5292 - closed) -
refactor: remove traces of FS mirroring behavior (container-registry#997 - closed) -
Discover Cells 1.0 impact for container_registry (#434985 - closed) -
Refactor Artifact Registry integration to depen... (#439206 - closed) -
Make Artifact Registry integration UI match the... (#439371 - closed) -
GAR integration: CI component for image replica... (#435205 - closed) -
GAR integration: frontend menu entry and list o... (#425154 - closed) -
GAR integration: frontend artifact details page (#425157 - closed) -
Use new container registry API for `List regist... (#432470 - closed) -
Enabling GitlabApiClient.repository_details for... (#434601 - closed) -
OCI Comformance are failing with latest distrib... (container-registry#1200 - closed)
Package Registry
This milestone we'll continue to improve Terraform, Maven, and npm.
-
NPM dependency proxy: implement the download tg... (#435644 - closed) -
Create Golang package class (#435830 - closed) -
Add a background worker to index the terraform ... (#438058) -
Discover Cells 1.0 impact for package_registry (#434984 - closed)
Dependency Proxy
There may be some spillover issues from 16.9. Stay tuned!
Stretch goals
Stretch goals are good to work on between Deliverable issues.
-
[container registry migration] Remove backend r... (#409873) -
NPM dependency proxy: implement the upload endp... (#441267) -
High database cpu usage for ContainerExpiration... (#440874 - closed)
Research issues
Issue Refinement
The issues below need refining to schedule them in subsequent milestones.
Assigned | Completed | Issue |
---|---|---|
|
||
|
|
|
|
|
🎥
Kick-off video
🌴
Holidays
Please order by From date
Person | From | To |
---|---|---|
Everyone (Summit) | March 11 | March 15 |
📦
Capacity
Helpful links
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 |
Operational tasks
-
PM: Create this issue with the title "Milestone XX.Y review and discussion (Package stage)" -
PM: Assign the issue to PM, EM, SET, and PD -
PM: Set the due date to the end of the milestone -
PM: Update links with the correct milestone -
PM: Write goals, list deliverables, community contribution, and stretch issues that align to the goals -
SET: List quality issues -
PD: List usability improvement issues -
PM: List research issues -
EM: List issues needing refinement -
EM: Review that all issues listed as deliverables are refined. If there is missing weight, implementation plan, and/or workflowready for development label, then ping the team to perform refinement -
EM: For issues that are refined and labeled as Package:P1, assign Deliverable and ~"Track Health Status" labels -
EM: Confirm the list of issues in this issue match with the ones in the filter. -
EM: Confirm there is enough work for golang engineers, rails engineers, and frontend engineers, and capacity is not exceeded. Can use the functional breakdown board to evaluate weights and coordinate with the team to confirm they feel comfortable with the commitments. -
EM: Record a comment like this with the total weight, average, and type of issues ratio and update the table in this issue -
PM: Record the kickoff video, link to this issue, and share it on Slack.
This issue was generated using the Package:Package Registry milestone plan template.