<!-- Add Title: Artifact Registry - Sprint W#: YYYY-MM-DD – YYYY-MM-DD --> **Previous sprint:** https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/46 **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 | |------------|------------|---------|-----|-----------|--------|-------|---------------| | Storage | https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/7+ | https://gitlab.com/gitlab-org/ops/artifact-registry/-/merge_requests/108+ | `@vespian_gl` | `@hswimelar` | 🟡 At risk | Critical-path foundation item; minimum-foundation focus is **S06 first**. | Focus W20 on **delivering S06**; if viable, land **interfaces + stub driver first** to unblock OCI core, with real drivers later. | | Conformance Tool | https://gitlab.com/gitlab-org/gitlab/-/work_items/598527+ | [S05](https://gitlab.com/gitlab-org/ops/registry-conformance/-/merge_requests/21), [S06](https://gitlab.com/gitlab-org/ops/registry-conformance/-/merge_requests/25) | `@radbatnag` | `@mkhalifa3 @sylviashen @jtapiab` | 🟢 On track | Required for implementations, but only in a reduced scope that directly supports the **foundations-first / OCI-core** path. | Keep W20 work limited to conformance/tooling that directly validates or unblocks the **foundations-first / OCI-core** path. | | 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` | :red_circle: Blocked | Pathfinder stream; **OCI core only**, not full vertical slice. | Rescope W20 to **OCI core** and resume implementation against the new foundation scope; defer OCI-specific edge cases to Phase 3. | | 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; broader implementation should wait for proven foundations. | Keep W20 focused on **spec/review/planning** and small implementation planning, not a broad backend push, unless it directly helps unblock foundations or OCI core. | | npm Local | https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/22+ | S11 | `@dmeshcharakou` | `@sylviashen @adie.po @radbatnag` | 🟢 On track | Implementation plan is under development and includes temporary solutions for the unfinished foundational work. | Keep W20 focused on **spec/review/planning** and small implementation planning, not a broad backend push, unless it directly helps unblock foundations or OCI core. | | Frontend | | S26 | `@rchanila` | `@fmccawley` | :question: | Deprioritized for W20 under the minimum-foundation / OCI-core sequencing. | No W20 deliverable expected here; revisit after **foundations + OCI core** are stable. | | Tooling | https://gitlab.com/gitlab-org/ops/artifact-registry/-/work_items/26+ https://gitlab.com/gitlab-org/ops/artifact-registry/-/merge_requests/206+ | S27, S05 | `@suleimiahmed` | | 🟢 On track | Spec in Review; **background jobs** are deferred beyond the minimum-foundation set. Spec in Review: **distributed state**| Keep S27 & S05 review moving if inexpensive, but **background jobs and redis are not a primary W20 deliverable** under the revised plan. | **This week's expected outputs** (MRs merged or ready for review by Friday): * [ ] Storage: **S06 path confirmed with DRI** and first S06 deliverable (**interfaces + stub driver**, if viable) merged or ready for review. * [ ] Foundations: **structured logging** MR merged or ready for review. * [ ] Foundations: **auth stub** MR merged or ready for review. * [ ] Container Registry Local: **OCI plan rescope to core path** is reflected in execution, and **OCI core** implementation is resumed or restructured against the new foundation scope. * [ ] In-flight specs: **spec MRs are triaged** so **S06** remains the critical path, **S08** scope is narrowed to the stub, and non-minimum specs are explicitly deprioritized. * [ ] Review model / workflow: **operator/reviewer pairs** are identified and focus time blocks are set up for the active workstreams. * [ ] Review tooling: **/review-branch** skill is created or ready for initial team use locally. * [ ] Delivery guardrails: **500 LOC gate** in the Claude Code harness is implemented or ready for review. * [ ] Team operations: **maintainer pool expansion** is proposed or enacted to reduce merge bottlenecks. **Explicitly not expected outputs for W20:** * [ ] Broad Maven / npm implementation progress beyond spec/review/planning. * [ ] S27 / background jobs as a primary weekly deliverable. * [ ] Conformance expansion beyond direct support for the foundations-first / OCI-core path. * [ ] Frontend implementation work as a primary W20 deliverable. --- ## Sources - [Artifact Registry - Proposal for a v2 Delivery Approach](https://docs.google.com/document/d/1qzh1ntBEZrfGahnEsMKPWVxtnJ4Yjw1Bw5MdBxXNdBo) - [docs(roadmap): W18 status, W19 refresh, W20 placeholder](https://gitlab.com/gitlab-org/ops/artifact-registry/-/merge_requests/146) --- ### 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 | 12 | 5 | ↑ +7 | | MRs open / in review | 6 | 12 | ↓ −6 | | Review queue depth (oldest open MR, days) | 17 | 20 | ↓ −3 | | Specs approved (of total needed) | 8 / 26 | 3 / 28 | ↑ +5 | | Workstreams on track | 4 / 7 | 4 / 7 | → | | Active blockers | 4 | 3 | ↑ +1 | --- ## Blockers > Age = days since created / days to resolution. Owner = person responsible for resolution. | Blocker | Owner | Age (days) | Status | |---------|-------|------------|--------| | S06 spec: FIPS/MD5 open question (how MD5 checksum headers behave in FIPS mode for redirect downloads) | @vespian_gl / @mkhalifa3 | ~3 | Pending input from @mkhalifa3; blocking spec merge | | S06 stub: process overhead (plan MR + 3 impl MRs = 4–5 calendar days) | @vespian_gl | ~1 | !209 proposes fix (optional plan MRs, stacking); in review | | OCI core foundational work blocking Container/OCI local impl | @hswimelar | ~14 | Active; no concrete resolution date | | API ADR missing CRUD APIs for org namespace lookup — blocking Frontend spec (S26) | @rchanila | ~21 | Tracked in gitlab-org/gitlab#590367; ADR MR open (handbook!19696) | --- ## 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 — HTTP server and routing | ✅ Implemented | | | | S02 — CLI | Planned | | | | S03 — Logging conventions | Draft | | | | S04 — Database | ✅ Implemented | | | | S05 — Distributed state | ✅ Approved | Tooling | !206 merged this week, unblocking plan/impl | | S06 — Storage layer | Draft | Storage | Listed as Planned in README but !108 is in active review — should be updated to Draft | | S08 — Authentication (stub) | Draft | | | | S09 — Authorization (stub) | ✅ Approved | | | | S10 — Maven local | ✅ Approved | Maven local | !120 merged this week | | S11 — npm local | Draft | npm local | !98 in final review | | S12 — Container/OCI local | ✅ Approved | Container/OCI local | Spec done; impl blocked on foundational work | | S13 — Virtual and remote foundation | Planned | | | | S14–S16 — Maven/npm/Container virtual | Planned | | | | S17–S25 — Management API, tracking, lifecycle, etc. | Planned | | | | S26 — Deployment | Planned | Frontend | Spec blocked on API ADR update | | S27 — Background jobs foundation | ✅ Approved | Tooling | !122 merged this week | --- ## 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. * S06 spec not yet merged at end of W20 — FIPS/MD5 open question unresolved. Stub hasn't started. This is the critical-path item for the OCI core path and the slip carries into W21. * Container/OCI local impl still at 0% plan progress — foundational blocker carried from W19 with no concrete resolution date. * Frontend spec (S26) remains blocked on the API ADR update (~3 weeks old). No movement this week. --- ## Decisions Made This Week > Decisions that affect architecture, scope, or process. Each one should reference an ADR or be flagged for ADR creation. * !195: Documentation pairing convention codified (merged, @jdrpereira) * !196: Benchmarks now required for skill changes (merged, @jdrpereira) * !197: Agentic-workflow label process documented (merged, @jdrpereira) * !209: Proposal to make plan MRs optional and allow stacking to reduce process overhead for S06 stub — in review, not yet decided --- ## Next Week Preview > What each workstream is targeting next week. Populated Monday; updated if priorities shift. | Workstream | Target output | DRI | Dependencies | |------------|---------------|-----|--------------| | Storage | Merge S06 spec (!108); start stub impl | @vespian_gl | FIPS/MD5 question resolved; !209 outcome | | Container/OCI local | Unblock foundational work; begin plan MR | @hswimelar | OCI core items | | Maven local | Begin plan MR following S10 spec merge | @mkhalifa3 | None known | | npm local | Merge S11 spec (!98); begin planning | @dmeshcharakou | None known | | Tooling | Begin S27 plan MR (gated on spec, now unblocked) | @suleimiahmed | None | | Conformance tool | Merge S05 Maven plan (!21); progress S06 npm (!25) | @radbatnag | None known | | Frontend | Resolve API ADR blocker (gitlab-org/gitlab#590367) | @rchanila | GitLab issue response | Any capacity constraints? Planned PTO? - ... --- ## Retrospective Notes > What worked, what didn't, what to change. Feed recurring items into the AI-Augmented Practices doc. ## **What worked:** ## **What didn't:** ## **Process changes to consider:** * !209 (optional plan MRs, stacking) — if merged, addresses a recurring process overhead complaint worth tracking as an improvement --- ## Closing Checklist * All workstream DRIs posted async updates on their issues * [x] Metrics table filled in * [x] Blockers table current * [ ] 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 ``` Walk git log --first-parent main between {YYYY-MM-DD} and {YYYY-MM-DD} in the project gitlab-org/ops/artifact-registry. List all MRs merged in that window with title, author, and merge date. Filter to feat:, fix:, and docs: prefixes only. Add a single line at the end: "Other changes: N merged" covering chore:, ci:, revert:, and bot-authored dependency bumps. ``` Review Queue ``` List all open, non-draft merge requests in gitlab-org/ops/artifact-registry that have been open for more than 2 days. Exclude Renovate/bot-authored MRs. Include title, author, created date, and days open. Sort oldest first. State the oldest open MR at the end. ``` Spec Coverage ``` Read the file docs/specs/README.md in the repository gitlab-org/ops/artifact-registry. List all specs with their current status (Planned, Draft, Approved, Implemented). Count how many are in each status. Note any specs that have open MRs in review but are still listed as Planned in the README. ``` Workstream Status ``` Read the async update threads posted as comments on issue {SPRINT_ISSUE_URL} this week. For each workstream, summarize: completion percentage, current status emoji, and any blockers mentioned. ``` Age of blockers ``` From the async update threads on issue {SPRINT_ISSUE_URL}, list any mentions of blockers, dependencies on other teams, or open questions that must resolve before an implementation MR can open. Include workstream, owner, estimated age, and current status. Note any 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 (feat/fix/docs count + other count), workstreams on track vs. at risk vs. blocked, active blocker count, and the single biggest risk or win this week. Keep it under 60 words. End with: Sprint W{N+1}: {link} ``` </details>