{"issue":{"milestone":null,"user":{"login":"laserlemon","id":34264,"url":"https://api.github.com/users/laserlemon","avatar_url":"https://secure.gravatar.com/avatar/0887991a8846577a6aa85433d6ab3ea2?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"0887991a8846577a6aa85433d6ab3ea2"},"title":"Version release notes","created_at":"2011-11-07T21:14:33Z","labels":[{"name":"feature","url":"https://api.github.com/repos/rubygems/rubygems.org/labels/feature","color":"349429"}],"updated_at":"2011-12-19T14:13:26Z","state":"open","id":2167500,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/rubygems/rubygems.org/issues/365","closed_at":null,"body":"Has there been any consideration for release notes attached to gem versions? @bryckbost and I have been talking it over recently and think there's a lot of value in an optional description attached to a new version release. Semantic versioning can only relay so much regarding the impact of a new version (and not everybody uses semantic versioning). A summary of the changes between versions would prove very useful to the gem's users.\r\n\r\nAs a bonus, a release note could be required when yanking a gem version. Providing the reason behind yanking a version would give a lot of insight into what action should be taken by those gems and projects that depend on that yanked version. Bundler could even (eventually) provide a meaningful message when trying to bundle a yanked gem version.\r\n\r\nThoughts? I am very willing to help out with implementation.","number":365,"url":"https://api.github.com/repos/rubygems/rubygems.org/issues/365","comments":9,"assignee":null},"comment":{"user":{"login":"ognevsky","id":175508,"url":"https://api.github.com/users/ognevsky","avatar_url":"https://secure.gravatar.com/avatar/0730b35a43de1bcbd5345cc9b8d38acd?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"0730b35a43de1bcbd5345cc9b8d38acd"},"created_at":"2011-12-19T14:13:26Z","updated_at":"2011-12-19T14:13:26Z","id":3203506,"body":"@laserlemon it's no problem to include it to Gemnasium, but Gemnasium is not opensource (as i can see), so i would write my own changelog-application (but you can do with MIT lib what you want). If Gemnasium was opensource (or i was team member), we could join our forces (not to develop 2 similar apps).\r\n\r\nAnd some good news, i think i would publish first version of my gem tonight.","url":"https://api.github.com/repos/rubygems/rubygems.org/issues/comments/3203506"},"action":"created"}