Post 1.11.0 release actions done

ANNOUNCE.rst

@@ -15,11 +15,11 @@ In addition to extensions, we are distributing library
 binaries in the wheels too.  This way, people willing to use the C-Blosc
 library can make use of these wheels to install the necessary development
 files.  For details, see:
-https://github.com/Blosc/c-blosc/blob/master/COMPILING_WITH_WHEELS.rst
+https://github.com/Blosc/c-blosc/blob/main/COMPILING_WITH_WHEELS.rst
 
 For more info, you can have a look at the release notes in:
 
-https://github.com/Blosc/python-blosc/blob/master/RELEASE_NOTES.rst
+https://github.com/Blosc/python-blosc/blob/main/RELEASE_NOTES.rst
 
 More docs and examples are available in the documentation site:
 

RELEASE_NOTES.rst

@@ -8,7 +8,13 @@
 :URL: https://github.com/Blosc/python-blosc
 
 
-Changes from 1.10.6 to 1.10.7
+Changes from 1.11.0 to 1.11.1
+=============================
+
+#XXX version-specific blurb XXX#
+
+
+Changes from 1.10.6 to 1.11.0
 =============================
 
 * Internal C-Blosc sources updated to 1.21.2 (they are a git submodule now).
@@ -81,7 +87,7 @@ Changes from 1.9.2 to 1.10.0
   Also, we are distributing binaries for C-Blosc libraries (dynamic and static)
   and headers.  This way, people trying to use the C-Blosc library can use the
   python-blosc wheels to install the necessary development files.  For details,
-  see: https://github.com/Blosc/c-blosc/blob/master/COMPILING_WITH_WHEELS.rst
+  see: https://github.com/Blosc/c-blosc/blob/main/COMPILING_WITH_WHEELS.rst
 
   We gratefully acknowledge Jeff Hammerbacher for supporting the addition of
   wheels for Blosc.

RELEASING.rst

@@ -10,7 +10,7 @@ Releasing python-blosc
 Preliminaries
 -------------
 
-* Make sure that the current master branch is passing the tests on Github Actions.
+* Make sure that the current main branch is passing the tests on Github Actions.
 
 * Make sure that ``RELEASE_NOTES.rst``
   and ``ANNOUNCE.rst`` are up to date with the latest news in the release.
@@ -33,7 +33,7 @@ Updating the online documentation site
 Tagging
 -------
 
-* Create a signed tag ``X.Y.Z`` from ``master``.  Use the next message::
+* Create a signed tag ``X.Y.Z`` from ``main``.  Use the next message::
 
     $ git tag -s vX.Y.Z -m "Tagging version X.Y.Z"
 
@@ -64,13 +64,11 @@ Announcing
 Post-release actions
 --------------------
 
-* Make sure you are in the master branch.
+* Make sure you are in the main branch.
 
-* Edit ``VERSION`` in master to increment the version to the next
+* Edit ``VERSION`` in main to increment the version to the next
   minor one (i.e. X.Y.Z --> X.Y.(Z+1).dev0).
 
-* Also, update the ``version`` and ``release`` variables in doc/conf.py.
-
 * Create new headers for adding new features in ``RELEASE_NOTES.rst``
   add this place-holder::
 

VERSION

@@ -1 +1 @@
-1.11.0
+1.11.1.dev0