Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

When using the `helm cli` tool, it should be clear which version of the tool is supported and how compatible it is with the currently supported OCP versions without guessing.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

We should have a clear support policy for helm cli tool and OCP versions. This support policy will define clearly and without guesses:

(1) which version of the tool is supported today 

(2) which OCP versions this version of helm cli is compatible/supported with.

We need to have a support matrix tested by QE reflecting this support policy.

As a cluster admin/developer using helm cli I need to know which version of helm cli I should use.

As a helm team software developer I need to know what are my obligations to the customer - which versions of the tool need to have bugfixes and CVEs, and which versions are out of support.

As a Red Hat employee working with customers using helm cli I need to have clarity about support configurations to ensure we provide the required support to our customers defined by the support policy.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

<enter general Feature acceptance here>

1. We have a written policy in our public docs explaining how the tool is supported.
2. We have the required tests in place to assure the compatibility matrix is provided.
3. We adjust our development practices to adhere with the agreed on policy.

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>