geointel/docs/40-build-launch/RELEASE_STRATEGY.md

RELEASE STRATEGY

GeoIntel releases must be small, testable and aligned with the build order graph.

Version targets

v0.1 — Foundation

• Backend starts.
• Frontend starts.
• Database/PostGIS works.
• Health/readiness works.

v0.2 — Project and Area Manager

• Project CRUD.
• Area CRUD.
• Geometry persistence.
• Map displays area fixtures.

v0.3 — Dataset Manager

• GeoJSON upload/register.
• Metadata extraction.
• Dataset list/detail UI.

v0.4 — Raster/Vector Foundation

• Raster metadata skeleton if dependencies are available.
• Vector operations baseline.
• Layer display improvements.

v0.5 — Detection Import / Detection Lab Skeleton

• Detection result import.
• Detection layer display.
• Model-adapter boundary, no heavy inference required yet.

v0.6 — QA/QC Foundation

• Reference vs prediction matching.
• Metrics.
• False positive/false negative outputs.

v0.7 — GeoJSON Export and Review

• Stable export workflow.
• Export validation.
• Basic review UI.

v1.0 — GeoAI Workbench MVP

• Stable dataset workflow.
• Raster/vector foundations.
• Detection/segmentation architecture.
• QA/QC workflow.
• Export workflow.
• Portfolio-ready demo.

Release rule

A release cannot be cut if:

• readiness checks fail;
• golden paths regress;
• docs are stale;
• API contracts drift without documentation;
• known limitations are hidden.