Adam Williamson wrote:
> This cycle was actually kind of an interesting case, because on the one
> hand, there's a pretty good argument that we were in a very bad state
> at freeze time this cycle. On the *other* hand, one of the main reasons
> we were in a bad state is because people kept frickin' landing de-
> stabilizing changes while we were still dealing with the fallout from
> the previous de-stabilizing change: we've had GCC 8, various
> unannounced soname bumps, basically all of nu-Modularity showing up in
> the middle there somewhere, anaconda modularization, new versions of
> pungi and pykickstart and systemd, and that's just the things I
> *remember*. It's been something of a wild ride.
The reason why there are so many major changes in F28 is pretty clear: the
F27 cycle was too short! Hardly any major change made it in there. So we now
get double the changes.
Kevin Kofler
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
