On Monday, February 1, 2021 3:55 PM, Neal Gompa ngompa13@gmail.com wrote:
On Mon, Feb 1, 2021 at 3:14 PM redbaronbrowser via CentOS-devel centos-devel@centos.org wrote:
On Sunday, January 31, 2021 7:14 AM, Peter Meier peter.meier@immerda.ch wrote:
I can't use CentOS Stream - it is beta quality and has critical bugs. For example: https://bugzilla.redhat.com/show_bug.cgi?id=1913806 This bug is critical for me, because I use systemd-nspawn containers for production. I will continue to use CentOS Stream in the future, but only as the beta-tester, to see what new will be in the future minor release of Oracle Linux / Alma Linux / Rocky Linux.
[...] And as a Stream user and contributor you can also add your use case to t_functional which in the end becomes gating for Stream. So you avoid future regression for your use case, although it is even not officially supported.
How? When? I still see no method to submit a pull request against the official CI/CD t_function sets. I also have not seen an ETA to being able to do so. Where is the example code of existing t_function sets? Where is the style/coding guide that must be followed to get new t_functions accept?
The functional tests are stored here:https://git.centos.org/centos/t_functional
You can make pull requests against it there.
I was under the impression that the RHEL team was sitting on much more than this. It seem like there was a good chance I would duplicating efforts on tests already done internally if I tried to contribute right now.
What exists looks like the level of testing I would expect of a *downstream* distribution. The amount of commits over the last three months also seem like downstream distribution level.
If this is the complete offering from the RHEL team to make Stream an upstream usable by 95% or more of CentOS users then that is very discouraging.
My personal perspective is we are having to recreate something to the level of Wikipedia from scratch in 11 months but at least most of the articles beginning with Z have been written.