Skip to content

Stabilize the experimental tier toward v1 + publish a compatibility matrix #179

Description

@joshua-temple

The entire IO/runtime surface (source, sink, durable, cluster, wasm, telemetry) is labeled experimental, which deters production adoption.

  • Define explicit graduation criteria for moving a module experimental → v1.
  • Publish a per-module stability / compatibility matrix in the README/docs.
  • Sequence modules toward v1.

Pairs with the broader docs honesty/stability-policy work.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requestroadmapPlanned enhancement / roadmap item

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions