SPIKE Story (Required)

<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?>

As a Shipwright maintainer trying to support a "stable" release version I want the project to adopt a release branch strategy.

Background (Required)

<Describes the context or background related to this story>

Projects that declare themselves "beta" tend to provide a stable release branch, so they can issue security updates and other bug fixes to the community without delivering unstable or risky features.

Out of scope

<Defines what is not included in this story>

• Implementing release branch strategy (and releases from release branches) upstream.

Approach (Required)

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

• Start discussion upstream via GitHub issue
• Propose a release process via SHIP (enhancement proposal)
• Work with upstream to get agreement

Dependencies

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

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