{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/io.js/issues/1484","labels_url":"https://api.github.com/repos/nodejs/io.js/issues/1484/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/io.js/issues/1484/comments","events_url":"https://api.github.com/repos/nodejs/io.js/issues/1484/events","html_url":"https://github.com/nodejs/io.js/issues/1484","id":69721068,"number":1484,"title":"Changelogs are noisy","user":{"login":"domenic","id":617481,"avatar_url":"https://avatars.githubusercontent.com/u/617481?v=3","gravatar_id":"","url":"https://api.github.com/users/domenic","html_url":"https://github.com/domenic","followers_url":"https://api.github.com/users/domenic/followers","following_url":"https://api.github.com/users/domenic/following{/other_user}","gists_url":"https://api.github.com/users/domenic/gists{/gist_id}","starred_url":"https://api.github.com/users/domenic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/domenic/subscriptions","organizations_url":"https://api.github.com/users/domenic/orgs","repos_url":"https://api.github.com/users/domenic/repos","events_url":"https://api.github.com/users/domenic/events{/privacy}","received_events_url":"https://api.github.com/users/domenic/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nodejs/io.js/labels/doc","name":"doc","color":"006b75"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-04-21T01:56:17Z","updated_at":"2015-07-21T02:40:33Z","closed_at":"2015-07-21T02:37:29Z","body":"I have a few complaints about the changelogs and was wondering if anyone shared them. In order of decreasing importance:\r\n\r\n- npm takes up half or more of the headlining \"notable changes\" space. I think it should get a budget of one sentence, and the rest can be links to the one or more npm changelog entries.\r\n- known issues is incomplete and repetitive. Pretty much all of [the 19 issues tagged as bug](https://github.com/iojs/io.js/labels/bug) count as \"known issues\". Probably others do too. And this section just stays the same release after release. Can we replace it with a link to the bug tag (or to a new known issues tag, if there's some distinction I'm missing between them)? If we need a snapshot of issues at a given point in time, can we collapse it into a single list like \"Known issues: #x, #y, #z\" instead of summarizing them over and over?\r\n- The commits list seems a bit redundant. Could we just link to the GitHub compare tags view? That way people can more easily expand to see the whole commit message.\r\n\r\nI say all this with love, as the readable changelogs are one of the best parts of io.js :). I just want to make them a bit more usable."},"comment":{"url":"https://api.github.com/repos/nodejs/io.js/issues/comments/123132650","html_url":"https://github.com/nodejs/io.js/issues/1484#issuecomment-123132650","issue_url":"https://api.github.com/repos/nodejs/io.js/issues/1484","id":123132650,"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-07-21T02:40:33Z","updated_at":"2015-07-21T02:40:33Z","body":"Closing since it's kinda been done and there hasn't actually been much complaint about this.\r\n\r\nWe generally just link to npm release notes now unless there's something exciting.\r\n\r\nThe known issues bit is kinda silly, it's very repetitive as we can't really fix the existing issues fast and there are in reality many more minor issues. I don't feel strongly about it either way."}}