Re: F27 and the short schedule [was Re: Fedora 27 Change Checkpoint: Completion deadline (testable)]

On Sat, Aug 05, 2017 at 01:10:44PM +0200, Kevin Kofler wrote: > There seems to be a misunderstanding: I am not claiming that No-more-alphas > was invented specifically for the short F27 schedule. I am only pointing out > that the F27 schedule assumes No-more-alphas and that such a short schedule

Re: F27 and the short schedule [was Re: Fedora 27 Change Checkpoint: Completion deadline (testable)]

Jan Kurik wrote: > This is going to follow the Change process, so if at certain point in > time the Change will not be ready it will go to FESCo to review the > progress and weight risks and benefits of the Change. It is then up to > FESCo to decide. Anyone from the Fedora community can join FESCo

Re: F27 and the short schedule [was Re: Fedora 27 Change Checkpoint: Completion deadline (testable)]

On Thu, Aug 3, 2017 at 4:45 AM, Kevin Kofler wrote: >> On Wed, Aug 2, 2017 at 2:47 PM, Matthew Miller wrote: >>> Because it is a short release, we should focus on a few key changes and >>> otherwise limit scope as much as possible. From my perspective, the >>> things we

Re: F27 and the short schedule [was Re: Fedora 27 Change Checkpoint: Completion deadline (testable)]

> On Wed, Aug 2, 2017 at 2:47 PM, Matthew Miller wrote: >> Because it is a short release, we should focus on a few key changes and >> otherwise limit scope as much as possible. From my perspective, the >> things we should focus on this time around are infrastructure related: >> >> - enabling CI

Re: F27 and the short schedule [was Re: Fedora 27 Change Checkpoint: Completion deadline (testable)]

On Wed, 2017-08-02 at 11:02 -0400, Matthew Miller wrote: > On Wed, Aug 02, 2017 at 10:49:58AM -0400, Owen Taylor wrote: > > I've been pushing hard to have the infrastructure changes ready on > > the F27 timescale, because we don't like to make unrelated > > infrastructure changes during the later

Re: F27 and the short schedule [was Re: Fedora 27 Change Checkpoint: Completion deadline (testable)]

On Wed, Aug 02, 2017 at 10:49:58AM -0400, Owen Taylor wrote: > I've been pushing hard to have the infrastructure changes ready on > the F27 timescale, because we don't like to make unrelated > infrastructure changes during the later stages of a release, and if > we wait to land the things until

Re: F27 and the short schedule [was Re: Fedora 27 Change Checkpoint: Completion deadline (testable)]

On Wed, 2017-08-02 at 09:31 -0400, Matthew Miller wrote: > On Wed, Aug 02, 2017 at 03:03:29PM +0200, Jan Kurik wrote: > > > Collectively, are there other F27 changes that seem really key to > > > release this year? If possible, I'd like to target any bigger changes > > > for F28 (or, unlink them

Re: F27 and the short schedule [was Re: Fedora 27 Change Checkpoint: Completion deadline (testable)]

On Wed, Aug 02, 2017 at 03:03:29PM +0200, Jan Kurik wrote: > > Collectively, are there other F27 changes that seem really key to > > release this year? If possible, I'd like to target any bigger changes > > for F28 (or, unlink them from the release itself). > > Checking the scope of the F27 [1] I

Re: F27 and the short schedule [was Re: Fedora 27 Change Checkpoint: Completion deadline (testable)]

On Wed, Aug 2, 2017 at 2:47 PM, Matthew Miller wrote: > On Wed, Aug 02, 2017 at 01:24:21PM +0200, Kevin Kofler wrote: >> It is really sad that FESCo is still maintaining this completely unrealistic >> kamikaze schedule. We have seen from the fallout of the mass rebuild

F27 and the short schedule [was Re: Fedora 27 Change Checkpoint: Completion deadline (testable)]

On Wed, Aug 02, 2017 at 01:24:21PM +0200, Kevin Kofler wrote: > It is really sad that FESCo is still maintaining this completely unrealistic > kamikaze schedule. We have seen from the fallout of the mass rebuild that > this is absolutely impossible to hold, the release will be completely broken