January 20th, 2017, Release of version 1.1.9
Logback's internal executor service had a thread pool size of 2 which could be used up rather quickly, e.g. configuration scanning in addition to an active ServerSocketAppender. When both threads where permanently in use, compression could not proceed. To alleviate this problem, the thread pool size has been increased to 8. See issue LOGBACK-1238 for more details.
Fixed issue with FileAppender instances embedded within SiftingAppender reporting filename collisions after reaching timeout and subsequently restarted. This problem was reported in LOGBACK-1167 by Michael Edgar.
Fixed SizeAndTimeBasedFNATP deprecation warning emitted even the replacement, i.e. SizeAndTimeBasedRollingPolicy, is in use. See LOGBACK-1236. This issue was reported by Claudius Nicolae.
Added proper implementation for LobackValve.getScheduledExecutorService() method. The missing implementation manifested itself in the form of an UnsupportedOperationException thrown by LogbackValve. This problem is further described in LOGBACK-1181 reported by Andreas von Roepenack.
December 9th, 2016, Release of version 1.1.8
Removed the two period safeguard, aka untouchable periods, for archive removal beyond the size specified by totalSizeCap in TimeBasedRollingPolicy. It turns out the safegaurd is not required and is unexpected as attested by LOGBACK-1166.
Fixed issue with Joran incorrectly reporting "Unexpected aggregationType AS_BASIC_PROPERTY_COLLECTION". This issue was raised in LOGBACK-1158 by Christian Hübner.
Gaffer (logback's groovy configurator) now supports the valueOf convention. This issue was raised in LOGBACK-1232 by Frans Orsel.
The org.slf4j.impl.StaticLoggerBinder class shipping in logback-classic no longer catches Throwable but Exception. This change was requested in LOGBACK-1159 by David J. M. Karlsen.
BeanDescriptionFactory no longer outputs a superflous warning message in case the class contains bridge methods. This fixes LOGBACK-1164 reported by Phil Clay.