Milestone progress

Milestone progress

metalcloak/magento-dev · https://git.kub3.424cloud.net · generated 15 Sep 2026, 21:15 UTC

Velocity measured over the last 30 days (16 Aug 2026 to 15 Sep 2026, 22 working days).

Working days to clear the board

27–29working days

83 issues outstanding across 12 milestones · All open milestones

Projected finish between 22 Oct 2026 and 26 Oct 2026.

144 of 227 issues closed · 63.4%

Rolled up at the repository's own closure rate, not the sum of the per-milestone rates below: the team works the board as one, and adding the cards together would count the same people once per milestone.

Group rollups

Each figure below assumes the whole team's current throughput goes to that group alone. Two rollups cannot both be true at once, and they cannot be added together.

Hyvä launch

M4, M5, M6, M7, M8

14–15working days

Projected finish between 5 Oct 2026 and 6 Oct 2026.

46 of 88 issues closed · 52.3%

Assumes the whole team's current throughput goes to Hyvä launch and to nothing else. It is not an independent forecast, and it cannot be added to another rollup on this page.

Advisories

  • Dormant with work outstanding — no closure inside the window: M1, M10, M11, M13, M2, M8, M9.
  • Gitea's own counters disagree with the issue list for M5, M6; pull requests are probably attached to those milestones. Only issues are counted here.
  • M8 — Testing & Release Hardening is on the Hyvä launch critical path with 15 open issues and no closure ever; its 10–30 working-day figure is borrowed from the median moving milestone, not measured. The Hyvä launch date above assumes M8 starts closing at that pace immediately.
  • M7 — Sibling Store Rollout has one closure in the window, so its 11–242 working-day band reflects how little is known, not a forecast. Do not quote a midpoint.
  • M1, M2, M10 have closed nothing since July; M9, M11, M13 are post-launch and have never closed an issue. Their dates are placeholders.

Milestones

Listed in the order the collector emitted them: measured estimates first, ordered by how soon they finish, with borrowed estimates last so the weakest numbers never head the list.

M4milestone open

M4 — Core Catalog — Category & Product

Implement the category listing page and the product detail page per the approved Hi-Fi designs, including all ArmoredWorks custom modules that couple to these surfaces.

Estimated working days remaining

2–4working days

Projected finish between 17 Sep 2026 and 21 Sep 2026.

14 of 16 issues closed · 87.5%

2 still open

High confidenceMeasured rate

Measured from 11 closures across 7 active days in the window (eight or more closures measured inside the window).

Last closure 2 Sep 2026, 23:35 UTC.

M12milestone open

M12 — Developer Onboarding Hardening

Make a fresh clone of this repository reach five verified working storefronts for a remote developer who has only their Gitea identity, via one interactive command, on Linux and WSL2.

Estimated working days remaining

2–6working days

Projected finish between 17 Sep 2026 and 23 Sep 2026.

41 of 46 issues closed · 89.1%

5 still open

High confidenceMeasured rate

Measured from 21 closures across 7 active days in the window (eight or more closures measured inside the window).

Last closure 4 Sep 2026, 20:49 UTC.

M5milestone open

M5 — Cart & Checkout

Implement the cart page and one-page checkout per the approved Hi-Fi designs, including all payment gateways, Rewards integration at checkout, and all custom checkout modules.

Estimated working days remaining

3–11working days

Projected finish between 18 Sep 2026 and 30 Sep 2026.

18 of 25 issues closed · 72%

7 still open

High confidenceMeasured rate

Measured from 15 closures across 6 active days in the window (eight or more closures measured inside the window).

Gitea's own counters disagree with this list: pull requests are attached to this milestone. Only issues are counted here.

Last closure 11 Sep 2026, 20:43 UTC.

M6milestone open

M6 — Login, Account & Pre-Launch Cleanup

Implement the login and account surfaces per the approved Hi-Fi designs. Validate required-login behavior. Complete the mandatory CMS theme-fit cleanup pass before launch.

Estimated working days remaining

6–14working days

Projected finish between 23 Sep 2026 and 5 Oct 2026.

11 of 18 issues closed · 61.1%

7 still open

High confidenceMeasured rate

Measured from 11 closures across 8 active days in the window (eight or more closures measured inside the window).

Gitea's own counters disagree with this list: pull requests are attached to this milestone. Only issues are counted here.

Last closure 15 Sep 2026, 19:03 UTC.

M7milestone open

M7 — Sibling Store Rollout

Extend the Hyvä implementation from MetalCloak to all four sibling stores (Carbon Offroad, KMS, Rocksport, Jobber Portal).

Estimated working days remaining

11–242working days

Projected finish between 30 Sep 2026 and 19 Aug 2027.

3 of 14 issues closed · 21.4%

11 still open

Low confidenceMeasured rate

Measured from 1 closure across 1 active day in the window (one or two closures measured inside the window).

Last closure 27 Aug 2026, 17:58 UTC.

M13milestone open

M13 — Post-Launch Performance & Caching

Performance and caching work deferred until after the Hyvä launch/deployment. Varnish full-page cache behaviour, CDN (Cloudflare) cache-hit rates, and post-launch performance regressions live here.

Estimated working days remaining

1–2working days

Projected finish between 16 Sep 2026 and 17 Sep 2026.

0 of 1 issues closed · 0%

1 still open

No confidenceBorrowed rateNever closed an issue

This milestone has closed nothing inside the window, so the estimate above is borrowed: it is the median rate of the milestones that are actually moving. It describes what a typical moving milestone would take, not what this one is doing. Treat it as a placeholder.

M1milestone open

M1 — Dev Environment Foundation

Migrate local development from Scandi CMA / WSL to Warden. Establish a one-command bootstrap, live reload for frontend iteration, a repeatable dataset restore workflow, and a documented environment/secret management approach.

Estimated working days remaining

2–4working days

Projected finish between 17 Sep 2026 and 21 Sep 2026.

5 of 7 issues closed · 71.4%

2 still open

No confidenceBorrowed rateNo closure in 68 days

This milestone has closed nothing inside the window, so the estimate above is borrowed: it is the median rate of the milestones that are actually moving. It describes what a typical moving milestone would take, not what this one is doing. Treat it as a placeholder.

M2milestone open

M2 — Discovery & Inventory

Achieve high certainty on every release-blocking surface, custom module, and third-party extension before any implementation issues are written.

Estimated working days remaining

4–10working days

Projected finish between 21 Sep 2026 and 29 Sep 2026.

49 of 54 issues closed · 90.7%

5 still open

No confidenceBorrowed rateNo closure in 53 days

This milestone has closed nothing inside the window, so the estimate above is borrowed: it is the median rate of the milestones that are actually moving. It describes what a typical moving milestone would take, not what this one is doing. Treat it as a placeholder.

M11milestone open

M11 — CMS Authoring System

Post-launch effort: a Hyvä-consistent CMS pattern library so employees create new CMS pages in the admin panel that match the launched UI. Planned via the Wayfinder map in this milestone; implementation issues are cut when the map's decisions are resolved. Sequenced after M6/M7 (launched theme + fixed CMS pages are the raw material).

Estimated working days remaining

6–18working days

Projected finish between 23 Sep 2026 and 9 Oct 2026.

0 of 9 issues closed · 0%

9 still open

No confidenceBorrowed rateNever closed an issue

This milestone has closed nothing inside the window, so the estimate above is borrowed: it is the median rate of the milestones that are actually moving. It describes what a typical moving milestone would take, not what this one is doing. Treat it as a placeholder.

M9milestone open

M9 — Privacy & Consent Hardening

Post-launch program to achieve Technical Consent Readiness across MetalCloak, Carbon Offroad, KMS, Rocksport, and Jobber Portal. Establish strict opt-in controls, synchronized cross-domain preferences, consent-aware optional technology loading, and evidence-based verification. This milestone does not block the Hyvä Launch and does not constitute legal certification.

Estimated working days remaining

6–18working days

Projected finish between 23 Sep 2026 and 9 Oct 2026.

0 of 9 issues closed · 0%

9 still open

No confidenceBorrowed rateNever closed an issue

This milestone has closed nothing inside the window, so the estimate above is borrowed: it is the median rate of the milestones that are actually moving. It describes what a typical moving milestone would take, not what this one is doing. Treat it as a placeholder.

M10milestone open

M10 — Analytics Modernization

Post-launch modernization of analytics across MetalCloak, Carbon Offroad, KMS, Rocksport, and Jobber Portal. Delivers a reliable measurement foundation after M9 consent hardening; it does not block the Hyvä Launch.

Estimated working days remaining

7–20working days

Projected finish between 24 Sep 2026 and 13 Oct 2026.

3 of 13 issues closed · 23.1%

10 still open

No confidenceBorrowed rateNo closure in 53 days

This milestone has closed nothing inside the window, so the estimate above is borrowed: it is the median rate of the milestones that are actually moving. It describes what a typical moving milestone would take, not what this one is doing. Treat it as a placeholder.

M8milestone open

M8 — Testing & Release Hardening

Execute the minimum release gate. Validate all release-blocking flows against staging. Deliver CI/CD foundations. Produce a signed-off go/no-go checklist for the Hyvä Launch.

Estimated working days remaining

10–30working days

Projected finish between 29 Sep 2026 and 27 Oct 2026.

0 of 15 issues closed · 0%

15 still open

No confidenceBorrowed rateNever closed an issue

This milestone has closed nothing inside the window, so the estimate above is borrowed: it is the median rate of the milestones that are actually moving. It describes what a typical moving milestone would take, not what this one is doing. Treat it as a placeholder.

How to read these numbers

Two rates, deliberately

The slow end spreads a milestone's closures over every working day in the window: the pace it holds if it keeps the share of attention it has been getting. The fast end spreads them only over the days that actually saw a closure: the pace it holds if nothing else is worked on. The truth sits between them. Neither end is a commitment.

Borrowed estimates

A milestone that closed nothing inside the window has no rate of its own, so it borrows the median rate of the milestones that are moving. That says what a typical moving milestone would take, not what this one is doing. Those cards are drawn weaker on purpose.

Issues only

Pull requests are excluded from every count and every rate. Where Gitea's own milestone counters disagree with the issue list, the card says so.

Working days

Monday to Friday, with no allowance for holidays, leave, or the days already lost to whatever else is on. Projected dates advance by working days from the generation date above.