Closed Bug 1695828 Opened 5 years ago Closed 4 years ago

Please update the Rust Update Policy document

Categories

(Firefox Build System :: Toolchains, task)

task

Tracking

(firefox105 fixed)

RESOLVED FIXED
105 Branch
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.

Component: General → Toolchains
Assignee: nobody → mh+mozilla
Depends on: 1709730

The imported policy document at https://firefox-source-docs.mozilla.org/writing-rust-code/update-policy.html still has the same problem.

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. )

(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.

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).

Pushed by mh@glandium.org: https://hg.mozilla.org/integration/autoland/rev/d358e5080b29 Update the Rust Update Policy to reflect the current practices. r=bholley
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 105 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: