Steve-Dee-Designs
/
woocommerce
mirror of https://github.com/woocommerce/woocommerce.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add expected folder for testing instructions to the release PR template (https://github.com/woocommerce/woocommerce-blocks/pull/2677) 

* Add expected folder for testing instructions to the release PR template

* update release doc

Co-authored-by: Darren Ethier <darren@roughsmootheng.in>
This commit is contained in:
Albert Juhé Lluveras 2020-06-09 17:50:15 +02:00 committed by GitHub
parent 211728b401
commit 27c68c520d
2 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
plugins/woocommerce-blocks/.github/release_pull_request_template.md vendored
View File

@ -72,7 +72,7 @@ those and list here as checklist items. You can have different engineers write t
* [ ] The release affects filters or action hooks.
* [ ] This is documented (see: <!-- Enter a link to the documentation here -->)
* [ ] Link to **testing instructions** for this release: <!-- Enter a link to the testing instructions here -->
* [ ] Link to **testing instructions** for this release: <!-- Enter a link to the testing instructions here, ideally in /docs/testing/releases -->
* [ ] The release has a negative performance impact on sites.
* [ ] There are new assets (JavaScript or CSS bundles)

3
plugins/woocommerce-blocks/docs/releases/readme.md
View File

@ -90,6 +90,7 @@ _Outcome_: **Release branch has all relevant changes merged & pushed and there i
- Make any other changes to readme as needed - e.g. support versions changing, new blocks.
- Push readme changes to release branch on origin repo.
- Note: you can push your readme changes directly to branch – no need for a PR & review process.
- Create testing notes for the release (you might be able to copy some from the pulls included in the release). Add the notes to [`docs/testing/releases`](../testing/releases/) (and update the [README.md index](../testing/releases/README.md) there)
_Outcome_: **Release branch has `readme.txt` is updated with release details.**
@ -108,7 +109,7 @@ _Outcome_: **Release branch has `readme.txt` is updated with release details.**
- Test to confirm new features/fixes are working correctly.
- Smoke test – test a cross section of core functionality.
- Tests performed should be recorded and listed in the release pull request.
- Ask a team member to review the changes in the release pull request and for anyone who has done testing that they approve the pull request. **Remember release pull requests are just used for tracking the release and are not merged into master**.
- Ask a team member to review the changes in the release pull request and for anyone who has done testing that they approve the pull request.
_Outcome_: **Confident that source code is ready for release: intended fixes are working correctly, no release blockers or build issues.**