Milestone progress
Velocity measured over the last 30 days (3 Aug 2026 to 2 Sep 2026, 23 working days).
Working days to clear the board
32working days
91 issues outstanding across 12 milestones · All open milestones
Projected finish 16 Oct 2026.
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.
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.
M4, M5, M6, M7, M8
19working days
Projected finish 29 Sep 2026.
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.
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.
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
1working day
Projected finish 3 Sep 2026.
Measured from 26 closures across 10 active days in the window (eight or more closures measured inside the window).
Last closure 1 Sep 2026, 23:53 UTC.
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–6working days
Projected finish between 4 Sep 2026 and 10 Sep 2026.
Measured from 13 closures across 8 active days in the window (eight or more closures measured inside the window).
Last closure 29 Aug 2026, 00:19 UTC.
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
5–28working days
Projected finish between 9 Sep 2026 and 12 Oct 2026.
Measured from 10 closures across 4 active days in the window (eight or more closures measured inside the window).
Last closure 18 Aug 2026, 22:47 UTC.
Extend the Hyvä implementation from MetalCloak to all four sibling stores (Carbon Offroad, KMS, Rocksport, Jobber Portal).
Estimated working days remaining
9–207working days
Projected finish between 15 Sep 2026 and 18 Jun 2027.
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.
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
16–368working days
Projected finish between 24 Sep 2026 and 31 Jan 2028.
Measured from 1 closure across 1 active day in the window (one or two closures measured inside the window).
Last closure 1 Sep 2026, 20:32 UTC.
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–3working days
Projected finish between 3 Sep 2026 and 7 Sep 2026.
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.
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–5working days
Projected finish between 4 Sep 2026 and 9 Sep 2026.
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.
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–12working days
Projected finish between 8 Sep 2026 and 18 Sep 2026.
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.
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–21working days
Projected finish between 10 Sep 2026 and 1 Oct 2026.
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.
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–21working days
Projected finish between 10 Sep 2026 and 1 Oct 2026.
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.
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–23working days
Projected finish between 11 Sep 2026 and 5 Oct 2026.
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.
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
9–33working days
Projected finish between 15 Sep 2026 and 19 Oct 2026.
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.
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.
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.
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.
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.