From 2f5ce201ff278692e218c1e72a7db0736c060799 Mon Sep 17 00:00:00 2001 From: brendancol Date: Thu, 25 Apr 2024 16:13:11 -0400 Subject: [PATCH] removed some older doc steps --- RELEASE.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index b08038d0..f95c1fdb 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -3,8 +3,6 @@ ### Preparation - Create a new branch containing the following changes: - Update CHANGELOG.md with new version number and list of changes extracted from `git log --pretty=oneline --pretty=format:"- %s" ..HEAD`. - - Add the new version reference in `xarray-spatial/docs/source/releases.json` - - Check that the new version number is included in `smv_tag_whitelist` in `docs/source/conf.py` so that the docs will be built and uploaded by CI. - Commit changes and submit them as a PR to the `master` branch. - If the CI passes OK, merge the PR. @@ -29,7 +27,8 @@ git push --tags - Click `Publish release`. ### Documentation -- When the github release is created, a github action automatically builds the documentation and uploads it to https://xarray-spatial.org/. This can take more than an hour to finish. + +- When the github release is created, a github action automatically builds the documentation and uploads it to https://xarray-spatial.readthedocs.io/. ### conda-forge packages - A bot in https://github.com/conda-forge/xarray-spatial-feedstock runs periodically to identify the new PyPI release and update the conda recipe appropriately. This should create a new PR, run tests to check that the conda build works, and automatically upload the packages to conda-forge if everything is OK. Check this works, a few hours after the PyPI release.