4 ms·
Postmortem Analysis in Cargo
- coderintherye 4y agoAll of this is great and transparent, speaks volumes to the efficacy of the Rust ecosystem and the processes the core team and developers have set up. I am curious though what about https://github.com/rust-lang/cargo/pull/11285/files https://github.com/rust-lang/cargo/pull/11285/files actually caused the resulting bug. I mean conceptually I get it, but it'd be neat to see some commentary on what exactly happened in that change to result in the actual bug itself.
- PoignardAzur 4y agoIt's cool that the cargo team is embracing formalized postmortems and using them to improve their process. Although I'm a bit surprised by the seriousness of the language employed; the post-mortem acts like they've dodged a major bullet, when the worst-case scenario would have been "nightly builds fail for a day or two", which, you know, is a risk you've signed up for if you use nightly builds. It's important to take even minor failures seriously, but I think we should also communicate accurately how serious they are; treating every failure with maximum seriousness leads to the situation where people say "look at how unsafe Rust is, it has a lot of CVEs!" where almost all these CVEs aren't even considered vulnerabilities in other languages.
- andrewf 4y agoPriority of action items (at the bottom), weighted by cost, is one view of seriousness.