Date: Sat, 31 Mar 2018 09:54:43 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 227130] lang/rust: Update to 1.25 Message-ID: <bug-227130-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227130 Bug ID: 227130 Summary: lang/rust: Update to 1.25 Product: Ports & Packages Version: Latest Hardware: Any URL: https://www.google.com.au/url?sa=3Dt&rct=3Dj&q=3D&esrc= =3Ds&sou rce=3Dweb&cd=3D1&ved=3D0ahUKEwissYrepJbaAhUGe7wKHZ38CuU= QFggn MAA&url=3Dhttps%3A%2F%2Fblog.rust-lang.org%2F2018%2F03%2 F29%2FRust-1.25.html&usg=3DAOvVaw1snq6RKNaaOe3uZGqT4V4Z OS: Any Status: New Keywords: needs-patch, needs-qa Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: rust@FreeBSD.org Reporter: koobs@FreeBSD.org CC: gecko@FreeBSD.org, jbeich@FreeBSD.org Flags: maintainer-feedback?(rust@FreeBSD.org) Assignee: rust@FreeBSD.org Flags: merge-quarterly? Tracking issue for the rust 1.25 release. The change needs to be MFH'd, per @jbeich who asks (via email): Firefox 61 scheduled on 2018-06-26 [1] will require [2] Rust 1.25 to build. If 2018Q2 will be stuck with Rust 1.24.1 I won't be able to MFH Firefox 61 on release day. Once 2018Q3 branches some users may delay upgrade for a few weeks due to inherent instability when a /quarterly branch is created. Can you add "MFH: 2018Q2" to commit message when landing Rust 1.25 update? [1] https://wiki.mozilla.org/RapidRelease/Calendar [2] https://bugzilla.mozilla.org/show_bug.cgi?id=3D1450078 https://wiki.mozilla.org/Rust_Update_Policy_for_Firefox --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227130-21738>