Adding to the meeting agenda for today's (2017-08-18) FESCo meeting at 16:00 UTC. @mattdm, @jkurik, would be great if you could both join.

I will not be able to join as I will be travelling, however I will read the meeting log, so feel free to throw an action to me, if needed.

@jakub @codonell how does the mass rebuild dates look for gcc and glibc?

This is based on the draft I made while Jan was on vacation, with adjustment for the change checkpoint (testable). We had discussion about this on the devel list and the mass rebuild pushed back a little bit to accommodate the tools team; I assume it's still okay with them.

@jakub @codonell how does the mass rebuild dates look for gcc and glibc?

This: "2018-01-31 Mass Rebuild" looks good to me. Green light from the glibc team.

Notes: The upstream glibc project starts their API/ABI freeze on 2018-01-01, so by the 31st we'll have an ABI stable release with almost no likelihood of ABI changes, and the official ABI-frozen release is on 2018-02-01. We do a tiny glibc rebase to get the ABI assurances provided by the officially released version.

Thanks @codonell and @mattdm. Sounds like we should be able to move forward with this schedule then.

From yesterday's FESCo meeting:

• This needs more discussion. We'll revisit again next week. (kalev,
  17:15:54)

https://meetbot.fedoraproject.org/fedora-meeting/2017-08-18/fesco.2017-08-18-16.00.html

@jakub input on gcc8 would be really useful here

@ausil We can't respond to the gcc8 question until early September. Key members of the Fedora toolchain team are out on vacation and won't be back until then for us to have some serious discussions about the schedule. When everyone is back I'll make sure we follow up here with the details. Sorry for the delay.

@codonell We had @jlaw join us in the meeting and he confirmed the schedule from GCC's side. Do you disagree?

@codonell We had @jlaw join us in the meeting and he confirmed the schedule from GCC's side. Do you disagree?

I do not disagree.

If @jlaw said the schedule was OK then it's OK.

This was approved last week