From 69ecd1e31e0b29d0fb1b762f3b195d12325967dc Mon Sep 17 00:00:00 2001 From: Robert Schweikert Date: Fri, 3 Jan 2025 14:05:14 -0500 Subject: [PATCH] Life-cycle change Per agreement with Product Management we will refresh inactive images on a 3 month scycle. Update the documentation to reflect this change in life-cycle policy. --- xml/cha_images.xml | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/xml/cha_images.xml b/xml/cha_images.xml index 425e3a4..c8ad308 100644 --- a/xml/cha_images.xml +++ b/xml/cha_images.xml @@ -38,9 +38,9 @@ - Images in an active state are refreshed every three - months. Replaced images are moved to the deprecated - state. + Images in active and inactive + states are refreshed every three months. Replaced images are moved to + the deprecated state. @@ -48,8 +48,9 @@ If a critical security vulnerability occurs, images in active and inactive states are updated as soon as possible once the fix for the affected code is - available. For images in active state the three month - timer restarts with this forced replacement. + available. For images in active and + inactive states the three month timer restarts with + this forced replacement. &suse; is committed to address all security vulnerabilities disclosed @@ -99,7 +100,7 @@ Inactive images are supported following the rules of LTSS or ESPOS and - will only get refreshed for critical security updates. The duration term + will get refreshed at least every three months. The duration term is defined by the product. For more information, refer to