Release channels take 2

This RFC describes changes to the Rust release process, primarily the division of Rust's time-based releases into 'release channels', following the 'release train' model used by e.g. Firefox and Chrome; as well as 'feature staging', which enables the continued development of experimental language features and libraries APIs while providing strong stability guarantees in stable releases.

This revision includes a significant simplification by merging stability attributes with feature gates, which further enables some additional useful features within Cargo related to version detection. One big implication of this change is that stability attributes are no longer suitable for use outside of std (if such a feature is desirable it is intended to be solved by Cargo).
What about `stable` things that aren't connected to any particular feature? (e.g. things that are `stable` now)

Also, what about unstable library that are just unstable because we want to iterate on the design something along the lines of `#[unstable(feature = "library design is hard")]`, but nicer, I guess?).