More version info updates

CMakeLists.txt

@@ -10,7 +10,7 @@ cmake_minimum_required(VERSION 3.12.0 FATAL_ERROR)
 project(
     bayeswave
     LANGUAGES C
-    VERSION 1.0.3
+    VERSION 1.0.4
     DESCRIPTION "LIGO/VIRGO burst analysis algorithm"
     HOMEPAGE_URL "https://git.ligo.org/lscsoft/bayeswave"
 )

doc/releasing.md

 # Preparing A Release
 Please familiarise yourself with this entire procedure before starting.
 
- 1. [Update Documentation](#update-documentation)
+ 1. [Update Hardcoded Version Info](#update-hardcoded-version-info)
  1. [Create a tag](#create-a-tag)
  1. [Build A Release Tarball](#build-a-release-tarball)
  1. [upload Source Tarball](#upload-source-tarball)
  1. [Open SCCB Request](#open-sccb-request)
  1. [Deployment](#deployment)
 
-## Update Documentation
-Along with any changes describing new functionality, the documentation should
-be updated to show the version number (see next step).  This should be done
-first, so that the documentation matches the release.  Specifically, edit `conf.py`
-[here](https://git.ligo.org/lscsoft/bayeswave/blob/master/doc/conf.py#L25).
+## Update Hardcoded Version Info
+There are a couple of places with (currently) hardcoded version numbers.
+Update these with the version you're about to release.  
+Specifically, edit :
+ * `conf.py` [here](https://git.ligo.org/lscsoft/bayeswave/blob/master/doc/conf.py#L25).
+ * `CMakeLists.txt` [here](https://git.ligo.org/lscsoft/bayeswave/blob/master/CMakeLists.txt#L13)
 
 Future releases may automate this step.