Updated deps

[AdrieanKhisbe]

Update dependancies + add David dependency watcher badge

[geek]

We won't want to have david reporting on dependencies, it doesn't seem smart enough to determine if a dependency is the latest version for a particular node version. For example, code 2 only works on node >= 4, so for seneca its not the latest version we should be using, since we support node >= 0.10

You will want to drop the version updates to code and joi, and focus on only the latest version that works on node >= 0.10

[AdrieanKhisbe]

damn it, I thought about lab, but no code. ^^

Shall I get ride of dependency status then?

[geek]

Ya, I think thats best to get rid of. David needs some feature enhancements for this type of issue.

[AdrieanKhisbe]

okey dokey :)

just saw alanshaw/david#95, awesome ;)

[AdrieanKhisbe]

By the way, any idea for how long we will support 0.10?

Pouring some es6 along with the codestyle uniformemisation is something really tempting :D

[mcdonnelldean]

@AdrieanKhisbe The plan in is to do this stuff (ES6, depreciate 0.10) after v1. In the new year I'll talk to @geek and @rjrodger on ways to better communicate long term plans to maintainers and the like.

[geek]

@AdrieanKhisbe version 1.0.0 of seneca will be published in a couple of weeks most likely. The issue is that 0.10.0 is still in wide use :/ I would really like to see a 2.0.0 version of seneca with node 4+ support only, and 1.0.0 being our LTS version.

[mcdonnelldean]

@geek +2 :D

[AdrieanKhisbe]

Okey Dokey. :)
Having a V1 that is compatible with 0.10 is a very good thing

[AdrieanKhisbe]

(then code style uniformemisation should be done before :))

[AdrieanKhisbe]

(had forgot the joi joi -> now solved)