Summary/Minutes from today's FESCo Meeting (2015-01-07)

[Jaroslav Reznik]

----- Original Message -----
> On Wed, Jan 14, 2015 at 4:32 AM, Jaroslav Reznik <jreznik at redhat.com> wrote:
> > ----- Original Message -----
> >> On Tue, 2015-01-13 at 15:58 -0700, Kevin Fenzi wrote:
> >> > The Fedora 21 mass rebuild took about 40 hours. ;)
> >>
> >> BTW, https://fedoraproject.org/wiki/Fedora_22_Mass_Rebuild is empty.
> >> What are the goals of a mass rebuild now, given that we just had one
> >> before F21 Beta?
> >
> > This is actually that reason I liked how we constructed schedule last two
> > releases - based on proposed changes, taking look what needs mass rebuild
> > etc. And it could even end with no mass rebuild (or mass rebuild request
> > can come on Jan-20 when the deadline for changes is). But I was alone
> > who liked the old-new way and FESCo decided to set schedule the old-old
> > way, I'm just the guy who puts it to the wiki :).
> 
> You aren't alone.  I'm still not convinced the strict time-based
> schedule will work, but most of FESCo wanted to give it a shot.
> Rather then be a stick in the mud, I went with "don't be afraid to
> fail".
>
> Who knows, maybe it will work out.  If it does, I think it's going to
> change some of the things people expect from Fedora in both good and
> bad ways.  Good, delivered on time.  Bad (maybe), delivered with less
> cutting-edge packages.

I didn't mean it bad and yes - the result may lead to less cutting
edge packages but on the other hand with predictable schedule, you know
the next window is pretty soon (within 6 months). I'm just not convinced
(planned) slips are that big deal (unless Phoronix forum complaints
makes it a big deal;-). It can put more stress on folks, flexibility
has some costs but... And we have that power to define what Fedora
should be and I accepted it :). 

Jaroslav

> josh
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct