Uploaded image for project: 'Samples Operator'
  1. Samples Operator
  2. SO-100

customer Doc Change indicating the deprecation

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Samples Operator
    • AppSvc Sprint 232

      Owner: Architect:

      Feny 

      Story (Required)

      The customer should be informed  about the downsizing of samples operator, So the official Samples Operator document for OCP 4.13 should reflect the same.  Collaborate with the Docs team for the same

      Background (Required)

      <Describes the context or background related to this story>

      Glossary

      <List of new terms and definition used in this story>

      Out of scope

      <Defines what is not included in this story>

      In Scope

      <Defines what is included in this story>

      Approach(Required)

      _<Description of the general technical path on how to achieve the goal of
      the story. Include details like json schema, class definitions>_

      Demo requirements(Required)

      _<Description of demo which would show the value of this story. Any demo
      should also be included as part of the acceptance criteria.>_

      Dependencies

      _<Describes what this story depends on. Dependent Stories and EPICs should
      be linked to the story.>_

      Edge Case

      _<Describe edge cases to consider when implementing the story and defining
      tests>_

      Acceptance Criteria

      _<Provides a required and minimum list of acceptance tests for this story.
      More is expected as the engineer implements this story>_

      Development:

      QE:
      Documentation: Yes/No (needs-docs|upstream-docs / no-doc)

      Upstream: <Inputs/Requirement details: Concept/Procedure>/ Not
      Applicable

      Downstream: <Inputs/Requirement details: Concept/Procedure>/ Not
      Applicable

      Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
      fix/Breaking change/Deprecated Functionality/Technology Preview>

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      v

      Legend

      Unknown

      Verified

      Unsatisfied

              fmehta@redhat.com Feny Mehta
              fmehta@redhat.com Feny Mehta
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: