## Q2 MVP Timeline Estimate – Artifact Registry modular service (DRAFT) | Weekly Sprint Dates | Iteration objective | Primary focus (AR functionality) | |-------|---------------------|----------------------------------| | Mar 23-27 | Cross-team Dependencies and ADRs | Assign cross-team DRIs, Document decisions that need to be made in ADRs | | Mar 30-Apr 3 | Cross-team Dependencies and ADRs | Finalize Artifact Registry foundational ADRs, align on cross-team implementation timelines and integration points | | Apr 6–10 | Service foundation (week 1) | Service skeleton, select golang libraries, storage wiring, DB setup, base schema | | Apr 13–17 | Service foundation (week 2) | Virtual registry foundational dependencies, Maven VR translation prompts | | Apr 20–24 **Fastboot** | Maven Virtual Registry service deployment | Maven virtual registry translation and deployment, feature parity with monolith | | Apr 27–May 1 | Virtual registry deployment - other formats | Npm + Docker virtual registry translation, monolith to service data migration plan | | May 4–8 | Organization management (week 1) | AuthN/AuthZ wiring, unified artifact list API | | May 11–15 | Organization management (week 2) | Configuration, pricing integration, storage management | | May 18–22 | Unified artifact list (backend) | APIs, GraphQL endpoints | | May 25–29 | Unified artifact list (frontend) | Monolith FE development, GraphQL | | Jun 1–12 | MVP readiness, PREP reviews | E2E testing, dogfooding, runbooks, docs, feedback/bug fixes |