anchor.diff:    Fix sync of newsletter related tables based on wrong foreign key constraints
   - 09/86 - Public: Fix padding in public search page
   - 09/88 - Public: Fix typos
  -
  -
  -.Security
   
   
   [[v0.9.4]]
  
positive.code: 
  [[unreleased]]
  == [unreleased]
  
  .Added
  - 09/87: New short field ('Kurzerfassungs-Feld') conclusion.
  
negative.code: 
  The format is based on http://keepachangelog.com/en/1.0.0/[Keep a Changelog].
  
  SciPaMato is an application. Therefore, the versioning scheme is _not_ adhering
  to http://semver.org/spec/v2.0.0.html[Semantic Versioning], which is mostly
  targeting software components or libraries. Nevertheless, I'm sticking with
  three part version numbers (e.g. 1.0.0), increasing the second number for
  bigger changes and the third number for relatively small changes and bug fixes.
  The first part of the version number will most likely remain version 1 for a
  longer period of time and may only change with a major rewrite of parts or the
  entire applicatin.
  
  In the version prior to 1.0.0, the second digit indicated the the development
  iteration, the third was keeping track of the number of the release within that
  iteration. Given a version number 0.ITERATION.RELEASE, we were incrementing
  
  . ITERATION version matching the project iteration
  . RELEASE version with every release within the given iteration.
  
  TIP: E.g. release 0.5.6 was the 6th release in iteration number 5.
  
  NOTE: References to user stories are in the form Iteration/Story-Number.
  
  