This is a tracking bug for Change: GCC5
For more details, see: https://fedoraproject.org//wiki/Changes/GCC5
Switch GCC in Fedora 22 to 5.x.y, rebuild some packages with it.
This message is a reminder that Fedora 22 Change Checkpoint: Completion deadline (testable) is on 2015-02-24 .
At this point, all accepted Changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Completion deadline.
This bug should be set at least to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. Fedora 22 is going to be strictly time based release. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon.
In case of any questions, don't hesitate to ask Wrangler (jreznik). Thank you.
GCC 5 landed in Fedora 22.
This message is a reminder that Fedora 22 "Change Checkpoint: 100% Code Complete Deadline" is on 2015-03-31 .
All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA.
As for several System Wide Changes, Beta Freeze is a point of contingency plan, all incomplete Changes will be reported to FESCo for 2015-04-01 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik).
Hi Jakub, we'd like to include this change in the Fedora 22 Beta Release Notes.
Please take a look at the draft I wrote in the Doc Text field, and let me know if this text is sufficient, or if there's anything you'd like to add or change.
I'd say that the C++14 support is full, not partial.
Instead of 5.0.x, you probably should write just 5.x, or 5.1.1 (the GA release, hopefully in a week or two, will be 5.1.0, and 5.1.1 will be the snapshots from the release branch until 5.2.0 is shipped (most likely 2 months after that or so).
Thanks, guys. Both are fixed now.