[main blog] Reducing support for 32-bit Apple targets#487
[main blog] Reducing support for 32-bit Apple targets#487emilyalbini merged 7 commits intorust-lang:masterfrom
Conversation
|
The RFC has been merged. |
|
Added a section in the end on how the change will affect nightly users. |
jonas-schievink
left a comment
jonas-schievink
left a comment
There was a problem hiding this comment.
Looks good to me, except the spelling of "Apple 32bit targets" looks a bit weird IMO. I've usually seen it as "32-bit Apple targets" instead. Feel free to disregard if that spelling has precedence though.
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
|
Good point @jonas-schievink, amended the blog post. |
emilyalbini
changed the title
| - Tier 3 targets are not available for download through rustup, and are | ||
| ignored during our automated builds. You can still build their standard | ||
| library for cross-compiling (or the full compiler in some cases) from source | ||
| on your own, but you might encounter build errors, bugs, or missing features. |
There was a problem hiding this comment.
I'm not sure if we need a full summary of how support tiers work in this announcement. I think the links to the current support tiers and RFC 2803, together with a simple statement that 32-bit Apple targets will no longer be exercised in any way via the Rust project's CI infrastructure, would be sufficient.
There was a problem hiding this comment.
As this affects both tier 1 and tier 2 platforms going into tier 3, I think having a brief description of what those tiers mean in the blog post is useful.
Co-Authored-By: Kyle J Strand <BatmanAoD@users.noreply.github.com>
5 participants
RFC 2837, "Demote Apple 32bit targets to Tier 3", is going to be merged soon, and one of the things it requires is a blog post on the main blog announcing the change, to bring as much awareness to the demotion as we can.
I wrote a draft of the post, what do y'all think?
r? @rust-lang/core
cc @rust-lang/release