Nominate npm releaser(s) for readable-stream #134
Description
As much as I'd like to be involved I have to be honest about my time availability and I just don't have the bandwidth to grok where this project even is at right now.
So, I'd like @nodejs/streams to nominate an individual (or >1 indiviuals if you have a plan for how that'll work) that should have npm publish rights for this package.
For background purposes, the current situation is like this:
@latest tag sticks to the 1.0.x releases where the x matches the Node.js v0.10.x version, with the code extracted out of Node.js, passed through the build/ scripts in the v0.10 branch to make it stand-alone and browserifiable. When you npm install readable-stream you get this, which is streams2.
@1.1 tag (which I don't think it's even possible to publish under with npm now because it doesn't like version-like tags) sticks to the 1.1.x releases where the x matches the Node.js v0.11.x version, with the code extracted out of Node.js, passed through the build/scripts on the master branch. You have to npm install readable-stream@1.1 (or a specific version) to get this branch, which is streams3.
We currently have nothing for 0.12 but it may make sense to continue on the 1.1.x series with those for continuity.
My hope was that we would jump a semver-major (or two) and start tracking io.js because it represents the best state of streams and it should go in @latest. How that works exactly is up to you guys.
Have a meeting, get a consensus or something and let me know who should be doing the releases.