{"action":"opened","issue":{"url":"https://api.github.com/repos/GoogleChrome/accessibility-developer-tools/issues/134","labels_url":"https://api.github.com/repos/GoogleChrome/accessibility-developer-tools/issues/134/labels{/name}","comments_url":"https://api.github.com/repos/GoogleChrome/accessibility-developer-tools/issues/134/comments","events_url":"https://api.github.com/repos/GoogleChrome/accessibility-developer-tools/issues/134/events","html_url":"https://github.com/GoogleChrome/accessibility-developer-tools/issues/134","id":53881086,"number":134,"title":"Suggestions for releases","user":{"login":"addyosmani","id":110953,"avatar_url":"https://avatars.githubusercontent.com/u/110953?v=3","gravatar_id":"","url":"https://api.github.com/users/addyosmani","html_url":"https://github.com/addyosmani","followers_url":"https://api.github.com/users/addyosmani/followers","following_url":"https://api.github.com/users/addyosmani/following{/other_user}","gists_url":"https://api.github.com/users/addyosmani/gists{/gist_id}","starred_url":"https://api.github.com/users/addyosmani/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/addyosmani/subscriptions","organizations_url":"https://api.github.com/users/addyosmani/orgs","repos_url":"https://api.github.com/users/addyosmani/repos","events_url":"https://api.github.com/users/addyosmani/events{/privacy}","received_events_url":"https://api.github.com/users/addyosmani/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-01-09T15:47:20Z","updated_at":"2015-01-09T15:47:20Z","closed_at":null,"body":"We recently published the tools to npm so developers could easily consume and build other tools on top of it rather than submoduling. The latest version in both the repo and on there is 2.6.0.\r\n\r\nIn the releases and tags section of the repo however, we last tagged a version back in early 2014 (0.0.5): https://github.com/GoogleChrome/accessibility-developer-tools/releases\r\n\r\nIn order to maintain version consistency and get into a regular release cadence, I would suggest that we:\r\n\r\n* Bump the next release (in package.json) to 2.6.1\r\n* Tag master with 2.6.1\r\n* Publish 2.6.1 to npm\r\n* Follow this process or use a tool like [npm-release](https://www.npmjs.com/package/npm-release) to automate the above steps as and when we want to cut new releases.\r\n\r\nA target release cycle of once every 2-3 weeks would ensure the latest fixes are always available to dependents.\r\n\r\nI would also suggest that (if possible), we try to do clean Release-page change logs every time a release is cut so it's clear to end developers what has changed.\r\n\r\nI would be happy to help with some of this, but tagging in @alice for her thoughts here :) \r\n\r\n"}}