You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are we ready for v1.0.0? — No, not yet. We're at 0.2.0a4 (alpha). This meta-issue is the single source of truth for what's left to cut 1.0.0, gated by ACCEPTANCE.md §5 (every applicable §2/§3/§4 criterion ✅ + quality gates + repo-owner go-ahead). Below: what's done, what's left, who owns it.
Where we are
✅ PyPI: 0.2.0a4 live; GitHub Releases aligned; main matches.
✅ Security: CodeQL 0, Dependabot 0, secret scanning + push protection on, threat model current.
ARCHITECTURE.md §8 is stale — it still lists inlines / custom actions / bulk actions / autocomplete / React-extension as "deferred to v1.x", but all shipped. Must be reconciled before declaring v1 (the architecture contract can't claim a shipped feature is deferred). → new issue.
ACCEPTANCE.md §2 (PM/UX), §3 (Architect), §4 (Security) audited all-green for the milestone.
D. Hardening (#144) — agent items done; owner actions remain
Branch protection on main (owner).
Rotate the .git/config PAT (owner).
E. Release (Tier 6, human)
All §5 rows ✅ → tag 1.0.0 (not …aN).
Repo-owner provides the go-ahead + holds the PyPI token.
Sequencing
A (frontend, the long pole — other-lane) and B/C (docs+quality, mostly my lane) can proceed in parallel. When A's deprecation-blocking rows + B + C are green, cut 0.2.0rc1, soak, then 1.0.0. D + E are the final human gates.
— filed by the Security & Compliance Lead at the repo owner's request ("what's left for v1.0.0").
Are we ready for
v1.0.0? — No, not yet. We're at0.2.0a4(alpha). This meta-issue is the single source of truth for what's left to cut1.0.0, gated byACCEPTANCE.md§5 (every applicable §2/§3/§4 criterion ✅ + quality gates + repo-owner go-ahead). Below: what's done, what's left, who owns it.Where we are
0.2.0a4live; GitHub Releases aligned;mainmatches.What's left for v1.0.0
A. Frontend parity — "delete
admin.site.urlsand lose zero workflows" (#160)Most deprecation-blocking rows have shipped (inlines render+edit #54, list_filter, date_hierarchy, FK links, M2M, files, actions, session-expiry, PWA install). Remaining SPA work:
B. Docs / contract reconciliation
ARCHITECTURE.md§8 is stale — it still lists inlines / custom actions / bulk actions / autocomplete / React-extension as "deferred to v1.x", but all shipped. Must be reconciled before declaring v1 (the architecture contract can't claim a shipped feature is deferred). → new issue.Range(...)) is unbuilt. → new issue.docs/api-contract.mdfinal freeze pass (the v1 wire contract becomes a stability commitment).C. Quality gate (
ACCEPTANCE.md§3.5 T-2)permissions.py/serializers.py100%;views/*≥ 95%.ACCEPTANCE.md§2 (PM/UX), §3 (Architect), §4 (Security) audited all-green for the milestone.D. Hardening (#144) — agent items done; owner actions remain
main(owner)..git/configPAT (owner).E. Release (Tier 6, human)
1.0.0(not…aN).Sequencing
A (frontend, the long pole — other-lane) and B/C (docs+quality, mostly my lane) can proceed in parallel. When A's deprecation-blocking rows + B + C are green, cut
0.2.0rc1, soak, then1.0.0. D + E are the final human gates.— filed by the Security & Compliance Lead at the repo owner's request ("what's left for v1.0.0").