This was one of my fears regarding the IBM acquisition. I guess we can't complain too much, it's not like anybody *pays* for CentOS. :)
On 12/8/2020 3:14 PM, Strahil Nikolov via Users wrote: > Yeah, > the main problem is that Stream won't be as stable as RHEL (which also > has tons of bugs) and you will have to fight with bugs in the OS as if > I'm running a Fedota and on top of that - we have to be extra careful > for oVirt. > Also the Stream is quite new and we can't say if it will be as CentOS > was in the past. > > Best Regards, > Strahil Nikolov > > В 14:56 -0500 на 08.12.2020 (вт), Alex McWhirter написа: >> On 2020-12-08 14:37, Strahil Nikolov via Users wrote: >>> Hello All, >>> >>> I'm really worried about the following news: >>> https://blog.centos.org/2020/12/future-is-centos-stream/ >>> >>> Did anyone tried to port oVirt to SLES/openSUSE or any Debian-based >>> distro ? >>> >>> Best Regards, >>> Strahil Nikolov >>> _______________________________________________ >>> Users mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/[email protected]/message/HZC4D4OSYL64DX5VYXDJCHDNRZDRGIT6/ >> I fail to see a major issue honestly. If current RHEL is 8.3, CentOS >> Stream is essentially the RC for 8.4... oVirt in and of itself is >> also >> an upstream project, targeting upstream in advance is likely >> beneficial >> for all parties involved. >> >> CentOS has been lagging behind RHEL quite a lot, creating it's own >> set >> of issues. Being ahead of the curve is more beneficial than >> detrimental >> IMO. The RHEL sources are still being published to the CentOS git, >> oVirt >> node could be built against that, time will tell. >> >> Supported or not, i bet someone forks it anyways. >> _______________________________________________ >> Users mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/[email protected]/message/SM3JM6DHDCRJGH4LMGIKYOLCJKGWJKS4/ > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/535INKZGF22FIMJIVIADYNBUJ6J3P26U/ _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/FMEYSKCAV5WUJ7XNG3E2QS36NONBPSHF/
