Release Proposal: v1.1.0

[Fishrock123]

(someone's gota do it)

Changes: d1fc9c6...6629751

Some notable changes:

• 4f68369 - build: disable v8 snapshots
• 497fd72 - fs: fix fd leak in ReadStream.destroy()
• 668bde8 - win,msi: broadcast WM_SETTINGCHANGE after install
• 87e62bd - crypto: implement privateEncrypt/publicDecrypt
• 45d8d9f - buffer: implement iterable interface
• cbc1262 - deps: upgrade v8 to 4.1.0.14
• 7604e6d...e17e6fb Feature/faster crypto (Feature/faster crypto #664)

Assigning to @chrisdickinson because I hear he's heading up this release. :)

(Should we use those milestone things for minor/majors?)

Edit: Updated to show changes to the final 1.1.0 commit instead of v1.x

[Fishrock123]

oh and cc @rvagg

[sam-github]

also, #325, which hasn't been merged pending a 1.1.0, I think /cc @bnoordhuis

[Fishrock123]

Yeah there's probably still a couple things that need merging. I'ma make that milestone.

[piscisaureus]

Also #668

[cjihrig]

#668 has been merged:

40e29dc - assert: use util.inspect() to create error messages

[othiym23]

There are several important regression fixes in faf34ff around proxy and SSL usage that are probably worth calling out.

There are two new subcommands (dist-tag and access) in faf34ff that are probably worth calling out.

ETA: I AM CORNFUSE

[chrisdickinson]

@rvagg Is there anything you need from me so I can do the release? I'll plan on starting this up on Monday if there are no objections between now and then.

[rvagg]

@chrisdickinson changelog, notable changes and known issues are what you can start getting ready.

I'm going to try and finish up the rest today for you.

[chrisdickinson]

@rvagg my (preferred) pubkey is:

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA5ICGWxfCj8iKi+5EdiyFK0Vnc8HwTtrIJJmxQH92TOaaz2xWuALzaNFlnyG2cHawX61LwfM+ucedkhpR+XccDPR3kbpwuQaT4PLwaXa7+fejaBJDRtT2A6HlABEX28JJu5twGODjog1thKzr8Cr0bdb5U75aX1rpIE0I/y/bn4und/QNkl5sv5k+JGpwJZVVdT1MbyqHy/zO2kz4GIsMRmJMy/gn8pXxIsgBj+chkVT7JVDDbwVthVwP+QKwXsq7LpLj1o9r2ibdoUvsO3adnQ1UVmbLjHWO+XbOCqux1OPymrUzOLNFEzAkFUVJAhEVH33vZkEEjwQBTCkshejTLQ==

[rvagg]

@chrisdickinson ready to roll .. except I DoSed the server via crontab, will be sorting that out but it shouldn't hold up your release which you can do whenever you want now.

[rvagg]

@chrisdickinson also, didn't mention this in the releases.md doc, the website update is still manual, you should ping someone from the website team who is around at the same time you're doing the release, perhaps @Fishrock123.

[Fishrock123]

Will be eating supper, but am available to update the site.

Edit: away for a bit. back at 9:15ish EST.

(ready whenever-ish really.)

[chrisdickinson]

Ok. Sorry, things got backed up yesterday, and I'm ready to get this rolling now. Apologies for the delay, all!

[rvagg]

@chrisdickinson use the release.sh script in my release-tools PR (# escapes me, typing this on mobile), it should be gtg but that PR may have to land in tc-agenda before it gets merged.

[rvagg]

And release.md also in that PR for instructions of course

[Fishrock123]

#681 for the release tooling PR.

[Fishrock123]

https://jenkins-iojs.nodesource.com/job/iojs+release/21/

[chrisdickinson]

It's released! Thanks @rvagg (edit and @indutny, and @Fishrock123!) for all of your help, the docs were great. Aside from some weirdness with my connection, everything went smoothly.

[rvagg]

btw, I think the sks-keyservers.net issue is because the submission actually points to a pool of servers, each of which have their own https identifiers and certs distinct from the alias you're using to submit.. an odd situation but I think if you submit to one of them then it should spread fine across the rest and pgp.mit.edu looks like it's one such server.