GigaCAD today versions CAD projects: branches you check out, versions you name, and release requests where you pick, file by file, what goes into the next release. Everything below is planned, not shipped. The order is the order we expect to build it, and we'll write here as each piece lands.
1. Windows and the SolidWorks add-in
Projects as folders in File Explorer, and locks, versions, and references inside SolidWorks. Release candidates are rebuilt in SolidWorks before anyone approves them.
2. Organizations
Teams and roles, teams as approvers, shared billing and storage, company sign-in, admin controls, and public organization pages. Organization projects start private.
3. Issues, boards, and sprints
A branch for every issue, issues linked to the parts they're about, and releases that close the issues they shipped. Sprints end in a release you can build.
4. Two-way Jira sync
Teams that already plan in Jira keep it. Releasing moves linked issues to Done and posts the release back.
5. Review on the model
Comments on faces, features, and drawings inside a release request, so reviewers can point at the hole that's too close to the edge.
6. Releases you can build from
Bills of materials, drawings, and manufacturing packages generated from a release.
7. More CAD programs, and more after that
Fusion, FreeCAD, and Onshape. Later, electronics: KiCad and Altium projects versioned and released next to the mechanical parts.
8. The open hardware hub
A place where public designs are found, forked, improved, and built.
Through all of it, the API and the command-line tool stay open to scripts and AI agents, with the same locks, roles, and approvals as people.