Milestone progress

Milestone progress

metalcloak/magento-dev · https://git.kub3.424cloud.net · generated 7 Oct 2026, 16:35 UTC

Velocity measured over the last 30 days (7 Sep 2026 to 7 Oct 2026, 23 working days).

Working days to clear the board

23–27working days

68 issues outstanding across 14 milestones · All open milestones

Projected finish between 9 Nov 2026 and 13 Nov 2026.

187 of 255 issues closed · 73.3%

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.

Closed in the last 6 weeks

88 issues closed between 26 Aug 2026 and 7 Oct 2026.

Seven-day buckets ending on the generation date, each labelled by its first day. “Other” is issues in milestones not shown on this page, or in no milestone.

23

26 Aug

10

2 Sep

17

9 Sep

8

16 Sep

16

23 Sep

14

30 Sep

Milestone26 Aug2 Sep9 Sep16 Sep23 Sep30 SepTotal
M441··6213
M5·21028224
M61575··18
M71····78
M12122··2117
M14·····11
M8·····11
Other5··1··6
All issues2310178161488

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

6–8working days

Projected finish between 15 Oct 2026 and 19 Oct 2026.

85 of 103 issues closed · 82.5%

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, M9, Production.
  • Gitea's own counters disagree with the issue list for M4, M5, M6; pull requests are probably attached to those milestones. Only issues are counted here.
  • Hyvä launch: the 6–8 working-day figure applies the whole team's rate (about 2.5–3.1 closures a day) to the 18 issues left. 45 of the group's 53 closures in the window came from M4, M5 and M6, which now have nothing open. Every remaining issue is in M7 (3) or M8 (15), and M8 has closed 1 issue in the window. Read the launch date as the result if the whole team turns to M8. At M8's own pace it is 15 to 345 working days.
  • Low confidence: M8 and M14 each have a single closure in the window behind them, which is why their bands are so wide. M12's band (4–47 days) rests on 3 closures over 2 active days.
  • All open milestones: the 23–27 day board figure applies the whole team's rate to 68 open issues. 37 of those sit in dormant milestones, and M9, M10, M11 and M13 are explicitly post-launch. The board figure answers 'if all of it were worked at today's pace', not 'when it will be done'.
  • M4, M5 and M6 have no open issues but are still open milestones in Gitea. This report reads the tracker and changed nothing.
  • Window: the default 30 days. Weekly closures have held between 8 and 23 for six weeks, so the window was not widened.

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

Complete

Nothing outstanding.

22 of 22 issues closed · 100%

0 still open

High confidenceMeasured rate

Measured from 8 closures across 5 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 30 Sep 2026, 21:28 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

Complete

Nothing outstanding.

34 of 34 issues closed · 100%

0 still open

High confidenceMeasured rate

Measured from 24 closures across 12 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 1 Oct 2026, 21:26 UTC.

M6milestone open

M6 — Login & Account

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

Complete

Nothing outstanding.

18 of 18 issues closed · 100%

0 still open

High confidenceMeasured rate

Measured from 13 closures across 7 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 22 Sep 2026, 19:31 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

2–10working days

Projected finish between 9 Oct 2026 and 21 Oct 2026.

10 of 13 issues closed · 76.9%

3 still open

Medium confidenceMeasured rate

Measured from 7 closures across 3 active days in the window (three to seven closures measured inside the window).

Last closure 5 Oct 2026, 23:45 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

4–47working days

Projected finish between 13 Oct 2026 and 11 Dec 2026.

44 of 50 issues closed · 88%

6 still open

Medium confidenceMeasured rate

Measured from 3 closures across 2 active days in the window (three to seven closures measured inside the window).

Last closure 6 Oct 2026, 21:58 UTC.

M14milestone open

M14 — Homepage, CMS & Content Theme-Fit (Pre-Launch)

Pre-launch theme-fit and compatibility work for CMS pages, CMS blocks, the homepage redesign, and content surfaces. Split out of M6, which is now login/account only. Per-store repeat of this sweep stays in M7 (#104).

Estimated working days remaining

7–161working days

Projected finish between 16 Oct 2026 and 20 May 2027.

1 of 8 issues closed · 12.5%

7 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 6 Oct 2026, 23:09 UTC.

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

15–345working days

Projected finish between 28 Oct 2026 and 2 Feb 2028.

1 of 16 issues closed · 6.2%

15 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 5 Oct 2026, 23:36 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–4working days

Projected finish between 8 Oct 2026 and 13 Oct 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.

Productionmilestone open

Production Hotfixes

Follow-up work from production incidents: land vendor hotfixes in package source, release through the normal dependency workflow, add regression coverage.

Estimated working days remaining

1–4working days

Projected finish between 8 Oct 2026 and 13 Oct 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–7working days

Projected finish between 9 Oct 2026 and 16 Oct 2026.

5 of 7 issues closed · 71.4%

2 still open

No confidenceBorrowed rateNo closure in 90 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–17working days

Projected finish between 13 Oct 2026 and 30 Oct 2026.

49 of 54 issues closed · 90.7%

5 still open

No confidenceBorrowed rateNo closure in 75 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–30working days

Projected finish between 15 Oct 2026 and 18 Nov 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–30working days

Projected finish between 15 Oct 2026 and 18 Nov 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–33working days

Projected finish between 16 Oct 2026 and 23 Nov 2026.

3 of 13 issues closed · 23.1%

10 still open

No confidenceBorrowed rateNo closure in 75 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.

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.