-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Semantically version the language specification, compiler, and libraries #303
Copy link
Copy link
Open
Labels
A-stabilityProposals relating to policy and changes about stability of features.Proposals relating to policy and changes about stability of features.A-versioningVersioning related proposals & ideasVersioning related proposals & ideasT-coreRelevant to the core team, which will review and decide on the RFC.Relevant to the core team, which will review and decide on the RFC.
Description
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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-stabilityProposals relating to policy and changes about stability of features.Proposals relating to policy and changes about stability of features.A-versioningVersioning related proposals & ideasVersioning related proposals & ideasT-coreRelevant to the core team, which will review and decide on the RFC.Relevant to the core team, which will review and decide on the RFC.
Type
Fields
Give feedbackNo fields configured for issues without a type.