Milestone progress

Milestone progress

metalcloak/magento-dev · https://git.kub3.424cloud.net · generated 14 Oct 2026, 20:26 UTC

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

Time to launch · Hyvä launch

14–15working days

Projected finish between 3 Nov 2026 and 4 Nov 2026.

40 of 90 issues closed · 44.4%

50 still open

Time to full completion · all open milestones

20–22working days

Projected finish between 11 Nov 2026 and 13 Nov 2026.

145 of 218 issues closed · 66.5%

73 still open

Milestones

Last 10 closed

  1. #515M14Choose the standalone service's starting codebase: fork an existing Magento MCP server or build fresh14 Oct 2026
  2. #529M14Round-trip a Transfer Center bundle between two instances and check its styling13 Oct 2026
  3. #511M14Which Magento instance launch content is published to before launch13 Oct 2026
  4. #527M14Prove content round-trips between the Hyvä CMS editor and the API13 Oct 2026
  5. #526M14Inventory every storefront area that carries CMS content and how editable it is13 Oct 2026
  6. #228M11Survey Magento + Hyvä mechanisms for reusable admin content patterns12 Oct 2026
  7. #516M14Which image store the service uploads new images to: Magento media or images.metalcloak.com12 Oct 2026
  8. #508M14Choose the editor for each CMS content surface12 Oct 2026
  9. #451M14CMS content missing from the dataset: footer, subheader nav and side menu blocks9 Oct 2026
  10. #409M14M7 — Add store-specific checkout policy CMS blocks for sibling stores9 Oct 2026

Closed in the last 6 weeks

97 issues closed between 2 Sep 2026 and 14 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.

10

2 Sep

19

9 Sep

8

16 Sep

17

23 Sep

11

30 Sep

32

7 Oct

Milestone2 Sep9 Sep16 Sep23 Sep30 Sep7 OctTotal
M7···16310
M122·2·149
M14····12425
M11·····11
M8····1·1
Other8196162·51
All issues1019817113297

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

M7, M8, M9, M11, M14

14–15working days

Projected finish between 3 Nov 2026 and 4 Nov 2026.

40 of 90 issues closed · 44.4%

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, M13, M2, M9, Production.
  • Gitea's own counters disagree with the issue list for M14; pull requests are probably attached to those milestones. Only issues are counted here.
  • Launch group scope is suspect: M9 and M11 describe themselves as post-launch and not launch-blocking, yet are counted in 'Time to launch'. M9 (9 open, 0 closed ever) contributes only a borrowed rate.
  • M8 (Testing & Release Hardening, the release gate) has 16 open issues and one closure in the window: its own band is 16 to 368 working days at low confidence. The launch date cannot be earlier than M8 finishing.
  • The launch and board figures spread the whole team's throughput (~3.4–3.7 closures/day) across the group; they assume closures keep coming at the September–October pace, which was dominated by M14 and M7.

Milestone detail

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.

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

1–3working days

Projected finish between 15 Oct 2026 and 19 Oct 2026.

13 of 14 issues closed · 92.9%

1 still open

High confidenceMeasured rate

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

Last closure 7 Oct 2026, 23:19 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–10working days

Projected finish between 16 Oct 2026 and 28 Oct 2026.

48 of 51 issues closed · 94.1%

3 still open

Medium confidenceMeasured rate

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

Last closure 8 Oct 2026, 22:39 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

4–15working days

Projected finish between 20 Oct 2026 and 4 Nov 2026.

25 of 41 issues closed · 61%

16 still open

High confidenceMeasured rate

Measured from 25 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 14 Oct 2026, 04:22 UTC.

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

8–184working days

Projected finish between 26 Oct 2026 and 29 Jun 2027.

1 of 9 issues closed · 11.1%

8 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 12 Oct 2026, 22:10 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

16–368working days

Projected finish between 5 Nov 2026 and 13 Mar 2028.

1 of 17 issues closed · 5.9%

16 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.

M15milestone open

M15 — Post-Launch Enhancements

Enhancements intentionally deferred until after the Hyvä Launch. Work in this milestone does not block launch; existing release-blocking storefront behavior must still be preserved. Includes the future move from native HTML navigation content to visual authoring with Hyvä CMS / Menu Builder.

Estimated working days remaining

Complete

Nothing outstanding.

0 of 0 issues closed · no issues yet

0 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.

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 15 Oct 2026 and 20 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 15 Oct 2026 and 20 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–10working days

Projected finish between 16 Oct 2026 and 28 Oct 2026.

5 of 8 issues closed · 62.5%

3 still open

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

3–17working days

Projected finish between 19 Oct 2026 and 6 Nov 2026.

49 of 54 issues closed · 90.7%

5 still open

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

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 22 Oct 2026 and 25 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

6–33working days

Projected finish between 22 Oct 2026 and 30 Nov 2026.

3 of 13 issues closed · 23.1%

10 still open

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