in Zope 2.13, the CMF permission declarations have been moved to CMFCore. this means that on Zope 2.13 CMFCore 2.2.2 is a minimum dependency, but I'm not sure how to declare that

- complete changelog from 2.1 branch
- RST fixes

- updated some imports
- removed obsolete BBB code

  formatted string (as before), but also a qualified TAL
  expression, meaning it has a prefix like "string:", "python:".
  (https://bugs.launchpad.net/zope-cmf/+bug/378292)

  make sure older export files remain supported.

  bypass added.
  (https://bugs.launchpad.net/zope-cmf/+bug/308947)

o Don't import from Globals;  instead, use real locations.

o Make other imports use the actual source module, rather than an
  intermediate (e.g., prefer importing 'ClassSecurityInfo' from
  'AccessControl.SecurityInfo' rather than from 'AccessControl').

o Avoid relative imports, which will break in later versions of Python.

 - Strip final newline here when importing, otherwise it would not match against a translation msgid (see: http://dev.plone.org/plone/ticket/8525)

  (and long dead) base_cms product.

  and transition actions and their GenericSetup profiles.

- merge all 2.1.x changes from the monolithic CHANGES file at
  http://svn.zope.org/CMF/branches/2.1/CHANGES.txt?rev=87755&view=auto

- change author email to the canonical list address
- change homepage to package's PyPI page
- change long_description so it contains useful information
- flesh out installation requirements

Fixed a deprecation warning for Products.PageTemplates.TALES by a conditional import, so it still works on Zope 2.12.

- added CHANGES.txt file with trunk only changes