diff --git a/RELEASE_PROCESS.md b/RELEASE_PROCESS.md
index 5b274450..776eecba 100644
--- a/RELEASE_PROCESS.md
+++ b/RELEASE_PROCESS.md
@@ -26,9 +26,6 @@ A minor release is preceeded by a feature freeze and created from the 'master' b
 1. Follow steps outlined in [Common Steps](#common-steps)
 1. In 'master' branch, Edit `bigchaindb/version.py`, increment the minor version to the next planned release, e.g. `0.10.0.dev`. (Exception: If you just released `X.Y.Zrc1` then increment the minor version to `X.Y.Zrc2`.) This step is so people reading the latest docs will know that they're for the latest (master branch) version of BigchainDB Server, not the docs at the time of the most recent release (which are also available).
 1. Go to [Docker Hub](https://hub.docker.com/), sign in, go to bigchaindb/bigchaindb, go to Settings - Build Settings, and under the build with Docker Tag Name equal to `latest`, change the Name to the number of the new release, e.g. `0.9`
-1. In 'master' branch, create a new directory `bigchaindb/docs/specs/release-(release_version++)`. e.g. If you just released `1.2` you need to create the directory `bigchaindb/docs/specs/release-1.3`.
-1. In 'master' branch, under the newly created directory i.e. `bigchaindb/docs/specs/release-1.3.0`, create a release tracking
-document `bigchaindb/docs/specs/release-1.3.0/release-1.3.0.md`. Please consult the [example release tracking document](./docs/specs/examples/example-release-doc.md) for contents.
 
 Congratulations, you have released BigchainDB!
 
diff --git a/docs/specs/README.md b/docs/specs/README.md
index 453700ad..95b67488 100644
--- a/docs/specs/README.md
+++ b/docs/specs/README.md
@@ -39,7 +39,7 @@ Create a new issue on our [GitHub repository](https://github.com/bigchaindb/bigc
 Submit a design specification document (Pull Request) of your feature. The spec needs to be submitted at:
 
 ```text
-/path/to/repo/bigchaindb/docs/specs/release-<latest-release>/
+/path/to/repo/bigchaindb/docs/specs/
 ``` 
 
 The PR for the specification document should be
@@ -59,4 +59,3 @@ Once, you have submitted the design specification document:
 - Get it merged.
 
 Once, your specification document is merged, it will be tracked for an upcoming release.
-
diff --git a/docs/specs/examples/example-release-doc.md b/docs/specs/examples/example-release-doc.md
deleted file mode 100644
index c1810aca..00000000
--- a/docs/specs/examples/example-release-doc.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# Release example.release.version
-
-The example.release.version cycle begins on Monday, January 1, 2049.
-
-## Team
-
-| **Role**        | **Name**           | **github**  |
-| ------------- |:-------------:| -----:|
-| Developer      | Alice | [alicegithub](https://github.com/) |
-
-## Notes
-Some notes about the release cycle:
-
-- Events or known overheads during the cycle.
-- Guidelines about which features can be merged and marked completed with in the timeline.
-- Sprint planning dates and timings
-
-## Discussions/Meeting minutes
-
-- Links to discussions or meeting minutes.
-
-## Timeline
-Timeline of the release cycle. For reference:
-
-- Mon Jan 1: Start of release cycle.
-
-- Mon Jan 8: Scoping
-
-  - All features being tracked for release, should have issues on GitHub.
-
-- Mon Jan 22: Code Freeze.
-
-- Mon Jan 29: Doc completion.
-
-- Mon Feb 5: Tag release.
\ No newline at end of file
diff --git a/docs/specs/release-1.4.0/release-1.4.0.md b/docs/specs/release-1.4.0/release-1.4.0.md
deleted file mode 100644
index 41863740..00000000
--- a/docs/specs/release-1.4.0/release-1.4.0.md
+++ /dev/null
@@ -1,12 +0,0 @@
-# Release 1.4.0
-
-The 1.4.0 release cycle begins on Tuesday, November 21, 2017
-
-## Notes
-None
-
-## Timeline
-None
-
-## Details
-None