Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Quay tags: stable/latest/pre-release etc.
See original GitHub issuePlease see https://quay.io/repository/ansible/molecule?tab=tags.
Our latest tag current points to the latest build IIUC. See https://github.com/ansible/molecule/issues/1813#issuecomment-471504129.
I’m unfamiliar with conventions for the latest tag but should it be latest ‘stable’, and point to v2.19?
See https://github.com/ansible/molecule/issues/1813#issuecomment-471476378.
My intuition is:
- stable -> v2.19 (or latest stable release)
- vX.Y -> pre-release versions for pre-release hacking / feedback / early testing
- latest -> convenience for latest build (and potentially dangerous to target)
I’m easy and just want to agree on this so we can be clear what tag is what.
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi, sure, if you need to help with maintaining anything, contact me. I will like to contribute to this project 😃.
Docker tradition is to have
latestpoint to unstable things. Using “latest” is usually equivalent of not pinning dependencies of the environment which is a generally discouraged practice in software development and deployment world. Whatever we choose we should clearly state that it’s recommended to point to a numeric version whenever using the image for anything other than experimenting. But pointinglatesttostablewe’d kinda encourage people to use it which is not kind of messaging I’d like to see.