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.

Sign up for GitHub

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

Jump to bottom

Drop node 0.6 support. #135

Closed
GoalSmashers opened this issue Aug 28, 2013 · 8 comments
Closed

Drop node 0.6 support. #135

GoalSmashers opened this issue Aug 28, 2013 · 8 comments
Assignees
@GoalSmashers
Milestone
1.1

Comments

@GoalSmashers
Copy link
Contributor

This should be a general rule to support last 2 versions of node (0.10 and 0.8 at this time).
@ghost ghost assigned GoalSmashers Aug 28, 2013
@XhmikosR
Copy link
Contributor

Personally, I still believe Travis should have the latest node version, even if it's not released as "stable" yet. This way you can make sure there are no issues before that version goes stable.

@GoalSmashers
Copy link
Contributor Author

If there is an option on Travis to warn (but not fail) on broken build under unstable node.js, then I'd go for it. Otherwise it's a waste of time.

@XhmikosR
Copy link
Contributor

I'm not aware of such an option, but I haven't looked closely.

@GoalSmashers
Copy link
Contributor Author

Yup, me neither...

@XhmikosR
Copy link
Contributor

http://about.travis-ci.org/docs/user/build-configuration/#Rows-That-are-Allowed-To-Fail

@GoalSmashers
Copy link
Contributor Author

Nice :)

@GoalSmashers
Copy link
Contributor Author

Here it goes: bc02ade
Thanks for investigating!

@XhmikosR
Copy link
Contributor

NP, glad I could help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GoalSmashers GoalSmashers

Labels
None yet
Projects
None yet
Milestone
1.1
Development

No branches or pull requests
2 participants
@XhmikosR @GoalSmashers