On Fri, Jun 15, 2018 at 10:21 PM, Joe Doss <joe@xxxxxxxxxxxxxx> wrote: > Hello! > > My name is Joe Doss and I want to help the Fedora Cloud SIG bring more > frequent tested releases of Fedora Cloud it's user base. The goal of this > project is to provide more frequent updates of Fedora Cloud to users on a > set cadence or on a case per case basis for major security events. > > One major pain point that Fedora Cloud currently faces is the fact that once > a new Fedora release comes out, the cloud images are no longer updated over > time. This brings a poor user experience if bugs that are fixed later on in > the current release cycle but are painful on the first boot of a Fedora > Cloud instance until the user updates the instance. That's not entirely true, the cloud images are updated for major security events. They are also built every day [1]. The issue is to date there's not been a proper process in which they're updated/communicated etc. Over all I welcome what you generally propose. > I reached out to Dusty Mabe and he agreed to mentor me on this project along > with help from Kellin and Mohan. > > The current ideas on the table for bringing this project to light are: > > * Standardize and improve Fedora Cloud tests > * Create a Fedora Cloud test day for these updates to help improve tests > * Set a release cadence policy post Fedora Release > * Set a security update policy for major security updates > > We will create issues under pagure.io/cloud-sig and try to get this project > rolling by Fedora 30 at the latest. Any comments or suggestions on this > topic are very welcome. [1] https://kojipkgs.fedoraproject.org/compose/cloud/ _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/cloud@xxxxxxxxxxxxxxxxxxxxxxx/message/WHAQNHBYBPYIPVMAV2NHQU6HPORFPLQI/