On Wed, Jan 14, 2015 at 9:28 AM, Jakub Jelinek <jakub@xxxxxxxxxx> wrote: > On Wed, Jan 14, 2015 at 09:12:42AM -0500, Jaroslav Reznik wrote: >> ----- Original Message ----- >> > On Wed, Jan 14, 2015 at 02:55:15PM +0100, Zbigniew Jędrzejewski-Szmek wrote: >> > > http://gcc.gnu.org/gcc-5/porting_to.html → 404 >> > >> > That will be added likely after the test mass rebuild with what we find >> > during that. >> >> Do you have any estimate when it will be done? F22 schedule is/will be pretty >> tight. We already have problem scheduling mass rebuild and I expect GCC 5 >> would require as long as possible period to fix issues/build problems. This > > How is that different from any other past Fedora releases (with the > exception of F21)? If I remember well, at least starting with GCC 4.3 (March 2008) > new GCC was deployed always in the spring release of Fedora, we've skipped > 4.2 before that and as there was no spring release last year, GCC 4.9 was > kind of an exception too. The difference this time is that FESCo decided to set a time-based schedule and adhere to it. The past two releases were set based on submitted Changes (with F21 being weird all around). Before that, the schedule was time-based but not strictly stuck to which led to lots of slips. Essentially, this is an attempt to _actually_ do a time-based schedule. That being said, FESCo is discussing the schedule again today because there's no room for a mass rebuild at all. It will be interesting to see if they actually stick to the plan and defer any Change that requires a mass rebuild. josh -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
