I think the answer mostly depends on the minimal node version that should be supported by modules. According to semver, minor versions may add functionality in a backwards-compatible manner. This means that the code which works on 4.0 will also work on 4.1, but the code which works on 4.1 may not work on 4.0 if it uses functionality that was added in 4.1.

So using 4 or 4.1 alone is not enough. 4 install the latest 4.x.x version, 4.1 installs the latest 4.1.x. Nothing guarantees that the code also runs on 4.0.x. Someone may accidentally use a feature in the code which was added in a minor version and it won't be caught by the test runner.

If the plan is to support all node versions starting from 4.0.0, then I think we should always run tests on the minimal minor version, which is 4.0. We can then add either 4 or 4.1 to make sure the code also works on the latest version. I see two options:

Run code on the minimal and the latest. Maintaining .travis.yml is easy this way.
```
node_js:
  - 0.10
  - 4.0
  - 4
```
Run code on each minor version starting from minimal. This ensures that the code works on all versions, but we would constantly need to update .travis.yml which is not an easy task given the number of modules the hapijs organization has.
```
node_js:
  - 0.10
  - 4.0
  - 4.1
```

I think the first version should be enough. It the code works on the minimal and the latest version, then it most likely will work on all versions between them.

However if there is no such minimal version requirement (the module should only work with the latest 4.x.x version), then using 4 in .travis.yml is enough.

Travis config for node 4 #54

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions