Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-7592

Summarise upstream PR and update docs

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • AI
    • Summarise upstream PR and update docs
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do

      Epic Goal

      • Based on a PAR, generate documentation that can be given to the docs team. The documentation should have
        • Summary/PR description
        • Details of commits
        • Usage examples
        • How does the change impact customer

       

      Why is this important?

      • This will reduce the time spent by developers to generate documentation and release notes.

      Scenarios

      1. ...

      Acceptance Criteria (Mandatory)

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      •  

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

              Unassigned Unassigned
              rh-ee-ntatinen Navya Tatineni
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: