Fedora I’d guess shouldn’t be affected at all. They’re fully upstream. They work on upstream, and then CentOS pulls from them. I will say that Red Hat management sometimes forces them into new code that isn’t ready for RHEL. Best example if I remember ride would be the upgrader they have. I can’t remember the name atm, but 6 months before RHEL’s 8 release we found out about it and Fedora scrambled to get it in and get it tested.
I think the application was LEAPP. I think it was this app they forced in. Kind of like they forced Docker into RHEL 7 before it was ready. LEAPP (pronounced lay-app) was going to help in place upgrades. I basically put the devs feet under the fire, because my team members were going to be the ones supporting it, and they couldn’t answer a LOT of question. Just kept saying “Well we tell customers to have to have backups.” Which yes we did, but we’d still be forced to support shit that broke, because managers didn’t understand a thing and would just tell us to fix it.
How does this affect Fedora?
Fedora I’d guess shouldn’t be affected at all. They’re fully upstream. They work on upstream, and then CentOS pulls from them. I will say that Red Hat management sometimes forces them into new code that isn’t ready for RHEL. Best example if I remember ride would be the upgrader they have. I can’t remember the name atm, but 6 months before RHEL’s 8 release we found out about it and Fedora scrambled to get it in and get it tested.
I think the application was LEAPP. I think it was this app they forced in. Kind of like they forced Docker into RHEL 7 before it was ready. LEAPP (pronounced lay-app) was going to help in place upgrades. I basically put the devs feet under the fire, because my team members were going to be the ones supporting it, and they couldn’t answer a LOT of question. Just kept saying “Well we tell customers to have to have backups.” Which yes we did, but we’d still be forced to support shit that broke, because managers didn’t understand a thing and would just tell us to fix it.