Removing stale code
Handling production mode flag via mustache

This is much cleaner than the previous HTML comments solution.
Pass
    PRODUCTION_MODE=1
as an environment variable to reference the minified production JS. Otherwise
the individual JS files will be included.
Merge branch 'master' into develop

Conflicts:
	client/index.html

This merge was needed once, to incorporate some master-specific changes
(production mode HTML comments) back into develop.
Adding release target to makefile

This automates the creation of a new tagged release.

Run
    make release VERSION=0.9.8
to create an annotated tag object "0.9.8" on the master branch. Afterwards, master
will be merged back in to develop, in order to make the new tag visible there, too.

This target will refuse to run if the git working directory contains uncommitted
changes. Together with the dependency on the "all" target, this will enforce
an up to date production version of the JS.
Updating production JS build
Removing explicit check for clean git directory

It does not work as advertised. Actually, the master checkout will
already fail by itself in case of uncommitted changes on known files.
Adding actual merge to make release target
Updating JS build