On Tue, 2015-12-22 at 12:59 +0100, Jan Kurik wrote:
= Proposed System Wide Change: GCC6 =
https://fedoraproject.org/wiki/Changes/GCC6
Change owner(s):
* Jakub Jelínek < jakub AT redhat DOT com >
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.
== Detailed Description ==
GCC 6 is currently in stage3, will move to stage4 around mid January,
in prerelease state with only regression bugfixes and documentation
fixes allowed. The release will happen probably in the middle of
April. We are working on scratch gcc rpms and will perform a test mass
rebuild.
== Scope ==
All packages should be rebuilt with the new gcc once it hits f24, or,
if there is not enough time for that, just all packages built after
the new gcc hits the buildroots.
This...seems like a worrying time frame. The Beta release is scheduled
for April 7. Do we really want to be landing the stable version of the
release compiler, and possibly trying to organize a mass rebuild, after
Beta is done?
Per the Change
policy: https://fedoraproject.org/wiki/Changes/Policy
Changes are required to be "feature complete or close enough to
completion by the Change Checkpoint: Completion deadline date that a
majority of its functionality can be tested during the Alpha and Beta
releases" - that deadline is currently listed as 2016-02-02, though I
believe by policy it's actually supposed to be 2016-02-16 (the date of
the Alpha freeze). I guess that lines up OK with 'stage4'. Changes are
required to be 'code complete' by 2016-03-29, defined as "New accepted
changes must be code complete, meaning all the code required to enable
to the new change is finished". Does that line up?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net