Adam Williamson wrote:
> So, during the blocker review process in the last few cycles, we have
> several times come up against the unfortunate situation that a bug that
> in the usual course of events would block a release is discovered
> extremely late - say the day before the go/no-go meeting - and at least
> some folks have argued that it's sometimes appropriate to not block the
> release in this case.
>
> This position has gained quite a bit of acceptance, and we agreed at
> the F26 Final go/no-go meeting to draft up some formal policy for this
> so we can make such decisions consistently and not in an ad hoc way
> that might lead to it becoming a loophole that gets abused.
IMHO, this is a slippery slope eroding the quality of Fedora just because
some people are not willing to wait a week longer for their "fix". The
argument that this steals time from the next cycle is also invalid, because
the obvious answer there is: "Don't Do That Then" – the schedule for the
next release needs to start from the ACTUAL release date of the current
release, NOT the planned release.
There is at least one user a day asking on #fedora-kde about the Discover
issue that you decided to ignore in violation of the process, and no doubt
there are many more who don't bother asking and just wipe Fedora and install
Kubuntu or Neon instead. The bug would have been trivial to fix.
A blocker ought to be a blocker, no matter when it is discovered and how
long it takes to fix.
Kevin Kofler
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
