|Product:||[Fedora] Fedora||Reporter:||Jan Kurik <jkurik>|
|Component:||Changes Tracking||Assignee:||Jakub Jelinek <jakub>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2016-09-29 11:26:01 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Jan Kurik 2016-01-12 08:37:49 UTC
This is a tracking bug for Change: GCC6 For more details, see: https://fedoraproject.org//wiki/Changes/GCC6 Switch GCC in Fedora 24 to 6.x.y, rebuild all packages with it, or optionally rebuild just some packages with it and rebuild all packages only in Fedora 25.
Comment 1 Jan Kurik 2016-02-24 14:26:16 UTC
On 2016-Feb-23, we have reached Fedora 24 Change Checkpoint: Completion deadline (testable). 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. Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness. Incomplete and non testable Changes will be reported to FESCo on 2016-Feb-26 meeting. Contingency plan for System Wide Changes, if planned for Alpha (or in case of serious doubts regarding Change completion), will be activated.
Comment 2 Jakub Jelinek 2016-02-25 14:54:54 UTC
Mass rebuild has been performed with this gcc, release is on track for release in April or so.
Comment 3 Jan Kurik 2016-04-20 15:02:13 UTC
On 2016-Apr-19 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 24 release. At this point all the Changes not at least in in "ON_QA" state should be brought to FESCo for review. Please update the state of this bug to "ON_QA" if it is already 100% completed. Please let me know in case you have any trouble with the implementation and the Change needs any help or review. Thanks, Jan