oVirt developers community, I see there are a few enhancements submitted in GitHub: engine: Add amt_ws fence agent support <https://github.com/oVirt/ovirt-engine/pull/810> Notification emails merging and localization <https://github.com/oVirt/ovirt-engine/pull/798>
And also some rebase proposal: Rebase on WildFly 26 <https://github.com/oVirt/ovirt-engine/issues/637> Which would probably make more sense to be targeted to an oVirt 4.6 than a 4.5.z. There are now about three hundreds Untargeted issues(no milestone set) <https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Aovirt+archived%3Afalse+no%3Amilestone> to be triaged and about sixty Untargeted PRs (no milestone set) <https://github.com/pulls?q=is%3Aopen+is%3Apr+user%3Aovirt+archived%3Afalse+no%3Amilestone> to be reviewed. Some of them might be ready for a 4.5.z bugfix release while others can wait for a 4.6. Anyone willing to step in to lead the oVirt 4.6 development? A year has passed since my blog post about the future of the oVirt project <https://blogs.ovirt.org/2022/02/future-of-ovirt-february-2022/> but the concept is the same: oVirt future depends on how you, the community! Come help contribute to this new future <https://ovirt.org/develop/>! CC users community in case someone wants to jump into development as well. Regards, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System Red Hat EMEA <https://www.redhat.com/> sbona...@redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-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/devel@ovirt.org/message/RWXBKOFD3MZ4SXNAOP5YUNXFJI4X6PBS/