Release planning

CadCraft 0.7 impact map

What is left from 0.6 and what comes next: every item that was not finished when 0.6 shipped moved here with its status, plus new requests. 0.6 itself keeps what was built.

ProjectCadCraft
Sheet0.7 impact
Items115
Date2026-10-26
10Fix
88Feature
3Spike
3Platform
2Site ops
9Sanity check
0Decision
≈ 0days in the planned and moved items
  • Planned 0 0.6 part 1 or part 2 list
  • Built 115 built and working in /lab (the dev builds); ships with 0.6
  • Partly built 0 part of it is built in /lab; the rest waits (see "Waits on")
  • Promised 0 the live site already says 0.6
  • Moved 0 moved from the 0.5 wishlist
  • Found 0 bug found after 0.5 shipped; 0.5.1 or 0.6
  • Candidate 0 recommended for 0.6 in a spike or session log; owner to choose
  • Community please test 0 built and in /use; a Discord post gives the steps and the expected result and asks people to try it on their own devices, files or know-how
  • Decision Time 0 a decision, check, file, key, flag or go only you can give; folds into the list once answered

Sheet 1 · impact areas

Where 0.7 lands

How many items touch each app and each layer, by kind. One item can touch several areas, so the rows add up to more than the item count. Pick a row to filter the schedule below.

Impact areaFixFeatureSpikePlatformSite opsSanity checkDecisionAll
Apps
CadCraft 4 38 – 2 – 4 – 48
BimCraft 3 34 1 2 – 6 – 46
ModelCraft – 21 3 2 – 3 – 29
MarkupCraft – 16 – 2 – 2 – 20
TakeoffCraft 1 15 – 2 – 2 – 20
CivilCraft – 34 – 2 – 3 – 39
DetailCraft – 16 – 2 – 2 – 20
PartCraft – 23 2 2 – 4 – 31
Studio 2 8 – 1 1 – – 12
SuperCad Studio – – – – – – – 0
Layers
Site and services – 4 – – – – – 4
Desktop host – – – – – – – 0
App shell 1 13 – 2 – – – 16
App code 2 28 – – – – – 30
Our engines – 4 – – – – – 4
Vendor engines – 2 – – – – – 2
Drawing surface 3 4 – – – – – 7
Help and words – 3 – – – 1 – 4
Tests and tooling – – – 1 – 3 – 4

Sheet 2 · schedule

Every fix and feature

Grouped by track. App chips carry each app’s layer colour; Studio is in ink. "Waits on" names what has to happen first; the small lines under it say who asked and where the item is written up.

Add an item Fork map (Rust and C++ forks) The roadmap

Issues sync every 10 minutes; last sync Oct 26, 2026 10:50 pm.

ItemWhatAppsLayersStatusDaysWaits onIssues
Suggestions from /suggest (Oct 14–20) 8
FeatureSU.881 Link to SU.881 Portuguese in 0.7: Brazilian Portuguese kept complete, and Portugal Portuguese

Asked: a full Portuguese (Portugal and Brazil) interface for every app, tool, menu and workflow, for newcomers and professionals who work better in their own language (#881, Oct 20). Owner 2026-10-22: "do Portuguese". Checked 2026-10-22: pt-BR is a finished draft in all 16 scopes (docs/lang-sessions/pt-BR.md; gap fill for bimcraft and modelcraft the same day). There is no pt-PT, and a pt-PT file would fall back to pt then English, never to pt-BR, so it has to be a whole file. Do: (a) pt-PT by the docs/LANGUAGES.md routine — glossary tools/lang/glossary/pt-PT.md with a pt-BR column, as es-ES has es-MX (ficheiro, ecrã, guardar, eliminar, utilizador, pré-visualização; the AO90 spelling; Portuguese NP / EN drafting terms), every scope translated from the English with pt-BR as a reference, never a word swap; (b) pt-BR kept at 0 missing / 0 stale until 0.7 closes, after each session's What's new strings land; (c) both say "Draft translation, not yet reviewed by a native speaker" until a native reviewer reads them (owner item); (d) the language picker lists both by their own names.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraftStudio Built 1 session lang-pt-PT (+ pt-BR gap fills) From: site suggestion (Suggestion) /admin/suggestions, reviewed 2026-10-22
Suggest an item

Anyone can send one; no account and no name needed. The team reads each idea, and the ones we take on appear on this page. Please leave out web addresses.