Open Stack

On 2018-05-13 20:44:25 -0600 (-0600), Wesley Hayutin wrote:
[...]
> I do think it would be helpful to say have a one week change
> window where folks are given the opportunity to preflight check a
> new image and the potential impact on the job workflow the updated
> image may have. If I could update or create a non-voting job w/
> the new image that would provide two things.
> 
> 1. The first is the head's up, this new minor version of centos is
> coming into the system and you have $x days to deal with it.
> 
> 2. The ability to build a few non-voting jobs w/ the new image to
> see what kind of impact it has on the workflow and deployments.
[...]

While I can see where you're coming from, right now even the Infra
team doesn't know immediately when a new CentOS minor release starts
to be used. The packages show up in the mirrors automatically and
images begin to be built with them right away. There isn't a
conscious "switch" which is thrown by anyone. This is essentially
the same way we treat Ubuntu LTS point releases as well. If this is
_not_ the way RHEL/CentOS are intended to be consumed (i.e. just
upgrade to and run the latest packages available for a given major
release series) then we should perhaps take a step back and
reevaluate this model. For now we have some fairly deep-driven
assumptions in that regard which are reflected in the Linux
distributions support policy of our project testing interface as
documented in OpenStack governance.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180514/85cffa75/attachment.sig>