Diecutter

----------------

- Nothing changed yet.

------------------

Bugfix release.

- Bug 112 - Fixed Sphinx configuration, fixed builds on readthedocs.org.

----------------

Added support for multiple template engines, reviewed documentation.

- Feature 77 - One `diecutter` server can support multiple template engines:

* The client can ask `diecutter` to use a specific engine with ``engine``
in query string.

* The list of supported engines in displayed in API index.

* Supported engines and their implementation can be configured server-side.

- Feature 104 - Get in touch via IRC: diecutter on freenode.

- Bug 103 - README is rendered as HTML on PyPI (was plain reStructuredText).

- Refactoring 107 - Functional tests moved to Sphinx documentation.

- Refactoring 108 - `diecutter` no longer requires `webtest` and `mock`. They
are only required to run tests or building documentation. Removed
``diecutter.tests`` from distributed package.

- Refactoring 110 - From demo, removed templates that are now maintained as
third-party projects: Django project, Python project and Sphinx
documentation.

- Features 81 and 87 - Reviewed documentation about alternatives and related
projects: added `Voodoo` and `cookiecutter` to alternatives ; highlighted
`piecutter` as the core Python API provider.

----------------

Moved some parts of diecutter to external projects: core in piecutter, demo in
template index and standalone template repositories.

- Moved generic bits of diecutter's core to third-party project 'piecutter'.

- Bug 100 - Files in tar.gz archives have a valid modification time (was
epoch).

- Feature 97 - Refactored diecutter's demo index, so that it references
templates from external repositories.

- Render archive filename using filename_engine.

- Added example configuration for cookiecutter and github.

- Improved contributor guide.

- Using tox to run tests. Development environment no longer uses zc.buildout.

----------------

Proof of concept implementation of remote template loader and Django template
engine.

- Features 27 and 28 - Experimental support of remote templates, where
templates are hosted in Github public repositories.
The github service is published at http://diecutter.io/github. It accepts
URLs like
http://diecutter.io/github/<owner>/<project>/<revision>/<path/to/template/resource>

- Features 57 and 29 - Public online SAAS at http://diecutter.io

- Feature 66 - Introduced support of Django template engine. You can choose
the (unique) template engine with ``diecutter.template_engine`` configuration
directive. Default value is ``piecutter.engines.jinja:Jinja2Engine``.

- Bug 60 - PyPI renders README as HTML (was plain text).

- Bug 65 - Contributor guide mentions dependency to virtualenv (was missing).

- Refactoring 68 - Code follows strict PEP8. Using flake8 in tests.

----------------

New feature (tar.gz archives) and marketing (talks).

- Feature 4 - Added support of "accept" header for POST requests on
directories: accepted types are ZIP (``application/zip``) and TAR.GZ
(``application/gzip``).

- Feature 53 - GZIP is now the default archive format when rendering
directories. Use "diecutter.default_archive_type = application/zip" in
configuration file if you need ZIP format as a default.

- Refactoring 55 - Dropped support of Python 2.6. Tests are run against Python
2.7 only.

- Refactoring 20 - Render functions return generator ; moved response
composition (file/archive) into views via writers.

- Feature 46 - Added content of talks in documentation: AFPY event and
EuroPython 2013.

- Feature 58 - Highlighted roadmap and vision in README.

See also `milestone 0.4 on bugtracker`_.