Remove references to spec-prod

Author: joshmoore

README.md

@@ -9,18 +9,14 @@
 Specifications are written in markdown, or technically
 [bikeshed](https://github.com/tabatkins/bikeshed) -- a markdown document, with
 special extensions understood by the bikeshed tool. The bikeshed tool is run
-on-commit via the [spec-prod github action](https://github.com/w3c/spec-prod),
-generating the familiar "spec looking" ReSpec format. ReSpec is just html with
-a javascript ReSpec library.
-
-Specification files end with the .bs file extension. The github action runs on
-commit to automatically convert to respec/html, via bikeshed. 
+during the Sphinx build step (see conf.py).
 
 [Learn more about bikeshed](https://w3c-ccg.github.io/bikeshed_instructions.html)
 
 ## Reviewing
 
-Commits on GitHub can be viewed using web services from the W3C:
+Commits on GitHub can be viewed at PR-numbered URLs provided by readthedocs.
+Additionally, bikeshed pages can be viewed using web services from the W3C:
 
  * Rendered page: http://api.csswg.org/bikeshed/?url=https://raw.githubusercontent.com/ome/ngff/master/0.2/index.bs
  * Diff: https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fngff.openmicroscopy.org%2F0.2%2F&doc2=http%3A%2F%2Fapi.csswg.org%2Fbikeshed%2F%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fome%2Fngff%2Fmaster%2Flatest%2Findex.bs
@@ -46,24 +42,22 @@ specification document using the
 [include-code](https://tabatkins.github.io/bikeshed/#including-code) directive.
 
 The official OME-NGFF JSON schemas are published under
-https://ngff.openmicroscopy.org/<version>/schemas/<schema_name>.schema using the
-[Spec prod](https://github.com/ome/spec-prod) GitHub action. When a new JSON schema is introduced,
-this action needs to be reviewed to update the deployment script and allow the publication
-of the schema.
+https://ngff.openmicroscopy.org/<version>/schemas/<schema_name>.schema.
 
 # Release process
 
-* copy `latest/index.bs` to `$VERSION/index.bs`
-* copy `latest/copyright.include` to `$VERSION/copyright.include`
-* update the head matter in the `$VERSION`ed file
-  * Use: `Status: w3c/CG-FINAL`
-  * Update `URL: `
-  * Use the following `Status Text:`: "This is the $VERSION release of this specification.
-    Migration scripts will be provided between numbered versions. Data written with the latest version
-    (an "editor's draft") will not necessarily be supported."
-* update the footer matter in the `$VERSION`ed file
-  * Version in the citation block including release date
-* Update https://github.com/ome/spec-prod for the new version
+* For patch releases, bump the submodule for the given version.
+* For minor and major versions, add a new submodule location for the version branch.
+* Check and update:
+  - copyright.include
+  - the head matter in the `$VERSION`ed file
+    * Use: `Status: w3c/CG-FINAL`
+    * Update `URL: `
+    * Use the following `Status Text:`: "This is the $VERSION release of this specification.
+        Migration scripts will be provided between numbered versions. Data written with the latest version
+        (an "editor's draft") will not necessarily be supported."
+  - update the footer matter in the `$VERSION`ed file
+  - Version in the citation block including release date
 
 # Citing