Node version

[lamphamsy]

Should we remove tests for old node versions such as 0.10, 0.12?

I think we could, as we have no need to be backwards compatible for this library.

There are people using this library if I trust https://www.npmjs.com/package/eclib so we'll need a major version bump. That would be acceptable if we're bundling that with every other planned breaking change.

[lamphamsy]

I am not sure that that would be a breaking change. Node 0.10 and 0.12 are too old now.

[ironman-machine]

Oh right.. If it's beeing used, nothing tells us that they have a more
recent version than 0.10 or 0.12...

On Tue, Nov 22, 2016 at 11:39 AM, lamphamsy notifications@github.com
wrote:

I am not sure that that would be a breaking change. Node 0.10 and 0.12 are
too old now.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#42 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AObSMyyU9LCoVv-odK0utmel-WH4mNXRks5rAsZ4gaJpZM4K5PSh
.

David Pineau
Scality R&D Engineer

http://go.scality.com/acton/media/18585/gartner-magic-quadrant-object-storage?utm_campaign=MQ&utm_medium=Email&utm_source=signatures

Yeah, npm stats aren't explicitly stating which node versions are being used. (And not supporting old versions anymore is a breaking change, there's no way around that fact)

To be clear, I am in favor of updating the library to recent standards, but this should not be done too hastily.