On 18 June 2018 at 09:21, Dusty Mabe <dusty(a)dustymabe.com> wrote:
On 06/18/2018 03:25 AM, Peter Robinson wrote:
> On Fri, Jun 15, 2018 at 10:21 PM, Joe Doss <joe(a)solidadmin.com> wrote:
>> Hello!
>>
>> 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.
Yeah we build images every night (I talked to Joe about it), but as far
as I know we haven't "released" any updated images after GA, even for
security
issues, for some time.
Please define "release" as it can mean different things to different
groups. If you ask QA you will get one definition. If you ask release
engineering you will get a similar but slightly different one. And
various other groups have their own what constitutes a release. Using
the term in general leads to long threads where people are either in
violent agreement or completely arguing past each other for a long
time.
Dusty
_______________________________________________
cloud mailing list -- cloud(a)lists.fedoraproject.org
To unsubscribe send an email to cloud-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.o...
--
Stephen J Smoogen.