Jens
faeb58ef6d
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
1.4 KiB
1.4 KiB
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.