Currently, the spec has some bikeshed errors that prevent us from using bikeshed's methods for publishing a CR.

Instead it needs to be done manually. Here are the steps needed to do this:

1. Create a branch to hold the cr named cr-<yyyy>-<mm>-<dd> for the date the CR is expected to be published. Do NOT delete this branch. It will be used to keep track of the version used to create the CR.

2. Add the following to index.bs:

   Status: CR
   Date: 2020-12-15
   Deadline: 2021-01-15
   Prepare for TR: yes
   

3. Run compile.sh to verify the spec builds. If there are unexpected errors, please try to fix them.

4. When compile.sh works do the following:

   1. Use the create-cr.sh script to create a zip file named cr.zip` or manually create a zip file consisting of
      • index.html
      • implementation-report.html
      • test-report.html
      • style.css
      • favicon.png
      • images/*.png

The zip file should now contain everything needed for the updated CR.

As an example for the changes that might be needed, see PR 2283.

When the CR is published, make sure the branch has all of the changes. (Sometimes the publication date changes from the time the CR is done and when it gets published.) Then create a tag for this branch: git tag -a <tagname>. This creates an annotated tag which requires a tag message, creation date, tagger name and e-mail. Feel free to also use -s or -u to add a GnuPG signature to the tag.