[logback-user] Versioning policy?

list+ch.qos.logback at io7m.com list+ch.qos.logback at io7m.com
Wed Feb 22 13:00:15 CET 2017


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?


[0] http://semver.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 854 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20170222/af58aeae/attachment.sig>

More information about the logback-user mailing list