Getting ready for release 0.2.2

ANNOUNCE.md

@@ -1,11 +1,10 @@
-# Announcing cat4py 0.2.1
+# Announcing cat4py 0.2.2
 
 
 ## What is new?
 
-Docstrings has been added! In addition, the documentation can be found at:
-https://cat4py.readthedocs.io. Also, the use of an itemsize different than
-a 2 power is allowed now.
+This release just add a `MANIFEST.in` for including all C-Blosc2 and Caterva
+sources in package.
 
 For more info, you can have a look at the release notes in:
 

MANINFEST.in

@@ -0,0 +1,16 @@
+include MANIFEST.in
+include LICENSE
+include *.txt *.rst *.md
+exclude RELEASING.rst
+include setup.py
+
+recursive-include cat4py *.py *.pyx *.pxd *.c *.h
+recursive-include tests *.py
+recursive-include c-blosc2 *.c *.h
+recursive-include Caterva *.c *.h
+recursive-include bench *.py *.txt
+recursive-include doc *.rst *.txt *.py *.pdf *.html *.css *.png
+recursive-exclude doc/_build *
+recursive-include LICENSES *
+recursive-include c-blosc2/LICENSE.txt *
+recursive-include Caterva/LICENSE *

RELEASE_NOTES.md

@@ -5,6 +5,11 @@
 :Date: 2019-09-17
 
 
+## Changes from 0.2.1 to 0.2.2
+
+* Added a `MANIFEST.in` for including all C-Blosc2 and Caterva sources in package.
+
+
 ## Changes from 0.1.1 to 0.2.1
 
 * Docstrings has been added. In addition, the documentation can be found at:

RELEASING.md

@@ -7,7 +7,7 @@
 
 ## Preliminaries
 
-* Make sure that te current master branch is passing the tests on Microsoft Azure.
+* Make sure that the current master branch is passing the tests on Microsoft Azure.
 
 * Make sure that `RELEASE_NOTES.md` and `ANNOUNCE.md` are up to date with the latest news
 in the release.
@@ -25,19 +25,19 @@ in the release.
 
 ## Tagging
 
-* Create a signed tag ``X.Y.Z`` from ``master``.  Use the next message::
+* Create a signed tag ``X.Y.Z`` from ``master``.  Use the next message:
 
     $ git tag -a vX.Y.Z -m "Tagging version X.Y.Z"
 
-* Push the tag to the github repo::
+* Push the tag to the github repo:
 
     $ git push
     $ git push --tags
 
 
 ## Packaging
 
-* Make the tarball with the command::
+* Make the tarball with the command:
 
   $ python setup.py sdist
 
@@ -46,7 +46,7 @@ Do a quick check that the tarball is sane.
 
 ## Uploading
 
-* Register and upload it also in the PyPi repository::
+* Register and upload it also in the PyPi repository:
 
     $ python setup.py sdist upload
 
@@ -62,11 +62,11 @@ Do a quick check that the tarball is sane.
 ## Post-release actions
 
 * Create new headers for adding new features in ``RELEASE_NOTES.md``
-  add this place-holder::
+  add this place-holder:
 
   XXX version-specific blurb XXX
 
-* Commit your changes with::
+* Commit your changes with:
 
   $ git commit -a -m"Post X.Y.Z release actions done"
   $ git push