Please update the Rust Update Policy document
Categories
(Firefox Build System :: Toolchains, task)
Tracking
(firefox105 fixed)
| Tracking | Status | |
|---|---|---|
| firefox105 | --- | fixed |
People
(Reporter: mstange, Assigned: glandium)
References
Details
Attachments
(1 file)
https://wiki.mozilla.org/Rust_Update_Policy_for_Firefox
The policy currently says:
We require a new stable Rust starting 2 weeks after it is released.
glandium tells me that that's not the case any more.
Please update the document.
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Updated•5 years ago
|
| Reporter | ||
Comment 1•5 years ago
•
|
||
The imported policy document at https://firefox-source-docs.mozilla.org/writing-rust-code/update-policy.html still has the same problem.
Comment 2•5 years ago
|
||
I think it would be good to have an explanation for why we're maintaining a 1.47.0 MSRV to the point of adding hacks that offend the Rust community.
(Someone on HN discovered https://searchfox.org/mozilla-central/source/third_party/rust/xmldecl/build.rs , which exists due to the 1.47.0 MSRV and not due to SIMD issues. This time, the high-level bad experience that was, on HN, Lobsters, and Reddit, initially blamed on Firefox's use of RUSTC_BOOTSTRAP turned out to be something different, though. )
| Assignee | ||
Comment 3•5 years ago
|
||
(In reply to Henri Sivonen (:hsivonen) from comment #2)
I think it would be good to have an explanation for why we're maintaining a 1.47.0 MSRV to the point of adding hacks that offend the Rust community.
We aren't, see bug 1715282.
Comment 4•5 years ago
|
||
It would really clear up confusion (mine at least) to say in the policy doc what we are doing (that's neither requiring a new stable Rust starting 2 weeks after it is released nor maintaining a particular MSRV).
| Assignee | ||
Comment 5•4 years ago
|
||
Comment 7•4 years ago
|
||
| bugherder | ||
Description
•