Re: Fedora 26 Alpha status is NO-GO

2017-03-24 Thread Matthew Miller
On Thu, Mar 23, 2017 at 08:00:35PM +0100, Jan Kurik wrote: > Due to blockers found during the last days [1] we have decided to > delay the Fedora 26 Alpha release for one more week. There is going to Of particular note, this does *not* automatically delay the F27 release. That means that with the

Fedora 26 Alpha status is NO-GO

2017-03-23 Thread Jan Kurik
The result of the second Fedora 26 Alpha Go/No-Go Meeting is NO-GO. Due to blockers found during the last days [1] we have decided to delay the Fedora 26 Alpha release for one more week. There is going to be one more Go/No-Go meeting on the next Thursday, March 30th, 2017 at 17:00 UTC to verify

Fedora 26 Alpha status is NO-GO

2017-03-23 Thread Jan Kurik
The result of the second Fedora 26 Alpha Go/No-Go Meeting is NO-GO. Due to blockers found during the last days [1] we have decided to delay the Fedora 26 Alpha release for one more week. There is going to be one more Go/No-Go meeting on the next Thursday, March 30th, 2017 at 17:00 UTC to verify

Fedora 26 Alpha status is NO-GO

2017-03-16 Thread Jan Kurik
Release status of the Fedora 26 Alpha Go/No-Go Meeting is NO-GO. Due to late blockers we are missing RC of Fedora 26 Alpha release. As such the decision is to slip the Fedora 26 Alpha release for one week. There is going to be one more Go/No-Go meeting the next Thursday, March 23rd, 2017 at 17:00

Fedora 26 Alpha status is NO-GO

2017-03-16 Thread Jan Kurik
Release status of the Fedora 26 Alpha Go/No-Go Meeting is NO-GO. Due to late blockers we are missing RC of Fedora 26 Alpha release. As such the decision is to slip the Fedora 26 Alpha release for one week. There is going to be one more Go/No-Go meeting the next Thursday, March 23rd, 2017 at 17:00