diff --git a/RELEASE.md b/RELEASE.md
index d62afe1a6..1e49b36c9 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -22,7 +22,8 @@ Release cadence of first pre-releases being cut is 6 weeks.
 | v2.15          | 2019-12-18                                 | Bartek Plotka (GitHub: @bwplotka)           |
 | v2.16          | 2020-01-29                                 | Callum Styan (GitHub: @cstyan)              |
 | v2.17          | 2020-03-11                                 | Julien Pivotto (GitHub: @roidelapluie)      |
-| v2.18          | 2020-04-22                                 | **searching for volunteer**                 |
+| v2.18          | 2020-04-22                                 | Bartek Plotka (GitHub: @bwplotka)           |
+| v2.19          | 2020-06-03                                 | **searching for volunteer**                 |
 
 If you are interested in volunteering please create a pull request against the [prometheus/prometheus](https://github.com/prometheus/prometheus) repository and propose yourself for the release series of your choice.
 
@@ -122,4 +123,4 @@ If the release has happened in the latest release branch, merge the changes into
 
 To update the docs, a PR needs to be created to `prometheus/docs`. See [this PR](https://github.com/prometheus/docs/pull/952/files) for inspiration (note: only actually merge this for final releases, not for pre-releases like a release candidate).
 
-Once the binaries have been uploaded, announce the release on `prometheus-announce@googlegroups.com`. (Please do not use `prometheus-users@googlegroups.com` for announcements anymore.) Check out previous announcement mails for inspiration.
\ No newline at end of file
+Once the binaries have been uploaded, announce the release on `prometheus-announce@googlegroups.com`. (Please do not use `prometheus-users@googlegroups.com` for announcements anymore.) Check out previous announcement mails for inspiration.