* rivets formatters and binders are now called with the scope of the view
* can set Rivets tempalte delimiters using `options.rivetDelimiters`
    * should we namespace the rivets config?
    * why is it all `rivet` and not `rivets`, like the library?
* plugin methods are now called with and argument of options (and still the context of the view)
* the rivets plugin no longer `this.model.set('viewId', this.cid)` for the view
* `rivetFormatters` and `rivetBinders` no longer have to be stored on the view and are consumed from `options` in initialize
* `rivetConfig` is now applied if truthy
* the rivets configs now use plural but are backward compatible to singular on options
    * `options.rivetsBinders` - `options.rivetBinders` both work - singular also works for all below
    * `options.rivetsConfig`
    * `options.rivetsDelimiters`
    * `options.rivetsFormatters`
    * `options.rivetsPrefix`
 * the rivet view allows configuration of whether to run the rivets plugin using whether `options.rivetsConfig` (or `options.rivetConfig`) is truthy or falsey.
* choosing not to include a wrapper div is no longer supported, since it can lead to some confusing gotchas if there are more than one root level elements in your template.
* lifecycle events are now triggered on the view itself in addition to notifying through the promise returned from start
upgrading grunt-shell
* added a new life cycle event, `afterRenderingDone` that happens once the template is compile, but before the element is inserted into the DOM
* updating rivets plugin to use life cycle events
Merge branch 'rivet'