John Spackman

## The Tool Proposal There are two independent proposals which seem to have become merged - firstly, there is `semantic-release` (the tool) which is simply a mechanism to take the...

> compile.json or running compile.js be stashed There is some support for this already, it takes a hash of the environment and compares that and the compiler version; to pick...

sorry, i thought i'd done those ... fixed now though

I agree with @hkollmann that we don't need to mock, just implement the server - however, as @cboulanger points out there is coordination to be done between client and server...

it has my vote :)

The commit message format is [the Angular format](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines) ## Commit Message Format Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format...

The `scope` is optional, but we could use it to separate out rules for things like PRs - EG if the scope is `compiler` or `docs` then we choose different...

perhaps just to ignore the scope altogether, and just use titles in the PR like `[compiler]` - that might be more natural, given that we're already used to using things...

> @oetiker said: I wonder if we could put something in place to warn authors about this problem ...maybe have the compailer complain if it sees keypress eventhandlers being assigned...

I see the logic in removing `keypress` now, in that `keydown` provides greater range of functionality, but I'm not convinced that `keypress` is obsolete or that `keydown` is a "better"...