I would like to emphasize this paragraph on the release policy page:
That part isn't unclear to me. What took time to sink in was the rolling release nature of community edition, meaning that this time investment for maintaining a system professionally recurs every three months, or four times a year. For all practical purposes, the test-learn-deploy cycle is non-stop. That's obvious to me now, but it wasn't at first. I retained the idea of a stable community edition option somehow.