Replies: 5 comments 9 replies
-
Just looking at what other projects do in regards to tagging on the Docker hub, there seems to be another tagname called Edit Keeping the current meaning of the |
Beta Was this translation helpful? Give feedback.
-
While we are talking tags, I see that the images tagged |
Beta Was this translation helpful? Give feedback.
-
Related issues: |
Beta Was this translation helpful? Give feedback.
-
Just want to comment to say I support this idea. |
Beta Was this translation helpful? Give feedback.
-
I have a related idea that would partly address this issue: #24987 |
Beta Was this translation helpful? Give feedback.
-
There are constant Github issues and Slack posts from new Superset admins who are trying to configure it for the first time and are struggling because the default Docker config is to run the
latest-dev
image. This is true even in the docker-compose-non-dev.yml file.Using the latest nightly build has several problems, e.g., unique and temporary bugs that are hard to troubleshoot and a waste of time, trouble downgrading back to 2.0.0 once a user realizes they want to run a stable release. For example, here's a case where someone has problems because they deployed with
latest
following "official docs."If the default Docker workflow instead used the latest stable release, that would be big step to reducing barriers to using Superset. Two ways I see to do that are:
2.0.0
. Quick fix but could fall out of date if not added to the release process.latest
point to the latest official release andlatest-dev
point to the latest dev version of that release. As in the other option, thelatest
tag would have to be updated as part of the release process.Either would be fine with me and maybe contributors have other/better ideas for accomplishing the goal of routing first-time users to a stable release.
In any case, this would be more in line with the Apache Foundation's Release Policy:
(this came out of a Slack discussion)
Beta Was this translation helpful? Give feedback.
All reactions