On ti, 22 tammi 2019, Matthew Miller wrote:
On Tue, Jan 22, 2019 at 10:29:28AM +0100, Jakub Jelinek wrote:
> I'm sorry, I forgot to create the every year feature request for GCC this
> year and only realized that when I've successfully built first non-scratch
> gcc 9 rpms. I believe Carlos has been mentioning GCC when F30 mass rebuild
> has been discussed and GCC updates is something that has been done every
> year in Fedora since at least Fedora 9 (we've skipped GCC 4.2 release back
> in 2007).
That's all true, but the change process still helps us coordinate. There are
many new people in Fedora every year, and the more we have documented and
explicit rather than "oh yeah, this happens every year", the better.
It sounds like you're thinking of it a little as "bureaucratic paperwork
where we pretend that there's some debate about whether we're going to
continue doing a completely normal thing". But it's not that. It's "the
process for making sure our routine update to GCC across the whole distro
goes smoothly for everyone".
To add to what Matthew said, I'll show another
example:
https://fedoraproject.org/wiki/Changes/NSSLoadP11KitModules was passed
in Fedora 29 without real communication with actual complex users of nss
databases in Fedora (FreeIPA, Dogtag) even though we are working in a
common understanding that something like that was needed.
As result, it broke use of SoftHSM in FreeIPA and Dogtag and continues
to be a blocker for our effort to add support of hardware-based security
modules in FreeIPA. We have to deal with the fact that now a lot of work
have to be directed into workarounding what looked as a nice logical
global change in Fedora.
Needless to say, neither FreeIPA nor Dogtag were mentioned in the change
and weren't consulted.
--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland