Release process setup and documented - Githubissues

bcgov / cas-reporting

This is for the Clean Growth Digital Services team for work related to reporting.

Apache License 2.0

0 stars 0 forks source link

Release process setup and documented #107

Closed pbastia closed 8 months ago

pbastia commented 8 months ago

Description:

As a developer, I want to have a release process implemented and documented, so that I can deploy releases of the Reporting app

Implement release-it Document release process

Acceptance Criteria:

Given I am a developer When I want to cut a release Then I have the step-by-step documentation And following it creates a release

Development Checklist:

[ ] Checklist item
[ ] Checklist item
[ ] Checklist item
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

-

pbastia commented 8 months ago

Closing, this is unnecessary since we're not publishing packages