https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227130
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=t&rct=j&q=&esrc=s&sou
rce=web&cd=1&ved=0ahUKEwissYrepJbaAhUGe7wKHZ38CuUQFggn
MAA&url=https%3A%2F%2Fblog.rust-lang.org%2F2018%2F03%2
F29%2FRust-1.25.html&usg=AOvVaw1snq6RKNaaOe3uZGqT4V4Z
OS: Any
Status: New
Keywords: needs-patch, needs-qa
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: r...@freebsd.org
Reporter: ko...@freebsd.org
CC: ge...@freebsd.org, jbe...@freebsd.org
Flags: maintainer-feedback?(r...@freebsd.org)
Assignee: r...@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=1450078
https://wiki.mozilla.org/Rust_Update_Policy_for_Firefox
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
freebsd-gecko@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-gecko
To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
