Goal

• < Goal-based statement, with context>
  • For example: As a <user/actor>, I Want <to achieve some goal>, so that <some reason/context>.
  • RHEL Sustaining Engineering organization is responsible for handling defects/bugs and CVEs in any extended life streams/offerings of RHEL, such as EUS, TUS, E4S, AMC/AUS and ELS.

Scope: Critical and Important impact security updates and urgent-priority bug fixes

Versions: rhel-6-els, rhel-7.7.z, rhel-7-els, rhel-8.2.z, rhel-8.4.z, rhel-8.6.z, rhel-8.8.z, rhel-9.0.z, rhel-9.2.z, rhel-9.4.z

 
Acceptance Criteria:

<A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.>

• Assemble a component list supported under this sst
• List location of any repositories
• Pointers to user documentation
• Plan an initial walk through the components with one of our engineers and their team. Gather their questions and plan next steps.
• requirements of tools, skills, accesses. We look for existing documentations if available to go through.
•  This is then followed by a demo session with any ongoing change/JIRA to understand workflow better, if not walk through the process step by step for any Jira which is worked upon recently
• To able to handle the critical bugs and CVEs, SE team need to understand the current workflow for Development  and QE activities 
• Steps for backporting, Perliminary testing and regression testing
• POCs for dev and QE workflow

Note:

• We(SE) team are aware of TPS test execution under EWA for RHEL 8.x streams but TPS is done for RHEL 9.X
• We are aware of Errata creation and release process
• As of z stream release process for EUS/AUS/TUS/ELS and more(under SE scope as described above), we perform tasks in same manner which are done by product engineering team for release and updates