Consider adjusting processes to ensure docs are current on RTD's stable

[markcmiller86]

Describe what needs to be documented.

RTD defines a stable view of the docs which is the most up to date release from GitHub. Its possible to hide RTD's stable docs but that winds up disabling warning features in hosted docs that warn users when they are looking at a version other than the most recent release.

However, after a year or more work making several releases from an RC branch, if all doc updates go to develop, they won't appear in RTD's stable for that entire time.

Should we adopt a new practice of doing doc updates both on RC and develop to avoid the long delays in documentation appearing on RTD's stable?

So far, we have one "user" that ran into this. @JustinPrivitera suggests we wait to decide this until we encounter another user using stable.