&gt; By complaining that when you update nightly you have to update your code that uses unstable features, you are in effect asking us to stabilize everything.<p>No, I think the point is to just have a specific unstable that corresponds to a specific stable as closely as possibly, and designated as such.,  Conceivably crates that needed unstable features, but not bleeding edge, could require at least that unstable release, while others that really need bleeding edge features could use nightly.  The issue here is that your release procedure treats unstable features differently than everything else, making any crate or code that wants to use any unstable feature resort to using a nightly of some sort.  Admittedly, I can see reasons why this might be by design.<p>You might have good reasons why you think that won&#x27;t work or be useful (I can think of a few, such as not wanting to promote people building on a specific implementation of an unstable feature).  At a minimum, it is at least slightly more work to make sure this new item is released, depending on the release process.<p>P.S. The prevailing wisdom so far when wanting to use unstable features from a point release is to use a nightly form the same day, but the release policy seems to indicate that the nightly from that time is actually <i>two</i> release versions ahead of the stable that was released the same day:<p>&gt; This process happens in parallel. So every six weeks, on the same day, nightly goes to beta, beta goes to stable. When 1.x is released, at the same time, 1.(x + 1)-beta is released, and the nightly becomes the first version of 1.(x + 2)-nightly.[1]<p>I&#x27;m a bit unclear on what the best thing to do would be if I wanted to use features from something that is as close as possible to a particular stable release.<p>1: <a href="https:&#x2F;&#x2F;doc.rust-lang.org&#x2F;book&#x2F;release-channels.html" rel="nofollow">https:&#x2F;&#x2F;doc.rust-lang.org&#x2F;book&#x2F;release-channels.html</a>