<!-- Add Title: Artifact Registry - Sprint W#: YYYY-MM-DD – YYYY-MM-DD --> **Previous sprint:** {link}\ **Roadmap:** [docs/roadmap.md](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/docs/roadmap.md) --- ## Workstream Plan | Workstream | Work Items | Spec(s) | DRI | Engineers | Status | Notes | Weekly Update | |------------|------------|---------|-----|-----------|--------|-------|---------------| | Conformance Tool | https://gitlab.com/gitlab-org/ops/registry-conformance/-/work_items/1+ https://gitlab.com/gitlab-org/gitlab/-/work_items/597641 | {spec} | @radbatnag | @mkhalifa3 @sylviashen @jtapiab | 🟡 At risk | Required for implementations | :x: / :white_check_mark: | | Storage Layer | https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/7+ https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/8+ | https://gitlab.com/gitlab-org/ops/artifact-registry/-/merge_requests/108+ | @vespian_gl | @hswimelar | 🟢 On track | Spec in review | :x: / :white_check_mark: | | Container Registry Local | https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/19+ | https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/docs/specs/S12-container-oci-local.md | @hswimelar | @vespian_gl | 🔴 Blocked | Implementation WIP | :x: / :white_check_mark: | | Maven Local | https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/16+ https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/21+ | S10 | @mkhalifa3 | @sylviashen @adie.po @radbatnag | 🟢 On track | Spec in review | :x: / :white_check_mark: | | npm Local | https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/17+ | S11 | @dmeshcharakou | @sylviashen @adie.po @radbatnag | 🟢 On track | Spec in review | :x: / :white_check_mark: | | Frontend | | S26 | @rchanila | @fmccawley | :question: | Not Started | :x: / :white_check_mark: | | Tooling | https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/26+ | S27 | @suleimiahmed | {} | :green_circle: On track | Spec in Review| :x: / :white_check_mark: | **This week's expected outputs** (MRs merged or ready for review by Friday): * Storage Layer: {specific deliverable} * [ ] Conformance Tools: Reviewed and merged * [ ] Storage Layer: spec in review * [ ] Container Registry Local: Implemented and reviewed * [ ] Maven Local: Spec merged, Implementation in progress * [ ] npm Local: Spec merged, Implementation in progress * [ ] Frontend: Spec started * [ ] Tooling: Background Jobs - spec merged ### Weekly Status Updates DRIs to post a weekly status update as a thread by EOD on Thursdays. Copy/Paste template below: ``` ## Workstream Weekly Update {Workstream Name} - [ ] Spec completion XX% -> Link to spec or work item - [ ] Plan completion YY% -> Link to plan - [ ] Implementation step 3 / 13 - MR #1 - MR #2 - ... - Status: 🟢 On track / 🟡 At risk / 🔴 Blocked - [ ] Workstream plan updated (work item description is up to date!) Notes: - XYZ... - Blockers: Pending ADRs / Missing designs / etc... ``` --- ## Metrics > Fill in Friday using the Duo queries in the companion reference. | Metric | This week | Last week | Trend | |--------|-----------|-----------|-------| | MRs merged | 5 | — | — | | MRs open / in review | 12 | — | — | | Review queue depth (oldest open MR, days) | 20 | — | — | | Specs approved (of total needed) | 3 / 28 | — / 28 | — | | Workstreams on track | 4 / 7 | — / 7 | — | | Active blockers | 3 | — | — | --- ## Blockers > Age = days since created / days to resolution. Owner = person responsible for resolution. | Blocker | Owner | Age (days) | Status | |---------|-------|------------|--------| | S27: River uses `pgx.Tx`, app query layer uses `database/sql` — cannot share atomicity. Three resolution paths documented in spec. | `@suleimiahmed` | 7 / — | Open — must resolve before implementation MR | | Container Registry Local implementation blocked pending S06 + S08 spec approvals | `@hswimelar` | 14 / — | Active — foundational specs still in review | | Conformance Tool Phase 1 not started; Phase 0 slipped ~1 sprint | `@radbatnag` | 7 / — | At risk — no external dependency | --- ## Spec Coverage > Updated when a spec moves to Approved status. Source: [docs/specs/README.md](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/docs/specs) | Spec | Status | Workstream | Notes | |------|--------|------------|-------| | S01 | Implemented | Conformance / foundations | HTTP server and routing | | S04 | Implemented | Foundations | Database | | S12 | Approved | Container Registry Local | Container / OCI local | | S03 | Draft | Foundations / Observability | Narrowed to logging conventions and merged this week via `!56` | | S06 | Planned | Storage Layer | In active review | | S08 | Planned | Auth / foundations | In active review | | S10 | Planned | Maven Local | In active review | | S11 | Planned | npm Local | In active review | | S27 | Planned | Tooling / Background Jobs | In active review | | S02, S05, S07, S09, S13–S26 | Planned | Various | Remaining planned specs | --- ## Changes From Last Week > What changed from what was planned. Be specific: what slipped, why, and what the downstream consequence is. If nothing changed, say so explicitly. * Container Registry Local slipped from implementation work to a foundations-first posture. Implementation is paused pending S06 and S08 approvals; revert MR `!161` merged. Downstream consequence: local container implementation is not moving forward until foundational specs land. * Conformance Tool Phase 0 slipped by about one sprint, and Phase 1 has not started yet. Downstream consequence: conformance support is lagging behind implementation needs. * Storage Layer progress paused mid-week while S12 reviews were handled, then resumed. Downstream consequence: S06 review progress continued, but more slowly than planned. * S03 was narrowed to logging conventions and merged this week, reducing scope for the observability foundation. --- ## Decisions Made This Week > Decisions that affect architecture, scope, or process. Each one should reference an ADR or be flagged for ADR creation. * S03 was narrowed to logging conventions via `!56`. _(Flag for ADR if this becomes the durable observability scope.)_ * Container Registry Local shifted to a foundations-first approach; implementation remains blocked on S06 and S08 approvals. _(Flag for ADR / delivery strategy record.)_ * Reference implementation reuse vs. AI rewrite policy was formalized via `!106`. _(Process decision.)_ --- ## Next Week Preview > What each workstream is targeting next week. Populated Monday; updated if priorities shift. | Workstream | Target output | DRI | Dependencies | |------------|---------------|-----|--------------| | Conformance Tool | Advance S04 consolidation MR and recover Phase 0 / Phase 1 plan | `@radbatnag` | Review capacity | | Storage Layer | Continue S06 review and drive toward approval | `@vespian_gl` | Reviewer / maintainer feedback | | Container Registry Local | Remain aligned to foundations-first path; resume only after S06 + S08 approvals | `@hswimelar` | S06 and S08 approval | | Maven Local | Finish maintainer review on S10 | `@mkhalifa3` | Maintainer review | | npm Local | Complete final review round on S11 | `@dmeshcharakou` | Final reviewer feedback | | Tooling | Resolve River / `pgx.Tx` vs `database/sql` atomicity question in S27 | `@suleimiahmed` | Architecture decision | | Frontend | Start workstream update / initial scoping | `@rchanila` | Capacity and scope alignment | --- ## Retrospective Notes > What worked, what didn't, what to change. Feed recurring items into the AI-Augmented Practices doc. ## **What worked:** * Async workstream updates made overall sprint status visible. * Five substantive MRs merged this week, including roadmap and spec/process updates. * S06, S10, S11, and S27 all made review progress. ## **What didn't:** * Review queue remains deep; oldest open MR is 20 days old. * Container Registry Local is blocked on foundational specs. * Conformance work slipped and Phase 1 has not started. * Frontend had no update posted this week. ## **Process changes to consider:** * Reduce review queue age on long-open docs/spec MRs. * Keep foundational approvals moving faster to avoid blocking downstream implementation. * Ensure every DRI posts an async update each week. --- ## Closing Checklist * All workstream DRIs posted async updates on their issues * [x] Metrics table filled in * [x] Blockers table current * [x] Roadmap updated at docs/roadmap.md * [x] Changes from last week documented * [ ] Next week's workstream targets confirmed with DRIs * [ ] Sprint summary posted to #f_artifact-registry Slack channel --- **Sprint summary for Slack** (copy-paste when closing): > Sprint W{N} closed. MRs merged: {N}. Workstreams on track: {N}/{total}. Blockers: {N}. {One sentence on biggest risk or win.} Sprint W{N+1}: {link} <details> <summary>Duo Queries</summary> MRs Merged This Week ``` Using the GitLab API, how many merge requests were merged in the project gitlab-org/ops/artifact-registry between {YYYY-MM-DD} and {YYYY-MM-DD}? List them by title, author, and merge date. ``` Review Queue ``` List all open merge requests in gitlab-org/ops/artifact-registry that have been open for more than 2 days and are currently awaiting review (not draft). Include title, author, created date, and days open. ``` Spec Coverage ``` Read the file docs/specs/README.md in the repository gitlab-org/ops/artifact-registry. List all specs with their current status (Draft, Approved, Implemented). Count how many are in each status. ``` Workstream Status ``` Summarize the recent activity on issue {ISSUE_URL} in gitlab-org/ops/artifact-registry. What was completed this week? Are there any blockers mentioned? ``` Age of blockers ``` Review all async updates posted as comments on issues in the milestone {MILESTONE_URL} this week. List any mentions of blockers, dependencies on other teams, or confidence drops below 70%. ``` Weekly Summary ``` Based on the sprint issue {SPRINT_ISSUE_URL}, write a one-paragraph Slack summary for #f_artifact-registry covering: MRs merged, workstreams on track vs. at risk, active blocker count, and the single biggest risk or win this week. Keep it under 60 words. ``` </details>