Update README.md (#85)

README.md

@@ -115,4 +115,5 @@ Each specification MUST thoroughly document how it is intended to be implemented
    1. At least two OCFL Editors have "[Approved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews)" the pull-request
    1. At least one other community member has "[Approved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews)" the pull-request
    1. The approvers represent three distinct organizations
-1. After the pull-request has been merged with `NNNN` as a placeholder for the extension number in the _Registered Name_, an OCFL Editor will determine the extension number based on the next sequentially available number. They will create an additional administrative pull-request to change `NNNN` to the appropriate number in the extension file name and the extension document itself, as well as adding an entry to the index page entry (`docs/index.md`).
+1. After the pull-request has been merged with `NNNN` as a placeholder for the extension number in the _Registered Name_, an OCFL Editor will determine the extension number based on the next sequentially available number. They will create an additional administrative pull-request to change `NNNN` to the appropriate number in the extension file name and the extension document itself, as well as adding an entry to the index page entry (`docs/index.md`). This PR and any formatting fixes may be merged without additional review.
+1. When the merge and any adjustment is complete, a github release should be created with the ISO8601 date as the release tag, and a message indicating changes since the last release. This should be pushed to Zenodo and will be available from [DOI 10.5281/zenodo.7148497](https://doi.org/10.5281/zenodo.7148497)