RELEASE.md: clarify release process

It's worth calling out explicitly that only the master branch is maintained.
kbsonlong · Jan 21, 2019 · 51e16be · 51e16be
1 parent a113647
commit 51e16be
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/RELEASE.md b/RELEASE.md
@@ -1,3 +1,5 @@
 # Release Process
 
-TODO: describe the release process for this project
+No tagged releases are planned at this point. The intention is to keep
+the master branch in a state such that it can be used for all
+supported branches in downstream repos which use these files.