pietroalbini

We're working on that! Expect more news around it in the coming months.

Note that this is just a first draft of the ferrocene spec, we aim to get it to a finished state by the end of the year!

The crates.io index is hosted on GitHub, but the application/API is hosted on Heroku (so in the us-east-1 AWS region) and the downloads on S3/CloudFront. And yes crates.io is currently impacted.

It's this research that prompted GitHub to show warnings, they didn't appear as of yesterday.

Mozilla has had to reduce its investment in Rust significantly, but it’s not abandoning Rust. Mozilla has committed to financial and logistical support while we get the foundation up and running, and we expect they will become a sponsor once that is an option.

This is still a open question! We made no decision on the name yet.

That flag shouldn't be documented: it's completly unsupported and meant to be used only by the compiler. Please don't rely on it :)

> to be able to block merging PRs on changes that accidentally impact LLVM's performance, like is currently the case for rustc.

rustc's CI doesn't prevent merging PRs that impact performance: while the reviewer can request benchmarks beforehand and choose not to approve the PR if it introduces a regression, all other benchmarks are run after the commits are merged to master.

Yeah, that's why I'd prefer for the Rust Foundation to be as lean as possible, explicitly excluding raising donations for the whole project and paying developers from its scope. Funding development could then be done by other entities, not related to the foundation.

https://internals.rust-lang.org/t/blog-post-towards-a-rust-f...

There are people inside Mozilla paid to work on the project full time. Not all of them are on the core team though.

Well with RHEL 8 you can get a pretty up to date rustc, as they update the version in their stable repos every three months (so every two releases): https://developers.redhat.com/blog/2019/11/07/support-lifecy...

Rust doesn't have LTS releases. Editions are both a way to market the new features introduced in the past years as a "bundle" to outside users, and a way for us to introduce some breaking changes for the users opting into the new edition. The release an edition is stabilized in (1.31 for Rust 2018) does not get any special treatment from the Rust team though, and that includes no LTS support (for example we won't backport bug fixes, even security ones).

Yeah, I only counted releases implementing new features, not every single one (both for Rust - even though we have few point releases - and for the other languages). Also some compilers don't have a fixed release schedule, which made gathering those stats a bit hard.

Microsoft is already sponsoring our CI on Azure Pipelines, so there would be no need to do that.

By the way, we don't actually run our CI on AWS. We use S3 to store caches and build artifacts, but all the builds run on Azure Pipelines at the moment.