Skip to content

Release Roadmap

The roadmap in this repository is implementation-oriented and grounded in the current scaffold.

The next product move is to grow the shared core while building the OSS and Enterprise tracks in parallel without splitting the codebase.

v0.1 Alpha

Focus:

  • Foundation layer bootstrap
  • Local state backend
  • Deterministic plan/apply/destroy workflow
  • Azure-first Databricks provider abstraction
  • Basic governance compilation
  • CLI bootstrap
  • Product-grade documentation baseline

Recently completed milestones

v0.2

  • Saved-plan apply hardening with metadata and stale-config checks
  • Richer schema validation
  • Better error modeling
  • More complete starter project scaffolding
  • OSS and Enterprise track maturation around shared edition-aware contracts

v0.3

  • Databricks CLI profile authentication and enterprise auth-extension boundary
  • Brownfield import suite generation for workspace, RBAC, taxonomy, and masking review
  • Identity and grant-aware import discovery where account SCIM and SQL warehouse access are available
  • Snowflake provider scaffold for state-only planning
  • Stronger provider contract coverage

v0.4

  • Import progress checkpoints
  • Resumable enterprise import jobs
  • Databricks grant scan budgets by object type
  • Enterprise import suite naming
  • Snowflake live-readonly database and schema discovery
  • Databricks-to-Snowflake mapping drafts
  • GitHub issue draft export for planning workflows

v0.5

  • Enterprise activation readiness preflight for hosted control plane onboarding
  • Redacted activation handoff bundle export for onboarding evidence
  • Hosted control plane product architecture and OSS extension contracts
  • Versioned hosted control plane reference architecture export
  • Redacted hosted control plane handoff contract generation
  • Redacted offline purchase review, fulfillment decision, and activation receipt contracts
  • Single-directory Enterprise activation handoff package export
  • Immutable offline tenant entitlement record export for future registry ingestion
  • Remote-state planning boundary for multi-user hosted workflows
  • State backend readiness inspection for local and remote backend contracts
  • Audit evidence and activation handoff documentation
  • Redacted activation audit evidence export
  • Snowflake-to-Databricks database/schema mapping drafts with collision checks

The OSS milestone stops at redacted offline evidence. Payment processing, private package access, cryptographic license signing, and hosted tenant provisioning require a future private Enterprise backend.

v0.6

Current release target: 0.6.0a1.

  • Versioned provider-neutral metadata inventory contract
  • Stable asset IDs and provider-native catalog, database, and schema types
  • Read-only normalization of Databricks and Snowflake discovery
  • Python API and JSON-safe inventory export CLI
  • Atomic, conflict-safe inventory publication
  • Environment-gated Databricks and Snowflake live-readonly test contracts
  • Provider-native table and view inventory with column children
  • Stable identities for dots, spaces, Unicode, quotes, and provider casing
  • Global fail-closed limits of 1,000 relations and 10,000 columns

The 0.6.0a0 slice established catalog/database and schema contracts. The 0.6.0a1 slice adds table, view, and column depth. Grants, lineage inference, policy enforcement, and provider mutation remain future reviewed slices.

The preliminary CLI banner remains unchanged. A future implementation may use the approved static ASCII wordmark direction only if it remains below 80 columns and adds no dependency. Banners may appear only for interactive human text output; JSON success, usage-error, and provider-error paths must always suppress them, and --no-banner is authoritative for every command. Banner implementation still requires separate approval.

v1.0 target direction

  • Complete open-source surface for the initial provider
  • More production-grade provider execution logic
  • Broader governance enforcement support
  • More polished contributor and operator workflows

Documentation implication

Every roadmap stage should ship with matching docs updates. For an international SaaS product, stale docs are a product defect, not a documentation inconvenience.