Post-Publishing Tests Checklist
Closed this issue · 0 comments
gkwan-ibm commented
Post-Publishing Tests
- Check appearance (contents, headings, paragraphs, code snippets, outputs, links) of the guide on openliberty.io
- Clone repo and test finish directory with no error
Other post-publishing tasks (to be done by the Admin Team)
- Add description for the repo with link to guide's published website
- Double check the SEO title and description are added for the guide
- Create the Home and Branches wiki pages
- Ensure automated test for PR and Continuous Tests are enabled for both
master
andqa
branches and are run on Travis, see instruction - Ensure the automated tests are running successfully for the daily builds
- Ensure the automated tests are running successfully for the daily docker image, if the guide uses a docker image
- Enable pull creation notification on the repo for
was-lib-guides-alerts
, see instruction - Enable
master
andqa
branches lock down, see instruction- make sure the Branch protection rules were created
- Add the new guide's repo to the
OpenLiberty/guides-common
ZenHub board - Delete
dev
branch - Send announcement to slack channels
- dev_advocates_java
- was-lib-guides-dev
- was-gm-testing
- Arrange a demo at the EOI meeting