Skip to content

Version numbering policy (e.g. reason for missing 0.126.0 and 0.127.0)? #20784

@your-diary

Description

@your-diary

I regularly check the release notes of codex, and often find some versions are skipped when a stable release is published.

For example, the next stable version after 0.125.0 is 0.128.0; 0.126.0 and 0.127.0 were skipped.

Regarding this, I have two questions:

  • Just out of curiosity, why do you sometimes skip some version numbers? This is a bit inconvenient because I usually compare the latest version number with the local one to estimate how far behind I am.

  • More importantly, when you release the version $N + M$ after the version $N$, skipping $N + 1,\ N + 2,\ \cdots,\ N + M - 1$, can we expect that the release note of the version $N+M$ contains all changes since the version $N$, not just the changes since $N + M - 1$?

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLIIssues related to the Codex CLIdocumentationImprovements or additions to documentation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions