Skip to content

Publish an API stability and deprecation policy #69

Description

@codeforester

Parent: #50

Train position: 19 of 22
Phase: P3 — Ecosystem trust

Problem

Wide adoption requires explicit promises about the supported public facade, schemas, semantic versioning, and migrations.

Acceptance criteria

  • The public surface, semantic-versioning guarantees, experimental namespaces, supported Python/dependency windows, and compatibility promises are defined.
  • Deprecations have a warning mechanism, minimum support period, removal rules, migration guide, and changelog requirements.
  • Contract tests and documentation guard exported symbols and versioned schemas before 1.0.

Dependencies

Activity

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

Metadata

Metadata

Assignees

Labels

documentationDocumentation improvements

Type

No type

Projects

  • Status
    Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions