Release planning

CadCraft 0.6 impact map

Every fix and feature lined up for 0.6, and what each one touches: which apps, and which layers of the stack. The layers are the ones on the Fork Map. 0.6 has shipped: this map keeps what it built, and every item that was not finished moved to 0.7.

ProjectCadCraft
Sheet0.6 impact
Items103
Date2026-10-21
30Fix
58Feature
4Spike
1Platform
4Site ops
2Sanity check
4Decision
≈ 0days in the planned and moved items, before DF.1’s fixes and the builds that wait on a go. Candidates are not counted: the one-lineup items alone would add about 109–117
  • Planned 2 0.6 part 1 or part 2 list
  • Built 98 built and working in /lab (the dev builds); ships with 0.6
  • Partly built 3 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.6 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 10 24 1 1 – 2 3 41
BimCraft 13 29 2 1 – – 1 46
ModelCraft 5 10 1 1 – – 2 19
MarkupCraft 2 8 1 1 – – 2 14
TakeoffCraft 1 8 – 1 – – 3 13
CivilCraft 1 13 1 1 – – 1 17
DetailCraft 1 8 – 1 – – 1 11
PartCraft 3 14 – 1 – – 1 19
Studio 4 9 – 1 – – 1 15
SuperCadCraft – – – – – – – 0
Layers
Site and services – 2 – – 4 – – 6
Desktop host 2 3 – 1 – – 1 7
App shell 3 10 – 1 – – – 14
App code 13 45 3 – – 2 4 67
Our engines 2 6 1 – – 2 – 11
Vendor engines – – 1 – – – – 1
Drawing surface 2 9 1 – – 1 – 13
Help and words – 11 – – – – – 11
Tests and tooling – 4 – 1 1 – – 6

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 21, 2026 8:20 pm.

ItemWhatAppsLayersStatusDaysWaits onIssues
Fixes 32
FixDF.1f Link to DF.1f Plant-layout DWG won’t open

a Discord member’s plant layout fails in ours and opens in ArtCraft’s app. Read it with cc-dwg in /use and /lab; fix the reader or say clearly what it can’t read.

CadCraft Our engines Partly built in DF.1 reader recovery in /use as 0.6.1; a Discord member's file to confirm From: Discord community (Discord) 0.6-PART2 DF.1 (2nd batch)
FixFIX-061-DWG2013 Link to FIX-061-DWG2013 CadCraft: a DWG 2013 (AC1027) drawing does not open

"This drawing could not be read… saved in a version the reader does not handle yet (AC1027)." That is the general unreadable message: cc-dwg reads 2013 drawings, so something in this file fails. Ask a Discord member for the file. docs/0.6.1.md 61.4a.

CadCraft Partly built – reader recovery in /use as 0.6.1; a Discord member's file to confirm From: Discord community (Discord) Discord #cadcraft, Oct 19, 2026
FixFIX-061-PLINE-VIEW Link to FIX-061-PLINE-VIEW CadCraft: polylines are drawn wrongly after a DWG is opened

Polylines look wrong on screen after a DWG is opened. Needs a Discord member's drawing to reproduce. (A REGEN command is its own 0.7 item, CAD-REGEN.) docs/0.6.1.md 61.4e.

CadCraft Partly built – wide-polyline fix in /use as 0.6.1; a Discord member's file to confirm From: Discord community (Discord) Discord #cadcraft, Oct 19, 2026

ArtCraft’s marks comments and requests about ArtCraft’s CADcraft, a different program that shares the Discord channel. They are not problems in ours. We run each one as a sanity check, so our apps don’t end up with the same issue.

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.