Add step to update website after a release

Signed-off-by: Brandon Mitchell <git@bmitch.net>

RELEASES.md

@@ -70,7 +70,7 @@ Releases usually follow a few steps:
   - [ ] count the PRs since last release (that this version is tracking, in the cases of multiple branching), like `git log --pretty=oneline --no-merges --decorate $priorTag..$versionBumpCommit  | grep \(pr\/ | wc -l`
   - [ ] get the date for a week from now, like `TZ=UTC date --date='next week'`
   - [ ] OPTIONAL find a cute animal gif to attach to the email, and subsequently the release description
-  - [ ] subject line like `[runtime-spec VOTE] tag $versionBumpCommit as $version (closes $dateWeekFromNowUTC)`
+  - [ ] subject line like `[image-spec VOTE] tag $versionBumpCommit as $version (closes $dateWeekFromNowUTC)`
   - [ ] email body like
 
 ```text
@@ -92,7 +92,8 @@ $sig
 - [ ] produce release documents
   - [ ] git checkout the release tag, like `git checkout $version`
   - [ ] `make docs`
-  - [ ] rename the output PDF and HTML file to include version, like `mv output/oci-runtime-spec.pdf output/oci-runtime-spec-$version.pdf``
-  - [ ] attach these docs to the release on <https://github.com/opencontainers/runtime-spec/releases>
+  - [ ] rename the output PDF and HTML file to include version, like `mv output/oci-image-spec.pdf output/oci-image-spec-$version.pdf``
+  - [ ] attach these docs to the release on <https://github.com/opencontainers/image-spec/releases>
   - [ ] link to the the VOTE thread and include the passing vote count
   - [ ] link to the pull request that merged the release
+- [ ] add release notes to the website <https://github.com/opencontainers/opencontainers.org/tree/main/content/release-notices>