Skip to content

Semantically version the language specification, compiler, and libraries #303

@rust-highfive

Description

@rust-highfive

Issue by cmr
Wednesday Jan 08, 2014 at 04:57 GMT

For earlier discussion, see rust-lang/rust#11396

This issue was labelled with: A-versioning, B-RFC in the Rust repository


semver is a specification for version numbers and what they mean. Once we hit 1.0, I think we should start semver for everything, thus actually making it 1.0.0.

The "public API" we define would only consist of items marked #[stable] in the libraries. For the language, it would be anything not requiring a feature gate. For the compiler, it'd be output filenames and arguments, excluding -Z, --link-args, --linker, undefined lints, --lvm-args, --passes, and --ar.

Nominating.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-stabilityProposals relating to policy and changes about stability of features.A-versioningVersioning related proposals & ideasT-coreRelevant to the core team, which will review and decide on the RFC.

    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