There's been a little discussion about this on Github (https://github.com/apache/superset/discussions/22244) and in the #operational-model-release-strategy channel on Slack.
I propose that the release process for an official Apache release include tagging the associated docker images with a new tag, "official." That's in line with what's on Docker Hub (https://hub.docker.com/r/apache/superset), which says '"Official" Releases coming soon.' Then the project's docker-compose-non-dev.yml file could point new users to the official image, rather than the latest (possibly-unstable) build. This would be in line with release guidance from the Apache Foundation and make it easier for new Superset admins to experience success with the product. The Foundation says, in bold, "*Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages."* Are there any concerns or alternatives that people would prefer? One thing I'm unsure about is how to handle cases like 1.5.3 being released after 2.0.1. Would it be undesirable for 1.5.3 to take over the "official" tag from 2.0.1 in that case? I'd think the highest numerical version should be the "official" release, not the latest chronologically. Which I'm not sure how to implement in the automated release process, but I hope would be possible. The upcoming release of 3.0.0 offers an opportunity to implement this, thus I'm raising it now.
