It's not just the kernel development that shows how Red Hat is becoming more "closed" or self-centered, the number of bugzilla entries that are private (closed to the public) is also worrisome.
As an example that I ran into yesterday, the bugfix announcement of Red Hat Satellite yesterday has 7 references to bugzilla entries, and none of them are open to the public. So putting them in the announcement is basically to help Red Hat engineers/consultants but Red Hat customers are left out in the dark.
https://rhn.redhat.com/errata/RHBA-2014-0228.html
So when we found a few regressions in the Satellite product we could not look into the what-and-why's or even engage in any discussion. This makes it impossible to assess the risk of a security/bugfix update.
Power management, mobile and firmware developer on Linux. Security developer at Aurora. Ex-biologist. mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer. Also on Mastodon.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Also bugzilla entries are more frequently closed to the public
Date: 2014-03-04 09:05 am (UTC)As an example that I ran into yesterday, the bugfix announcement of Red Hat Satellite yesterday has 7 references to bugzilla entries, and none of them are open to the public. So putting them in the announcement is basically to help Red Hat engineers/consultants but Red Hat customers are left out in the dark.
https://rhn.redhat.com/errata/RHBA-2014-0228.html
So when we found a few regressions in the Satellite product we could not look into the what-and-why's or even engage in any discussion. This makes it impossible to assess the risk of a security/bugfix update.