Update release template

Currently testers are using google docs to store release tests. This is maybe overkill.

I've documented the steps here and the proposal is for testers to document their test in the release issue.

.github/ISSUE_TEMPLATE/release.md

@@ -27,6 +27,12 @@ assignees: ''
 - [ ] Move this issue to Test Ready.
 - [ ] Notify `@testers` in [#testing].
 - [ ] Test build: [Deploy to Staging] with release tag.
+- [ ] Check the following:
+      - [ ] Map is displayed correctly. Address changes are reflected in the map.
+      - [ ] Stripe with no authentication card: 4242424242424242 as shopper and as Admin. Order confirmation displays order as “Paid” 
+      - [ ] Stripe with Authentication required card: 4000002760003184 as shopper and as Admin. As admin, check authorization through customer account `/account#/transactions` and email
+       - [ ] Pay with Paypal
+       - [ ] Order on mobile
 - [ ] Notify a deployer to deploy it
 
 ## 3. Deployment at beginning of week
@@ -57,4 +63,4 @@ The full process is described at https://github.com/openfoodfoundation/openfoodn
 [Create issue]: https://github.com/openfoodfoundation/openfoodnetwork/issues/new?assignees=&labels=&projects=&template=release.md&title=Release
 [#delivery-circle]: https://openfoodnetwork.slack.com/archives/C01T75H6G0Z
 [Transifex Client]: https://developers.transifex.com/docs/cli
-[minor or major breaking changes]: https://github.com/openfoodfoundation/openfoodnetwork/pulls?q=label%3A%22breaking+change%22%2C%22major+breaking+change%22
+[minor or major breaking changes]: https://github.com/openfoodfoundation/openfoodnetwork/pulls?q=label%3A%22breaking+change%22%2C%22major+breaking+change%22