4 ms·

"There is no expectation for dedicated engineer time or solving their support cases" Sorry, but yes there is. The final product includes the outcome of all tha

by jzb 3y ago

"There is no expectation for dedicated engineer time or solving their support cases" Sorry, but yes there is. The final product includes the outcome of all that. Especially the minor and z-stream releases are the culmination of all the work of customers reporting bugs and Red Hat applying that dedicated engineer time and solved support cases to the next release. There are many companies (including the one I work for) who treat clones as equivalent to RHEL. So, yes, it effectively conveys many of the certifications and system requirements to receive support from other companies. The clones have been promising "bug-for-bug" compatibility for a reason, and that reason is (in part) to ride the certification coat-tails. If these things were not true, there'd be none of this drama. Rocky and Alma could easily base Linux distros off Stream and do additional testing and add or modify features to be more interesting. The code is there. The product is not.

vetinari 3y ago
> are the culmination of all the work of customers reporting bug Aren't these supposed to go into Stream? > So, yes, it effectively conveys many of the certifications and system requirements to receive support from other companies. The clones have been promising "bug-for-bug" compatibility for a reason, and that reason is (in part) to ride the certification coat-tails. Yet, it is not the same as certifications. Certifications apply only to the original RHEL; clones are in the gray zone: it should work, but if there are problems and you need to use them, you better have it on RHEL. > If these things were not true, there'd be none of this drama. The drama is there, because RH/IBM thought, they could squeeze those customers, that use both CentOS and RHEL (usually CentOS for dev or staging and RHEL for production); they wanted it all. I can understand if those companies file support cases that originated in CentOS and RH things, that they abuse their support contract. That's not OK. But RH has it's own skeletons in closet, too. The clones themselves are a collateral damage there.

by jzb 3y ago

vetinari 3y ago

> are the culmination of all the work of customers reporting bug Aren't these supposed to go into Stream? > So, yes, it effectively conveys many of the certifications and system requirements to receive support from other companies. The clones have been promising "bug-for-bug" compatibility for a reason, and that reason is (in part) to ride the certification coat-tails. Yet, it is not the same as certifications. Certifications apply only to the original RHEL; clones are in the gray zone: it should work, but if there are problems and you need to use them, you better have it on RHEL. > If these things were not true, there'd be none of this drama. The drama is there, because RH/IBM thought, they could squeeze those customers, that use both CentOS and RHEL (usually CentOS for dev or staging and RHEL for production); they wanted it all. I can understand if those companies file support cases that originated in CentOS and RH things, that they abuse their support contract. That's not OK. But RH has it's own skeletons in closet, too. The clones themselves are a collateral damage there.