Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency mess #449

Closed
vojtajina opened this issue Apr 1, 2013 · 2 comments
Closed

Dependency mess #449

vojtajina opened this issue Apr 1, 2013 · 2 comments
Labels

Comments

@vojtajina
Copy link
Contributor

There are three dimensions in this matrix:

  • karma version
  • node version
  • each dependency version

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).

@dignifiedquire
Copy link
Member

👍 Sounds good

vojtajina added a commit that referenced this issue Apr 1, 2013
@vojtajina
Copy link
Contributor Author

Closing, I think it's ok now. (once 0.9 gets into stable, adding another version dimension - plugins, it's gonna be fun).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants