- the section on logback initialization references the FAQ entry (location of config 
  files on the class path). This fixes LBSITE-20.
- minor enhancements in architecture.html relating to the basic selection rule
- updates to news.html

- LoggerContext reset, registered turbo filters are first stopped before being 
  unregistered. This fixes LBCLASSIC-89.
    

  automatically print status data on the console in case of warnings
  as well as errors. Previously, status data was printed only in
  case of errors.

- In case multiple configuration files are found on the class
  path, ContextInitializer will now emit a warning. This fixes 
  LBCLASSIC-85.

Documentation enhancements. Closing LBCLASSIC-30

ContextInitializer now prints the url it uses for default configuration.
This was requested in LBCLASSIC-55.

- Fix LBCORE-74
  
  HTMLLayoutBase now takes into custom conversion words.
  
- Moved StringListAppender to c.q.l.classic.testUtil package

- cleaned up config files so that "level" is an XML attribute and not
  an XML element

- updated Gmail related examples

- LBCLASSIC-100

  Evaluators are now wired into an appender automatically (implicit
  rules) without the help of EvaluatorAction. EvaluatorAction is now
  only needed for global evaluator elements.

  It follows that name attribute is necessary only for global
  evaluators. Embedded evaluators no longer need a name.

  EvaluatorAction has been modified to accept evaluators of any type
  and not just JaninoEvaluators.

- add tests for verifying that parameter types which are concrete classes 
  can be instantiated by implicit actions
- ongoing work on evaluators

be loaded by a different class loader than the class loaded that loaded
c.q.l.core.Loader (part of logback-core).

  Thus, it is no longer necessary to specify the class name as an xml attribute for sub-components
  
- refactoring of sibling appender 

- logback-access tests are now all JUnit4

  instead of a generic K. This simplifies the code without real loss
  of generality. :-) 

- Finished renaming HoardingAppender as SiftingAppender (as well as associated classes)

No commit message

- BasicStatusMessages's internal buffer now has two parts, the head part and the tail part.

- Initial commit of HoardingAppender

HoardingAppender contains other appenders which it can build
dynamically depending on MDC values. The built appender is specified
as part of a configuration file. Here is an example.

<configuration debug="true">
  <appender name="HOARD"  class="ch.qos.logback.classic.hoard.HoardingAppender">
    <mdcKey>userid</mdcKey>
    <hoard>
      <!-- you can put any appender here -->
      <appender name="file-${userid}" class="ch.qos.logback.core.FileAppender">
        <File>${userid}.log</File>
        <Append>true</Append>
        <layout class="ch.qos.logback.classic.PatternLayout">
          <Pattern>%d [%thread] %level %logger{35} - %msg%n</Pattern>
        </layout>
      </appender>
    </hoard>
  </appender>
  <root level="DEBUG">
    <appender-ref ref="HOARD" />
  </root>
</configuration>

A new file appender will be built each according to the MDC value
associated with the key "userid" when a logging event occurs. The
above configuration file will ventilate logging into log files named
after the userid. 

- Added PropertyContainer interface
- Context interface now extends PropertyContainer
- InterpretationContext implements PropertyContainer
  It now has a field called propertiesMap which has precedence
  over values placed in the context
- InterpretationContext.getSubstitutionProperty was renamed as
  getProperty
- It is now possible to initialize a joran Interpreter with an initial
  (not empty) pattern

This is still very much ongoing work.
  

Fix LBCORE-78. 

AsynchronousCompressor shuts down the executor it created, thus avoiding a memory leak.

- cosmetic changes in Context

Removed 'synchronized' keyword from the incSize() and size() methods. 
Synchronization was causing a deadlock described in LBCLASSIC-81
These two methods are used internally by logback for testing purposes.

The getEffectiveLevel() method needs to be synchronized to protect
against concurrent modification when iterating over
childrenList.iterator().