On Fri, Jun 5, 2020, 11:36 Michal Skrivanek <michal.skriva...@redhat.com>
wrote:

> Hi all,
> we would like to ask about interest in community about oVirt moving to
> CentOS Stream.
> There were some requests before but it’s hard to see how many people would
> really like to see that.
>
> With CentOS releases lagging behind RHEL for months it’s interesting to
> consider moving to CentOS Stream as it is much more up to date and allows
> us to fix bugs faster, with less workarounds and overhead for maintaining
> old code. E.g. our current integration tests do not really pass on CentOS
> 8.1 and we can’t really do much about that other than wait for more up to
> date packages. It would also bring us closer to make oVirt run smoothly on
> RHEL as that is also much closer to Stream than it is to outdated CentOS.
>
> So..would you like us to support CentOS Stream?
>
The answer is yes, though I do not see any other option, if I'm not
mistaken.

We don’t really have capacity to run 3 different platforms, would you still
> want oVirt to support CentOS Stream if it means “less support” for regular
> CentOS?
> There are some concerns about Stream being a bit less stable, do you share
> those concerns?
>
> Thank you for your comments,
> michal
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> 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/users@ovirt.org/message/3B5MJKO7BS2DMQL3XOXPNO4BU3YDL52T/
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
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/users@ovirt.org/message/XRDC2S6RKJ2BW7MJCTMLPD6Z5RSPODPX/

Reply via email to