{"action":"created","issue":{"url":"https://api.github.com/repos/WordPoints/dependencies/issues/3","repository_url":"https://api.github.com/repos/WordPoints/dependencies","labels_url":"https://api.github.com/repos/WordPoints/dependencies/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/WordPoints/dependencies/issues/3/comments","events_url":"https://api.github.com/repos/WordPoints/dependencies/issues/3/events","html_url":"https://github.com/WordPoints/dependencies/issues/3","id":68684420,"number":3,"title":"Specification for dependencies and versions","user":{"login":"JDGrimes","id":4005415,"avatar_url":"https://avatars.githubusercontent.com/u/4005415?v=3","gravatar_id":"","url":"https://api.github.com/users/JDGrimes","html_url":"https://github.com/JDGrimes","followers_url":"https://api.github.com/users/JDGrimes/followers","following_url":"https://api.github.com/users/JDGrimes/following{/other_user}","gists_url":"https://api.github.com/users/JDGrimes/gists{/gist_id}","starred_url":"https://api.github.com/users/JDGrimes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JDGrimes/subscriptions","organizations_url":"https://api.github.com/users/JDGrimes/orgs","repos_url":"https://api.github.com/users/JDGrimes/repos","events_url":"https://api.github.com/users/JDGrimes/events{/privacy}","received_events_url":"https://api.github.com/users/JDGrimes/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2015-04-15T13:33:57Z","updated_at":"2017-01-30T20:27:16Z","closed_at":null,"body":"From https://github.com/WordPoints/dependencies/issues/1#issuecomment-92874405:\n\n> Prioritizing here, the first thing we need to do is establish a standard for specifying dependencies so that modules can begin doing this. We can then begin working on the implementation, and modules will already be ready when we actually release.\n"},"comment":{"url":"https://api.github.com/repos/WordPoints/dependencies/issues/comments/276180291","html_url":"https://github.com/WordPoints/dependencies/issues/3#issuecomment-276180291","issue_url":"https://api.github.com/repos/WordPoints/dependencies/issues/3","id":276180291,"user":{"login":"JDGrimes","id":4005415,"avatar_url":"https://avatars.githubusercontent.com/u/4005415?v=3","gravatar_id":"","url":"https://api.github.com/users/JDGrimes","html_url":"https://github.com/JDGrimes","followers_url":"https://api.github.com/users/JDGrimes/followers","following_url":"https://api.github.com/users/JDGrimes/following{/other_user}","gists_url":"https://api.github.com/users/JDGrimes/gists{/gist_id}","starred_url":"https://api.github.com/users/JDGrimes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JDGrimes/subscriptions","organizations_url":"https://api.github.com/users/JDGrimes/orgs","repos_url":"https://api.github.com/users/JDGrimes/repos","events_url":"https://api.github.com/users/JDGrimes/events{/privacy}","received_events_url":"https://api.github.com/users/JDGrimes/received_events","type":"User","site_admin":false},"created_at":"2017-01-30T20:27:16Z","updated_at":"2017-01-30T20:27:16Z","body":"> We are also going to need to specify what version of a dependency a dependent has been tested with.\r\n\r\nThis is partly something more for the update API though. The question is exactly how we will handle These specifications. If we just make it a matter of the minimum version being specified (for the most part) as the requirement, we need some way of knowing what the maximum is as well.\r\n\r\nFor example, say the version is `1.0`. That means a minimum of `1.0`. Say there is an update to `1.0.1`. That's probably OK, though we've indicated above that at times it might not be. So we might, generally, assume compatibility there, though it would be nice if we could be sure about it (by specifying that the version had been tested with the module—which would need to be done through the \"update\" API, since the version didn't actually exist when the module was released.)\r\n\r\nThis is even more important when it comes to the release of `1.1`. Making assumptions about that is riskier. In semantic versioning it is OK, but it isn't always so, since many plugins don't follow semantic versioning. So again, we'd need to be able to determine if the module had been tested with the new version. If we couldn't, we'd need to warn the user.\r\n\r\nAnd for 2.0, we'd really need to warn the user. Though again, barring semantic versioning, this may or may not be much different from 1.1 in terms of compatibility.\r\n\r\nWhat this really brings home is the importance of communicating with the module channel so that we can get information about what it has been tested with. Also that in regard to updates, of course."}}
{"actor":{"display_login":"JDGrimes"}}