-
Story
-
Resolution: Duplicate
-
Critical
-
builds-1.2
-
None
Story (Required)
As a developer trying to build apps with Shipwright I want to use a Red Hat built version of the `shp` CLI.
<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>
Background (Required)
<Describes the context or background related to this story>
With each release, we should be providing an updated version of the CLI with the latest upstream fixes and features.
Out of scope
<Defines what is not included in this story>
TBD
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
TBD
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
TBD
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met
- duplicates
-
BUILD-1144 Release Engineering for Builds 1.2
- In Progress