{"action":"opened","issue":{"url":"https://api.github.com/repos/iojs/io.js/issues/252","labels_url":"https://api.github.com/repos/iojs/io.js/issues/252/labels{/name}","comments_url":"https://api.github.com/repos/iojs/io.js/issues/252/comments","events_url":"https://api.github.com/repos/iojs/io.js/issues/252/events","html_url":"https://github.com/iojs/io.js/issues/252","id":53710098,"number":252,"title":"release: bundling npm","user":{"login":"rvagg","id":495647,"avatar_url":"https://avatars.githubusercontent.com/u/495647?v=3","gravatar_id":"","url":"https://api.github.com/users/rvagg","html_url":"https://github.com/rvagg","followers_url":"https://api.github.com/users/rvagg/followers","following_url":"https://api.github.com/users/rvagg/following{/other_user}","gists_url":"https://api.github.com/users/rvagg/gists{/gist_id}","starred_url":"https://api.github.com/users/rvagg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rvagg/subscriptions","organizations_url":"https://api.github.com/users/rvagg/orgs","repos_url":"https://api.github.com/users/rvagg/repos","events_url":"https://api.github.com/users/rvagg/events{/privacy}","received_events_url":"https://api.github.com/users/rvagg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-01-08T03:12:03Z","updated_at":"2015-01-08T03:12:03Z","closed_at":null,"body":"We didn't get to this discussion in the TC meeting today even though @piscisaureus put it on the agenda (I didn't see it and we ran out of time anyway). We need to resolve how we're going to handle bundling npm for releases, specifically the 1.0.0.\r\n\r\nSome ideas:\r\n\r\n* Release as it is now\r\n* Upgrade to current 2.x.y as dictated by npm folks\r\n* Remove npm completely from deps and add a build step that downloads an appropriate version so you can `make install` it like normal and also bundle it in a tarball for release\r\n\r\nWhatever we go for, I'd like to see the npm client team be made responsible for decisions about what version to bundle (they can also take responsibility for breakages!). Perhaps we need to add @othiym23 as a collaborator and let him take on deps/npm, I doubt anybody currently on the team other than @isaacs really wants to take responsibility for it.\r\n\r\nSuggestions so we can move forward with a decision for the release?"}}