{"action":"created","issue":{"url":"https://api.github.com/repos/ev3dev/ev3dev-lang/issues/135","labels_url":"https://api.github.com/repos/ev3dev/ev3dev-lang/issues/135/labels{/name}","comments_url":"https://api.github.com/repos/ev3dev/ev3dev-lang/issues/135/comments","events_url":"https://api.github.com/repos/ev3dev/ev3dev-lang/issues/135/events","html_url":"https://github.com/ev3dev/ev3dev-lang/issues/135","id":122418846,"number":135,"title":"Tag a release of ev3dev-lang to correspond with kernel release","user":{"login":"WasabiFan","id":3310349,"avatar_url":"https://avatars.githubusercontent.com/u/3310349?v=3","gravatar_id":"","url":"https://api.github.com/users/WasabiFan","html_url":"https://github.com/WasabiFan","followers_url":"https://api.github.com/users/WasabiFan/followers","following_url":"https://api.github.com/users/WasabiFan/following{/other_user}","gists_url":"https://api.github.com/users/WasabiFan/gists{/gist_id}","starred_url":"https://api.github.com/users/WasabiFan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WasabiFan/subscriptions","organizations_url":"https://api.github.com/users/WasabiFan/orgs","repos_url":"https://api.github.com/users/WasabiFan/repos","events_url":"https://api.github.com/users/WasabiFan/events{/privacy}","received_events_url":"https://api.github.com/users/WasabiFan/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ev3dev/ev3dev-lang/labels/all%20languages","name":"all languages","color":"eb6420"},{"url":"https://api.github.com/repos/ev3dev/ev3dev-lang/labels/question","name":"question","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":16,"created_at":"2015-12-16T03:20:04Z","updated_at":"2015-12-22T02:05:54Z","closed_at":null,"body":"Now that we have gotten the libraries in this repo updated so that (aside from some last changes) they are all ready for the newest kernel release, I think we should get the readme and spec updated, set the submodules to be pointing at the proper commits, and then merge `develop` into `master` and tag a release.\r\n\r\nThe TODO list as I see it:\r\n- [ ] Update for breaking changes in new ev3dev release\r\n- [ ] Autogen the markdown spec and update it for LED changes and new sensors\r\n- [ ] Update the \"currently supported kernel\" in the markdown spec\r\n- [ ] Decide on fate of current lua binding\r\n  - I think that, unless @rhempel's new lua binding is ready for prime time, we should hold off on including it (more on that below)\r\n  - Either mark it as old/broken or remove it for release\r\n- Get each individual library updated (full testing runs + confirmation from authors)\r\n  - [ ] Python\r\n  - [ ] C++\r\n  - [ ] JS\r\n- [ ] Work through issues and close any that can be closed\r\n  - Make sure that we haven't forgotten about anything important\r\n\r\nAs for the new bindings (C# and Lua v2), I think we should hold off on those until after we have a release, and then add them in and tag a new release with those included after those have been tested.\r\n\r\nWe should also figure out the versioning scheme to use on the main ev3dev-lang repo. We had started versioning the spec at v0.9 and continued from there (0.9.1, 0.9.2). We did this because we did not have enough feature coverage at the time to feel reasonable calling it a \"v1\". At this point, I think that jumping to v1 might be a good idea, but I think this too needs more discussion.\r\n\r\nWhat am I missing? Thoughts, additions, corrections? @ddemidov @rhempel \r\n"},"comment":{"url":"https://api.github.com/repos/ev3dev/ev3dev-lang/issues/comments/166478875","html_url":"https://github.com/ev3dev/ev3dev-lang/issues/135#issuecomment-166478875","issue_url":"https://api.github.com/repos/ev3dev/ev3dev-lang/issues/135","id":166478875,"user":{"login":"rhempel","id":5571620,"avatar_url":"https://avatars.githubusercontent.com/u/5571620?v=3","gravatar_id":"","url":"https://api.github.com/users/rhempel","html_url":"https://github.com/rhempel","followers_url":"https://api.github.com/users/rhempel/followers","following_url":"https://api.github.com/users/rhempel/following{/other_user}","gists_url":"https://api.github.com/users/rhempel/gists{/gist_id}","starred_url":"https://api.github.com/users/rhempel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhempel/subscriptions","organizations_url":"https://api.github.com/users/rhempel/orgs","repos_url":"https://api.github.com/users/rhempel/repos","events_url":"https://api.github.com/users/rhempel/events{/privacy}","received_events_url":"https://api.github.com/users/rhempel/received_events","type":"User","site_admin":false},"created_at":"2015-12-22T02:05:54Z","updated_at":"2015-12-22T02:05:54Z","body":"Inverting the model has the distinct advantage of decoupling the language bindings from each other and allowing each author to manage their releases independently. Based on my inability to merge coherently this may be a good thing.\r\n\r\nI still think we want to require that a language binding is able to report the `spec.json` and `autogen` and `kernel` versions!"}}