{"action":"created","issue":{"url":"https://api.github.com/repos/iojs/io.js/issues/930","labels_url":"https://api.github.com/repos/iojs/io.js/issues/930/labels{/name}","comments_url":"https://api.github.com/repos/iojs/io.js/issues/930/comments","events_url":"https://api.github.com/repos/iojs/io.js/issues/930/events","html_url":"https://github.com/iojs/io.js/issues/930","id":58654405,"number":930,"title":"Remove stability designations in core JS API","user":{"login":"mikeal","id":579,"avatar_url":"https://avatars.githubusercontent.com/u/579?v=3","gravatar_id":"","url":"https://api.github.com/users/mikeal","html_url":"https://github.com/mikeal","followers_url":"https://api.github.com/users/mikeal/followers","following_url":"https://api.github.com/users/mikeal/following{/other_user}","gists_url":"https://api.github.com/users/mikeal/gists{/gist_id}","starred_url":"https://api.github.com/users/mikeal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikeal/subscriptions","organizations_url":"https://api.github.com/users/mikeal/orgs","repos_url":"https://api.github.com/users/mikeal/repos","events_url":"https://api.github.com/users/mikeal/events{/privacy}","received_events_url":"https://api.github.com/users/mikeal/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-02-23T21:47:40Z","updated_at":"2015-02-23T22:08:10Z","closed_at":null,"body":"For several years we've been marking the core API with a sliding scale of \"stability.\"\r\n\r\nIt seemed like a good idea at the time but is at best, a poorly messaged note about how much work is happening on an API, and at worst an outright lie.\r\n\r\nEven if a module has the lowest level of stability attached we may, and actually have been, guaranteeing backwards compatibility if enough of the ecosystem depends on it.\r\n\r\nStreams is laughably marked \"Unstable\" at the moment. While it is true that streams have been changing a huge amount of effort in each change has gone in to guaranteeing backwards compatibility. That kind of compatibility is not what anyone would expect from an API being messaged as \"Unstable.\""},"comment":{"url":"https://api.github.com/repos/iojs/io.js/issues/comments/75647626","html_url":"https://github.com/iojs/io.js/issues/930#issuecomment-75647626","issue_url":"https://api.github.com/repos/iojs/io.js/issues/930","id":75647626,"user":{"login":"Fishrock123","id":1093990,"avatar_url":"https://avatars.githubusercontent.com/u/1093990?v=3","gravatar_id":"","url":"https://api.github.com/users/Fishrock123","html_url":"https://github.com/Fishrock123","followers_url":"https://api.github.com/users/Fishrock123/followers","following_url":"https://api.github.com/users/Fishrock123/following{/other_user}","gists_url":"https://api.github.com/users/Fishrock123/gists{/gist_id}","starred_url":"https://api.github.com/users/Fishrock123/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Fishrock123/subscriptions","organizations_url":"https://api.github.com/users/Fishrock123/orgs","repos_url":"https://api.github.com/users/Fishrock123/repos","events_url":"https://api.github.com/users/Fishrock123/events{/privacy}","received_events_url":"https://api.github.com/users/Fishrock123/received_events","type":"User","site_admin":false},"created_at":"2015-02-23T22:08:10Z","updated_at":"2015-02-23T22:08:10Z","body":"> How are we going to handle things like domains though? Deprecation warnings?\r\n\r\nDomains is already marked as deprecated as of #141, but not yet in code.\r\n\r\n> That is all on a per-API basis. Not all API is equal, if we're confident nobody is actually using something we will act differently than an API we think even a few people might be dependent on.\r\n\r\nI think it would be worth just having a standard \"what happened to the stability index\" link for a little bit."}}