Hi, I don't think we use semantic versioning. Semantic versioning allows “unlimited” changes when the MAJOR version is changed. In both SLF4J and logback projects the major version has been stuck at 1. The rule of thumb is as long as the slf4j-api and the binding versions are the same, you should be fine for any version of slf4j-api. For recent versions of logback, the slf4j-api version should be at least 1.7.16. As for logback, for the vast majority of users changes should be transparent unless you are writing your own logback extensions in which case some minor adjustments might be necessary from time to time. To answer your question directly, the version range [1.7.16, 1.8.0) for slf4j-api should be safe. -- Ceki On 2/22/2017 13:00, list+ch.qos.logback@io7m.com wrote:
Hello.
I use Logback and SLF4J in a rather large number of projects. I like to keep dependencies up-to-date, and this means that I end up incrementing a large set of version numbers fairly frequently. It would reduce my workload if I could specify a version range in my dependency declarations for both Logback and SLF4J. However, I can only do this safely if I know the versioning policy of both of those projects. It sort of looks like they use something like Semantic Versioning [0], but I don't see an explicit policy written down anywhere.
Can I use version ranges such as [1.7.0, 2.0.0) safely?
M