possibly in the same document we should describe more about what versions of our software we will support. By its nature this would be intertwined with #12, but there's probably a separable "how should I version my software" from the details of "what workflow supports that versioning scheme".
In https://innerspace.stsci.edu/display/DATB/Python+Version+Support+Plan+for+DATB I wrote up a document about practices for supporting versions of Python and external dependencies in DATB. We should have something like that here (happy to just translate my words into this repo if that makes sense). A more general policy exists (but perhaps is not ratified?) for ST here: https://innerspace.stsci.edu/display/isec/Software+Language+Supported+Versions
possibly in the same document we should describe more about what versions of our software we will support. By its nature this would be intertwined with #12, but there's probably a separable "how should I version my software" from the details of "what workflow supports that versioning scheme".