Dear SRMs, My understanding is that Debian's new-ish plan is to update firefox-esr versions in stable when there is a security update and the firefox-esr upstream support window for the previous version has expired. What is the plan for handling any new build-deps this new firefox-esr release might require, and how will they also be merged into the existing stable release?
Firefox upstream is discussing how things will work once a (part) of Firefox build-depends on the Rust compiler (rustc.deb). Rust has strong backwards guarantees, but is otherwise rapidly evolving. It is highly likely that a newer upstream codebase will require a newer rustc, and I'm wondering what the implications for our rustc packaging might be if we have to plan for a newer rustc to be merged into an existing stable release. I feel like I read the answer to this once before, but haven't been able to find it described anywhere. A pointer to an existing doc would be most welcome. - Gus
