[logback-user] Versioning policy?

list+ch.qos.logback at io7m.com list+ch.qos.logback at io7m.com
Sat Feb 25 15:03:12 CET 2017

On 2017-02-23T19:10:15 +0100
Ceki Gülcü <ceki at qos.ch> wrote:

> 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.

Sounds good, thanks!

-------------- 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/20170225/d3896169/attachment.sig>

More information about the logback-user mailing list