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 9:10 pm.

ItemWhatAppsLayersStatusDaysWaits onIssues
Decision Time 5
DecisionLC-SCOPE Link to LC-SCOPE Which lineup gaps go into 0.6

Pick from LC.1–LC.10 (0.6-PART3 has the coverage table: their product → our app → covered, partial, gap).

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App code Built – You: decision From: asked of the owner by: 0.6-PART3 (Session) 0.6-PART3
DecisionDEC-2-5 Link to DEC-2-5 Live session defaults

Live session limits are soft. How many people can join depends on their hardware, the drawing’s complexity and the network, none of which GetCadCraft controls, so there is no hard cap of our own (today the protocol stops at 20; the host can lower it). When a host allows a large list of people, Live shows a warning that explains the performance cost (every edit goes to everyone, and weaker laptops or slow links will lag) and lets them continue. The other defaults stand: holds start on select, viewers need approval, browser joiners allowed, the hold and assistant rules as built.

CadCraftMarkupCraftTakeoffCraftStudio App codeDesktop host Built – Owner decided 2026-10-17; to build From: asked of the owner by: 0.5-PLAN; live-core, live-finish (Session) 0.5-PLAN; live-core, live-finish
DecisionDEC-10 Link to DEC-10 Which add-ons we build

Approved by the owner on 2026-10-17: the first-party add-ons in docs/ADDONS-CANDIDATES.md (Electrical, Apparel, Render, Point clouds, then HVAC and Piping) are the ones we build. All of them are already built (Electrical and Apparel in 0.5, Render in 0.5, point clouds in 0.5 and 0.6, HVAC and Piping in 0.5, off by default). Everything else on that list is community work on the developer kit.

CadCraftTakeoffCraft App code Built – – From: asked of the owner by: 0.5-PLAN decision 10 (Session) 0.5-PLAN decision 10
DecisionDR.4 Link to DR.4 Push-pull flush: outline or one face

Keep the outline (recommended) or merge back to one flat face. Moved out of Decision Time 2026-10-17: Keep the outline when an inner face lands flush (the recommended choice, and how it works now).

ModelCraft App code Built – Default in place; change it here if you decide otherwise From: asked of the owner by: model, a Discord member (Session) model

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.