Getting ready for release 1.11.1

ANNOUNCE.rst

@@ -1,16 +1,13 @@
 ==============================
-Announcing python-blosc 1.11.0
+Announcing python-blosc 1.11.1
 ==============================
 
 What is new?
 ============
 
-This is a maintenance release with many improvements cummulated during
-the last year.  Besides coming with the latest C-Blosc sources (1.21.2),
-there are quite a lot of fixes, specially in the build process.  And we
-added support for Python 3.10 and 3.11, and deprecated Python 3.7.
+This is a maintenance release.  Besides coming with the latest C-Blosc
+sources (1.21.3), there are new arm64 wheels for MacOS.
 
-Now, we are generating wheels for Python 3.10 and 3.11 (finally!).
 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
@@ -25,6 +22,9 @@ More docs and examples are available in the documentation site:
 
 https://www.blosc.org/python-blosc/python-blosc.html
 
+**Important note**: There is a new Python-Blosc2 wrapper
+on top of the next generation C-Blosc2 library.  Check it out at:
+https://github.com/Blosc/python-blosc2
 
 What is it?
 ===========

RELEASE_NOTES.rst

@@ -11,7 +11,7 @@
 Changes from 1.11.0 to 1.11.1
 =============================
 
-#XXX version-specific blurb XXX#
+* Internal C-Blosc sources updated to 1.21.3.
 
 
 Changes from 1.10.6 to 1.11.0

RELEASING.rst

@@ -15,10 +15,7 @@ Preliminaries
 * Make sure that ``RELEASE_NOTES.rst``
   and ``ANNOUNCE.rst`` are up to date with the latest news in the release.
 
-* Check that ``VERSION`` and ``doc/conf.py`` files contains the correct number.
-
-* Check any copyright listings and update them if necessary. You can use
-  ``git grep -i copyright`` to figure out where they might be.
+* Check that ``VERSION`` file contains the correct number.
 
 * Commit the changes::
 

VERSION

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