Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated deps #285

Merged
merged 3 commits into from
Dec 30, 2015
Merged

Updated deps #285

merged 3 commits into from
Dec 30, 2015

Conversation

AdrieanKhisbe
Copy link
Contributor

Update dependancies + add David dependency watcher badge

@geek
Copy link
Member

geek commented Dec 28, 2015

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

@geek geek self-assigned this Dec 28, 2015
@AdrieanKhisbe
Copy link
Contributor Author

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

Shall I get ride of dependency status then?

@geek
Copy link
Member

geek commented Dec 28, 2015

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

@AdrieanKhisbe
Copy link
Contributor Author

okey dokey :)

just saw alanshaw/david#95, awesome ;)

@AdrieanKhisbe
Copy link
Contributor Author

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
Copy link
Contributor

@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
Copy link
Member

geek commented Dec 28, 2015

@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
Copy link
Contributor

@geek +2 :D

@AdrieanKhisbe
Copy link
Contributor Author

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

@AdrieanKhisbe
Copy link
Contributor Author

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

@AdrieanKhisbe
Copy link
Contributor Author

(had forgot the joi joi -> now solved)

@geek geek added this to the 0.9.4 milestone Dec 30, 2015
geek added a commit that referenced this pull request Dec 30, 2015
@geek geek merged commit 547860d into senecajs:master Dec 30, 2015
@AdrieanKhisbe AdrieanKhisbe deleted the updated-deps branch December 30, 2015 16:07
@AdrieanKhisbe AdrieanKhisbe restored the updated-deps branch January 15, 2016 10:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants