Disable Win Py

.github/workflows/build.yml

@@ -108,6 +108,7 @@ jobs:
                 ./deploy/win_build.sh configure "win-${GITHUB_SHA:0:8}"
                 ./deploy/win_build.sh build
             - name: Build Python
+              if: false
               run: |
                 cd build
                 CI_COMMIT_BRANCH="${GITHUB_REF#refs/*/}"
@@ -142,6 +143,7 @@ jobs:
                 branch="${GITHUB_REF#refs/*/}"
                 ./deploy/win_build.sh deploy "$branch" "-i $PWD/privkey"
             - name: Upload Pypi
+              if: false
               env:
                 TWINE_PASSWORD: ${{ secrets.TWINE_PASSWORD_GITLAB }}
                 TWINE_USERNAME: __token__

.github/workflows/pypi.yml

@@ -53,6 +53,7 @@ jobs:
               run: |
                 ./deploy/gitlab_commit_status.py $RESULT
     windows:
+        if: false
         runs-on: windows-latest
         defaults:
             run:

docs/docs/contributing/code/misc.md

@@ -33,21 +33,22 @@ You can use the script that adds all that
 
 1. Update the version number on the root `CMakeLists.txt`
 2. Ensure `CHANGELOG.md` is up to date and changes are under the heading for the scheduled release
-3. Build the `release_0` target
-4. Wait for CI to complete <https://gitlab.com/mattbas/glaxnimate/-/pipelines>
-5. If there are errors
+3. Add release notes page to the docs
+4. Build the `release_0` target
+5. Wait for CI to complete <https://gitlab.com/mattbas/glaxnimate/-/pipelines>
+6. If there are errors
     * fix the errors
     * `./deploy/tag-branch.sh`
     * go back to 4.
-6. build the `release_1` target, this builds the `release` branch
-7. Wait for CI to complete
-8. In the tag pipeline, manually run the `release` job
-9. Wait for CI to complete
-10. New release should be ready at <https://gitlab.com/mattbas/glaxnimate/-/releases>
-11. Run the release validation jobs
+7. build the `release_1` target, this builds the `release` branch
+8. Wait for CI to complete
+9. In the tag pipeline, manually run the `release` job
+10. Wait for CI to complete
+11. New release should be ready at <https://gitlab.com/mattbas/glaxnimate/-/releases>
+12. Run the release validation jobs
     * https://gitlab.com/mattbas/glaxnimate/-/pipelines `release:check`
     * https://github.com/mbasaglia/glaxnimate/actions/workflows/verify_release.yml
-12. Merge `release` / `pre-release` back into master if there have been any new commits
+13. Merge `release` / `pre-release` back into master if there have been any new commits
 
 
 ## Creating/Editing AUR packages with docker