Re: continuous release, you can also replace the term with continuous integration; not so much if you DO release regularly, but if you CAN. Ask questions like, do we have build monitoring on the release branch? Is it green most of the time? Is work integrated into it regularly (multiple times a day)? If we discover a bug, can we just push a fix to master and deploy or do we need to do a hotfix on an older tag? What are the steps to create a new release?

While yes, continuous deployment may not be desirable in a lot of cases, continuous integration is a practice that (IMO) most software should strive for.