- Include ztk-sources.cfg and ztk-versions.cfg
- (without accidentally including .installed.cfg or .mr.developer.cfg)
- Exclude built Sphinx docs

- Move changelog to root project directory.  Leave a stub behind for Sphinx.

- Move 'doc' -> 'docs' and fix up.

- Use newer Sphinx locations for support files,  build targets.

This imports SVN revision 130401.

Note that Tres has superpowers now :)

'zope.publisher.publish.unwrapMethod' was not recognizing the faux-callable
nature of DTMLMethod.  Add a '__code__' attr to help it find us.

Neaten / normalize functest scaffolding.

Borked during merge of Products.PloneHotfix20131210 fixes.

Also fix one HTTP PyPI reference that I missed.

Because otherwise doc/INSTALL.rst lies to users when it tells them the
source tarball will have a buildout.cfg and everything.  Lying to users
is Bad.

(I don't know what to do about the .mo files that are in git.  Should
they be included in the sdist?)

PyPI will redirect to HTTPS anyway, besides, why allow the man-in-the-middle?

There is no bootstrap/ subdirectory in git.

Then again there's no bootstrap/ subdirectory nor bootstrap.py nor, in fact, buildout.cfg in https://pypi.python.org/packages/source/Z/Zope2/Zope2-2.13.22.zip, so I don't know what this document is talking about.  Broken MANIFEST.in?

The changelog is the canonical place for bug / release associations.

(was at svn.zope.org/repos/main/zope2docs/trunk/maintenance/index.rst)