Skip to content

META: v1.0.0 release readiness — gates + what's left #234

@MartinCastroAlvarez

Description

@MartinCastroAlvarez

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.
  • ✅ Backend: full CRUD + list_filter, date_hierarchy, autocomplete, actions, bulk, M2M, OpenAPI schema, inlines read+write, file fields, login/logout, get_app_list, history, delete-preview, save_options, PWA manifest+SW.
  • ✅ Repo public.

What's left for v1.0.0

A. Frontend parity — "delete admin.site.urls and 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 field WRITE pathStructured range serializer + tests (PR #94 follow-up — contract says it; code doesn't emit it) #141 shipped the read envelope; the symmetric write coercion (accept the structured envelope → Range(...)) is unbuilt. → new issue.
  • docs/api-contract.md final freeze pass (the v1 wire contract becomes a stability commitment).

C. Quality gate (ACCEPTANCE.md §3.5 T-2)

  • Coverage ≥ 90% overall; permissions.py/serializers.py 100%; 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

  • 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").

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions