You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's support node 0.8, 0.10 (in general two latest "minor" stable versions). I believe it's ok if we only test with the latest patch version of each, as updating a patch version should be easy enough, so we will assume everybody is on the latest patch version (eg. now as of 04/01/2013 it's 0.8.22 and 0.10.2). Both these versions are tested on Travis.
Currently we have all the dependencies to fixed versions. Let's free this up to "minor" versions. (eg. ~0.2) As long as authors follow semver principle of no breaking change/feature in patch version, we should be fine.
If some dependency does not provide a version compatible with both node versions that particular version of karma support, let's allow two "minor" versions. (eg. currently log4js).
The text was updated successfully, but these errors were encountered:
There are three dimensions in this matrix:
Let's support node 0.8, 0.10 (in general two latest "minor" stable versions). I believe it's ok if we only test with the latest patch version of each, as updating a patch version should be easy enough, so we will assume everybody is on the latest patch version (eg. now as of 04/01/2013 it's
0.8.22
and0.10.2
). Both these versions are tested on Travis.Currently we have all the dependencies to fixed versions. Let's free this up to "minor" versions. (eg.
~0.2
) As long as authors follow semver principle of no breaking change/feature in patch version, we should be fine.If some dependency does not provide a version compatible with both node versions that particular version of karma support, let's allow two "minor" versions. (eg. currently
log4js
).The text was updated successfully, but these errors were encountered: