Is your feature request related to a problem? Please describe.
After merging a PR into master, the DockerHub task kicks off to create a new image with the code currently in master and uploads it to DockerHub with a tag of smartsdk/quantumleap:latest. To us "latest" means latest build but others out there may take it to mean "latest & greatest", expecting a stable release. On the other hand, our stable releases get tagged with a major/minor/patch number as in e.g. smartsdk/quantumleap:0.7.5. This scheme may be confusing to some as it isn't immediately clear: (1) what is the latest stable release fit for production use and (2) whether the image tagged "latest" is stable or in which instances it should be used---e.g. RC testing, early adopters, etc.
Describe the solution you'd like
Come up with a more descriptive naming scheme that makes it easier to tell what an image is fit for.
Describe alternatives you've considered
N/A
Additional context
It happened in the past that people used the latest image on DockerHub expecting it to be stable.
github-actions[bot]
commented
3 years ago
Is your feature request related to a problem? Please describe. After merging a PR into master, the DockerHub task kicks off to create a new image with the code currently in master and uploads it to DockerHub with a tag of
smartsdk/quantumleap:latest. To us "latest" means latest build but others out there may take it to mean "latest & greatest", expecting a stable release. On the other hand, our stable releases get tagged with a major/minor/patch number as in e.g.smartsdk/quantumleap:0.7.5. This scheme may be confusing to some as it isn't immediately clear: (1) what is the latest stable release fit for production use and (2) whether the image tagged "latest" is stable or in which instances it should be used---e.g. RC testing, early adopters, etc.Describe the solution you'd like Come up with a more descriptive naming scheme that makes it easier to tell what an image is fit for.
Describe alternatives you've considered N/A
Additional context It happened in the past that people used the latest image on DockerHub expecting it to be stable.