diff --git a/CMakeLists.txt b/CMakeLists.txt
index a6ecc4f..66c6253 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -4,7 +4,7 @@
 cmake_minimum_required(VERSION 3.3)
 # - Call project() to setup system
 # From CMake 3, we can set the project version easily in one go
-project(prmon VERSION 1.0.1)
+project(prmon VERSION 1.1.1)
 
 #--- Define basic build settings -----------------------------------------------
 # - Use GNU-style hierarchy for installing build products
diff --git a/NOTICE b/NOTICE
index efc8de7..6c43d24 100644
--- a/NOTICE
+++ b/NOTICE
@@ -1,4 +1,4 @@
-Copyright 2018 CERN
+Copyright 2018-2019 CERN
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
diff --git a/doc/RELEASE_PROCEDURE.md b/doc/RELEASE_PROCEDURE.md
new file mode 100644
index 0000000..280ce14
--- /dev/null
+++ b/doc/RELEASE_PROCEDURE.md
@@ -0,0 +1,26 @@
+# prmon Release Procedure
+
+## Git and GitHub
+
+1. On the master branch make the last feature commits and ensure that all
+   tests pass.
+2. Update the release number in `CMakeLists.txt` and commit.
+3. Update the `stable` branch to this commit in `master`.
+4. Make a tag, following a semantic versioning scheme `vA.B.C`.
+  - Use an *annotated* tag, add brief release notes in the annotation.
+5. Push changes to GitHub.
+6. Prepare a binary tarball of the static build to add to the release:
+  - `cmake -DBUILD_STATIC=ON <PATH_TO_SOURCES>`
+  - `make package`
+  - Use the `tar.gz` archive.
+6. In GitHub go to releases, *Draft a new release*.
+7. Select the new tag.
+8. Add release notes as needed.
+9. Add the binary tarball to the release.
+
+## Zenodo
+
+1. Zenodo should pull the new release and assign it a DOI.
+  - The DOI does take a short time to activate.
+2. Grab the DOI link and update the `README.md` file on the
+`master` branch so that the correct DOI is shown on GitHub.