I realized we weren't testing these, so I added them.

We intentionally dropped v0.11 support because it's supposed to be compatible with v0.12. See #307.

Artur took out iojs support a month or so ago. Didn't iojs and node merge, so there's no reason to test against these versions? I could be mistaken, so please correct me if I'm wrong.

^ the commit I'm referring to is 6acfbe8

@nfischer: I know v0.11 is supposed to be the same as v0.12, but I feel like it's probably worth testing.

As for iojs, yes, node >4 are actually iojs releases. So the release line looks like this(-ish):

v0.9 --- v0.10 ---- v0.11 --- v0.12 ---- v0.13 --- v0.14 --- v4.0 --- v5.0 --- [Future]
               \                                           /
                 ------ v1.0 ------ v2.0 ------ v3.0 -----

If iojs is merged back into the project, shouldn't it be ok to drop support for it? Is iojs actually still supported, or was it dropped in favor of node 4?

From #307:

0.11 is an unstable version that is not supported or updated anymore. 0.12 is fully compatible with 0.11 and as it is in maintenance mode, no breaking changes will be committed there.

Since it just slows CI down, and I don't see a strong benefit, I'd vote against including these versions.

I'm not super strong on it, but I feel like we should test any version that we claim to support, just in case theres an incompatibilities.

In that case, I'd rather stick with supporting v0.12, v4, and v5 in that case. It's essentially the same as what we're testing on now (minus v0.10), and we don't have to worry about all the differences iojs might have going forward.

Hmm...

I think that we should support (and therefore test) any active, LTS, or maintenance version of node (less v0.10). That would mean v0.11, v0.12, all releases of iojs, and node 4/5.

I doubt it would slow down travis that much, but if we really wanted to make it run fast, we could enable travis fast finishing.

I suppose this is fine then