Feature Overview (aka. Goal Summary)

Customers are wondering if they should upgrade to each version of RHDH or they can skip. For example, upgrading RHDH 1.5 to 1.7 directly or to 1.6 then 1.7

Goals (aka. expected user outcomes)

Add a new step in the upgrade documentation to let the customer know that they can upgrade RHDH directly to the latest version, but they will have to check each release notes to find the breaking changes. For example, if upgrading from 1.5 to 1.7, the customer needs to check the Release Notes from 1.6 and 1.7

Requirements (aka. Acceptance Criteria):

• Update the upgrade documentation to let the customer know or remind them to check the all the release notes from their current version to the latest release.
• The documentation should be for both the Helm and the Operator.

  Who is your target persona?
  

  <Role>
  

  What stage of the user journey are you targeting?
  

  <User journey>
  

  Why is this content important?
  

  <Justification>
  

  What is the main user goal aka job to be done?
  

  As a <role>, I want to <goal>
  

  What high level steps does the user need to take to accomplish the goal?
  

1. <User steps to accomplish goal>
   

What pain points are the user likely to encounter when accomplishing this goal?

<Pain points>

Links to existing content

• <Add link to content>
  

People:

• SME: <SME>
  
• QE: <QE>
  

Release Note: Yes/No

Documentation Outline

• <Documentation outline>