message: notes-to-maintainers: add section "Release flow"
diff: ## Before a Merge
  - Make sure Travis Builds a passing
  -- Run the tests locally (`npm run buildtests & npm run test`)
  +- Run the tests locally (`npm run buildtests & npm run test`) (if not just documentation is changed)
  - Review the Pull-Request if something should be changed
  ## How to Merge
  @@ -22,6 +22,14 @@ when a new major version comes out, the old version is moved into `old/` for leg
  when 6.0.0 comes out, the old version (5.9.x) will be moved into (`old/5.x`) and `r6/master` merged into master
  +## Release flow
  +
  +The current schedule for releases is depending on what accumulates
  +aside from that, the flow looks like this:
  +- Patch Versions are released immediately
  +- Minor Versions are released with at least one pre-release
  +- Major Versions are released with at least one pre-release
  +
  ## Versioning
  [look at README#Versioning](../README.md#versioning)
  