We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stable
Issue summary We are currently using the moving tag latest, which may be confusing. See an interesting article dedicated to this problem here.
latest
It'd be beneficial to change the behaviour a bit:
latest shall denote the latest stable release
edge shall denote the latest development build (latest main build)
edge
main
introduce edge tag to the Docker workflows
update the documentation
update the forest-iac infra so that it uses the edge tag for tests
forest-iac
Other information and links
The text was updated successfully, but these errors were encountered:
How about using latest for the latest stable release and dev for rolling builds?
dev
Sorry, something went wrong.
I'd go with edge and latest as described in https://devops.pingidentity.com/docker-images/releaseTags/#edge https://devops.pingidentity.com/docker-images/releaseTags/#latest
Also this approach seems to be supported by docker meta action. https://github.com/docker/metadata-action#typeedge
Sounds good?
LesnyRumcajs
Successfully merging a pull request may close this issue.
Issue summary
We are currently using the moving tag
latest
, which may be confusing. See an interesting article dedicated to this problem here.It'd be beneficial to change the behaviour a bit:
latest
shall denote the latest stable releaseedge
shall denote the latest development build (latestmain
build)introduce
edge
tag to the Docker workflowsupdate the documentation
update the
forest-iac
infra so that it uses theedge
tag for testsOther information and links
The text was updated successfully, but these errors were encountered: