ENH: point to the status of master branch on travis
ENH: consistent operation of formatExceptionInfo + unittest for it
ENH: basic test for setup.py itself (when applicable, should greatly improve coverage ;) )
TST: cover few more lines in fail2banreader.py
TST: Some primarily smoke tests for tests utils
ENH: actually tune up TraceBack to determine "unittest" portions of the stack across all python  releases

before for 2.7 it would spit out "suite" and other components of unittest module
ENH: use the same python executable for setup.py test

This doesn't anyhow resolve gh-161 which was revealed consistently on Debian sytem
after adding this testSetupInstallRoot
ENH: strengthen detection of working pyinotify

Even though import might work -- pyinotify might be dysfunctional.
Check by creating/deleting a dummy WatchManager upon import
BF: Fix for filterpoll incorrectly checking for jailless state
Merge pull request #225 from yarikoptic/master

Additional check that pyinotify is functional on this platform to enable it
DOC: inline commends with ';' are in effect only if ';' follows as space
ENH: issue a warning if jail name is longer than 19 symbols (Close #222)
ENH: now we know that logging handlers closing was still buggy in 2.6.2
ENH: include explicit list of new files which should not be there upon "install --root"

that is to figure out what gets there on failing travis tests:

e.g. https://travis-ci.org/fail2ban/fail2ban/jobs/7112324
ENH: also print the failing traceback line in case of failure

Also to troubleshoot
https://travis-ci.org/fail2ban/fail2ban/jobs/7112324
BF: (travis) if tests ran under coverage -- there is a traceback parts to report (thus > would be present)
BF: (travis) relax the test for needed to be presented installed directories -- allow new

on travis scripts install into user's home by default
All the (version) updates for the release of 0.8.9
BF: add missing files to MANIFEST (I think we shoult not rely on sdist anyways -- 'git tag' tarballs are more thorough ;) )
Merge tag '0.8.9' into 0.9 (quite a bit of conflicts "resolved")

Release 0.8.9

* tag '0.8.9':
  BF: add missing files to MANIFEST (I think we shoult not rely on sdist anyways -- 'git tag' tarballs are more thorough ;) )
  All the (version) updates for the release of 0.8.9
  BF: (travis) relax the test for needed to be presented installed directories -- allow new
  BF: (travis) if tests ran under coverage -- there is a traceback parts to report (thus > would be present)
  ENH: also print the failing traceback line in case of failure
  ENH: include explicit list of new files which should not be there upon "install --root"
  ENH: now we know that logging handlers closing was still buggy in 2.6.2
  ENH: issue a warning if jail name is longer than 19 symbols (Close #222)
  DOC: inline commends with ';' are in effect only if ';' follows as space
  BF: Fix for filterpoll incorrectly checking for jailless state
  ENH: strengthen detection of working pyinotify
  ENH: use the same python executable for setup.py test
  ENH: actually tune up TraceBack to determine "unittest" portions of the stack across all python  releases
  TST: Some primarily smoke tests for tests utils
  TST: cover few more lines in fail2banreader.py
  ENH: basic test for setup.py itself (when applicable, should greatly improve coverage ;) )
  ENH: consistent operation of formatExceptionInfo + unittest for it
  ENH: point to the status of master branch on travis

Conflicts:
	ChangeLog
	MANIFEST
	README.md
	fail2ban/version.py -- all of the above obvious version changes

   below files primarily  needed just a bit of help in resolution
	config/jail.conf
	fail2ban/server/filterpoll.py
	fail2ban/server/server.py
	fail2ban/tests/servertestcase.py

   and following were more difficult -- git wasn't able to track renames/moves of the code
    fail2ban-testcases -- needed to introduce those changes to tests/utils.py
	testcases/clientreadertestcase.py -- manually applied patch from master
	testcases/utils.py -- manually applied patch from master