Milestone 16.11 review and discussion (Package stage)
🚀 (MAR 21 - APR 18)
Milestone 16.11
🎯
Goals - Celebrate the completion of the beta launch of the Google Artifact Management integration on schedule.
- Advance the npm dependency proxy to help drive ARR.
- Add sorting and pagination to the container registry UI to help improve user experience.
- Unblock self-managed customers from migrating to the new container registry.
- Prepare for breaking changes in %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
Breaking changes
All breaking changes from the epic have been completed and are just waiting for feature flag removal in 17.0. Congrats team! And let me know if I missed any.
🔍
Investigations _This milestone we have planned three investigations for the container registry. First, adding background database migrations will help unblock Accept and record unknown media types (original... (container-registry#973 - closed) and move to GA for the next-generation container registry. The other two are investigations into a cleanup policy bug and the performance of the API.
-
Investigate strategy for enabling background da... (container-registry#221 - closed) -
Investigate the performance of the repositories... (#444463)(moved to 17.0) -
"Keep these tags" cleanup policy not working (t... (#428584)(moved backlog)
Container Registry
_This milestone, we have some exciting issues planned. We'll wrap up the instrumentation work in gitlab-org&8732, add the last published date into the UI, resolve issues with the OCI-conformance tests, and continue to drive adoption of the metadata database by unblocking self-managed customers and driving awareness of the beta program. We also have work scheduled for the public preview of the Artifact Management Integration.
-
confidential -
fix(notifications): retrying sink does not stop... (container-registry#1210) -
Document three-step migration process for Helm ... (#439684)(moved to 17.0) -
Display the last published date for container r... (#290949) -
Add metadata database banner to Registry pages ... (#442701 - closed) -
Run both 1.0.x and 1.1.x OCI conformance tests (container-registry#1206 - closed) -
Stale blob upload should return 204 (container-registry#1207 - closed) -
Retry previous blob chunk upload should return 416 (container-registry#1208 - closed) -
Instrument usage stats for the Google Artifact ... (#441693 - closed) -
Update the name of the integration to Google Ar... (#444825 - closed) -
GCP Integration: consolidate GCP jwt implementa... (#435739)(moved to 17.0) -
Consolidate guards around list and details oper... (#443518 - closed)(moved to 17.0) -
Use custom User-Agent for Google Artifact Regis... (#444752 - closed) -
[container registry migration] Remove backend r... (#409873) -
GAR integrations: Implement configuration test ... (#438560 - closed) -
https://gitlab.com/gitlab-org/gitlab/-/issues/439729+ -
UX improvements to Google Artifact Registry pages (#442151 - closed) -
Update Artifact Registry integration docs to me... (#450853 - closed)
Package Registry
This milestone we'll continue to drive forward several key projects. The first is the npm dependency proxy, which is expected to impact ARR and adoption significantly. We also will continue to make progress on adding support for Terraform module readme.md which is important for Platform Engineers who want to help their Developers use the module correctly and safely. It's also likely that there will be follow up work on the Artifact Management Integration, so please leave room for that.
-
confidential -
NPM dependency proxy: metadata cache update bac... (#435694) -
Better error messages for package processing er... (#330515 - closed) -
Support Nuget deprecation (#346150) -
Create Debian package class (#435831)
Stretch goals
Stretch goals are good to work on between Deliverable issues.
-
Validate JWT issued for moving a project within... (container-registry#1176 - closed) -
Add a new component to help understand ineffici... (#441951 - closed) -
Package: Package Registry Group documentation u... (#443450 - closed) -
Package: Container Registry Group documentation... (#443449 - 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 |
---|---|---|
Summit | March 11 | March 15 |
@rchanila |
March 18 | March 19 |
@dmeshcharakou |
March 18 | March 22 |
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.