Fix builds: remove node v0.10 from travis matrix

[styfle]

Description

Fixes our failing builds.

Node v0.10 went End-of-Life two years ago which is why jasmine (our test framework) won't work anymore (looks like they dropped support awhile ago and just introduced breaking changes recently.

Related: jasmine/jasmine-npm#144

Contributor

• no new tests required for this PR.

Committer

In most cases, this should be a different person than the contributor.

• Draft GitHub release notes have been updated.
• CI is green (no forced merge required).
• Merge PR

[UziTech]

Does this constitute a breaking change?

[styfle]

@UziTech That's a great question 🤔

I think we could say this PR itself is not breaking because it doesn't actually break compatibility with older versions of node, its just a change to CI.

However, our next release that contains breaking changes (0.6.0) should mention that node v0.10 is no longer supported.

It's a loop-hole but it will get CI green again and get the patch release out (0.5.2)

[davisjam]

1. By itself dropping node v0.10 from CI is not a breaking change.
2. But yes it's a bit of a loophole, and could lead to breaking changes in the future.

Good candidate for release notes.

[styfle]

@davisjam I will definitely add to release notes once you approve 😄

[styfle]

I couldn't find if we officially support any browser/versions though. I know we don't run automated tests in any browsers. So my best way to communicate v0.10 as a browser is IE. Thoughts on this one?