Auto merge of #5252 - feministy:release-docs, r=segiddins
Auto merge of #5252 - feministy:release-docs, r=segiddins

documenting release process

refs #4135

I took the comments from @segiddins, @lynnco, and @indirect and organized them with a little extra prose where I saw fit. It's mostly y'alls words, just reorganized 😊

There are a few questions I have, mostly about branching:

- When `1.12.pre.1` is released, is it merged to `1-12-stable`?
- If there are bugs in `1.12.pre.1` *and* the branch (`1-12-pre-1`) is merged to master, is the branch for `1.12.pre.2` a branch off of `1-12-stable`?
- Are there any places we can reference to follow on discussions about in progress features, roadmaps, planned work, etc? It might be a good place to reference some of that stuff
- How can people get in touch with the core team?
- Is there a template for blog posts?

A few things to note:

- In the notes on the issue, it looks like you flop between using `.` versus `-` as the delimiter in your branch names. I went with `-` since that appears to be what you're using in the repo itself
- I do the full Github links so when people pull it down locally, they have the reference to the full link locally instead of relying on Github's magic linking

dilumnavanjana/bundler,mvz/bundler,bundler/bundler,dilumnavanjana/bundler,mvz/bundler,bundler/bundler