Post-Publishing Tests Checklist

[gkwan-ibm]

Post-Publishing Tests

• [x] Check appearance (contents, headings, paragraphs, code snippets, outputs, links) of the guide on openliberty.io
• [x] Clone repo and test finish directory with no error

Other post-publishing tasks (to be done by the Admin Team)

• [x] Add description for the repo with link to guide's published website
• [x] Double check the SEO title and description are added for the guide
• [x] Create the Home and Branches wiki pages
• [x] Ensure automated test for PR and Continuous Tests are enabled for both master and qa branches and are run on Travis, see instruction
• [x] Ensure the automated tests are running successfully for the daily builds
• [x] Ensure the automated tests are running successfully for the daily docker image, if the guide uses a docker image
  • no need to run because other guides, e.g. kube, openshift guides can cover
• [x] Enable pull creation notification on the repo for was-lib-guides-alerts, see instruction
• [x] Enable master and qa branches lock down, see instruction
  • make sure the Branch protection rules were created
• [x] Add the new guide's repo to the OpenLiberty/guides-common ZenHub board
• [x] Delete dev branch
• [x] (Optional) Send announcement to slack channel(s)
• [x] Arrange a demo at the EOI meeting