Automating release post #88
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Haven't tested it yet, but this looks pretty awesome! |
|
I can see some problems here but not time just yet to comment, the node v4 release is going to have a structure more similar to io.js than 0.12, including the files that will be dropped, also we have a pretty mature changelog format from io.js that we'll be using |
|
Thanks for your initial thoughts @rvagg! It handles io.js changelog format already. I'll change the files list too resemble iojs' instead. Any other thoughts? Just generated for v3.3.0 after changing versions ---
date: 2015-09-04T11:43:52.691Z
version: 3.3.0
category: release
title: Node v3.3.0 (Stable)
slug: node-v3-3-0-stable
layout: blog-post.hbs
---
## 2015-09-02, Version 3.3.0, @rvagg
### Notable changes
* **build**: Add a `--link-module` option to `configure` that can be used to bundle additional JavaScript modules into a built binary (Bradley Meck) [#2497](https://github.com/nodejs/node/pull/2497)
* **docs**: Merge outstanding doc updates from joyent/node (James M Snell) [#2378](https://github.com/nodejs/node/pull/2378)
* **http_parser**: Significant performance improvement by having `http.Server` consume all initial data from its `net.Socket` and parsing directly without having to enter JavaScript. Any `'data'` listeners on the `net.Socket` will result in the data being "unconsumed" into JavaScript, thereby undoing any performance gains. (Fedor Indutny) [#2355](https://github.com/nodejs/node/pull/2355)
* **libuv**: Upgrade to 1.7.3 (from 1.6.1), see [ChangeLog](https://github.com/libuv/libuv/blob/v1.x/ChangeLog) for details (Saúl Ibarra Corretgé) [#2310](https://github.com/nodejs/node/pull/2310)
* **V8**: Upgrade to 4.4.63.30 (from 4.4.63.26) (Michaël Zasso) [#2482](https://github.com/nodejs/node/pull/2482)
### Known issues
See https://github.com/nodejs/io.js/labels/confirmed-bug for complete and current list of known issues.
* Some uses of computed object shorthand properties are not handled correctly by the current version of V8. e.g. `[{ [prop]: val }]` evaluates to `[{}]`. [#2507](https://github.com/nodejs/node/issues/2507)
* Some problems with unreferenced timers running during `beforeExit` are still to be resolved. See [#1264](https://github.com/nodejs/io.js/issues/1264).
* Surrogate pair in REPL can freeze terminal. [#690](https://github.com/nodejs/io.js/issues/690)
* `process.send()` is not synchronous as the docs suggest, a regression introduced in 1.0.2, see [#760](https://github.com/nodejs/io.js/issues/760).
* Calling `dns.setServers()` while a DNS query is in progress can cause the process to crash on a failed assertion. [#894](https://github.com/nodejs/io.js/issues/894)
* `url.resolve` may transfer the auth portion of the url when resolving between two full hosts, see [#1435](https://github.com/nodejs/io.js/issues/1435).
### Commits
* [[`1a531b4e44`](https://github.com/nodejs/node/commit/1a531b4e44)] - **(SEMVER-MINOR)** Introduce --link-module to ./configure (Bradley Meck) [#2497](https://github.com/nodejs/node/pull/2497)
* [[`d2f314c190`](https://github.com/nodejs/node/commit/d2f314c190)] - **build**: fix borked chmod call for release uploads (Rod Vagg) [#2645](https://github.com/nodejs/node/pull/2645)
* [[`3172e9c541`](https://github.com/nodejs/node/commit/3172e9c541)] - **build**: set file permissions before uploading (Rod Vagg) [#2623](https://github.com/nodejs/node/pull/2623)
+ alot more commits omitted for brevity's sake in this example
Source Code: http://nodejs.org/dist/v3.3.0/node-v3.3.0.tar.gz
Macintosh Installer (Universal): http://nodejs.org/dist/v3.3.0/node-v3.3.0.pkg
Windows Installer: http://nodejs.org/dist/v3.3.0/node-v3.3.0-x86.msi
Windows x64 Installer: http://nodejs.org/dist/v3.3.0/x64/node-v3.3.0-x64.msi
Windows x64 Files: http://nodejs.org/dist/v3.3.0/x64/
Linux 32-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-linux-x86.tar.gz
Linux 64-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-linux-x64.tar.gz
Solaris 32-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-sunos-x86.tar.gz
Solaris 64-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-sunos-x64.tar.gz
Other release files: http://nodejs.org/dist/v3.3.0/
Website: http://nodejs.org/docs/v3.3.0/
Documentation: http://nodejs.org/docs/v3.3.0/api/
Shasums:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
3ec6fb8d7a9ad30f673a8e114a98b2dcd6b802a375b87e5b3039dac51a967423 iojs-v3.3.0-darwin-x64.tar.gz
c52bc752d2b0af38c4e8ffc83a6132df7e4ff84775db2ecaaa71893a873d4cdf iojs-v3.3.0-darwin-x64.tar.xz
36136360c082a6cb0753b338f76ac110d2b183846a9df2e8934bb5257675d35b iojs-v3.3.0-headers.tar.gz
3067437c9338c0415fe721fa5a67995f9435e6f313b4fab00a65f28e824ecafa iojs-v3.3.0-headers.tar.xz
571b12fa6fcf658873ee556fc61edab07c12daae092cfe6bdeb173df3449214c iojs-v3.3.0-linux-armv6l.tar.gz
6c210d78728c51a69ab6fdbf096c69d3632897bcc4eed4c60958e34b642ed53f iojs-v3.3.0-linux-armv6l.tar.xz
af44c0644128a552896247866e283d3991934025eee4bdc8c288439bb8d5516f iojs-v3.3.0-linux-armv7l.tar.gz
688b4506efaf2fb330c6b3d6dbe80f47af60df2cdaf24f47f0ed966d01815819 iojs-v3.3.0-linux-armv7l.tar.xz
c9b1c51b7cc780c19df504e29e26b27ee89f7bf6f8d601da597f52e7e39767fd iojs-v3.3.0-linux-x64.tar.gz
add2cd394886d7d3a92bc84e9af6e4a0d509060f0b63bf4b11de6471046043e8 iojs-v3.3.0-linux-x64.tar.xz
197716f55592c85e04f644f9e2ef0d276cf90fecba3cf0e01bad6d3d628446dd iojs-v3.3.0-linux-x86.tar.gz
a4ef6de573441b50bffe8a82f66ebf941a238f175d9decc3d021a615110722d4 iojs-v3.3.0-linux-x86.tar.xz
db18a6029c8b9fdc0b95287b1a51e4ea753b515f3f7799e4a5f85ff67ef7a036 iojs-v3.3.0.pkg
e84a649858e6f5c1458c0d5d7bf1952f78e93a26ea6bc519222e92e43e2fadde iojs-v3.3.0.tar.gz
8b317162af3e0e81b3f5efcda664e5f3525e6e1ab4c21b446db83cf9c4028a32 iojs-v3.3.0.tar.xz
68289641c2780e8c34fc9d4c1c92290d5adb7612b4979722523d6212c79bb0d0 iojs-v3.3.0-x64.msi
1d692b5427d6c27dcdff6fe500e209a3d44de4c069d63e5213457986ffae727d iojs-v3.3.0-x86.msi
0ecb7cd753e55e611ab2235f97ce59205486af4f157b2396ba74c8405e89d622 win-x64/iojs.exe
9b4e1cbe8e731d14f39d006613482ddd143c6c7f7e77d41f37fc8dc231a0ab24 win-x64/iojs.lib
27e8129adc45c7e4cbfbbf59db419c3f7ba0a8a03bee7532e3d2030c1c178680 win-x86/iojs.exe
6c7c3508599353f2718c37f50db74950a64021df625a3ad407b8848099f7f1e1 win-x86/iojs.lib
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJV5uz/AAoJEMJzeS99g1Rdsx0H/0XR2EIUlaT8g6hyYhwlB3Wo
dhwoDm5z1/NcjTiCS5eGZm9WvPV+2kfMAbY02+01hcdl1oNSZ3BgIqyHZQtLDEd9
y/S+QnH33VaLWbWjs0r2oeF9E8ifGLPYiR/4DPE4VhcbZZSgBP06mC8KbR5Cjz0e
eodXVHE24/R/x/0KRrzQ9zAVs1EULrhrobBkCp1Ftn/dyrJQyOFOeYuTKqT2ZxpL
CqfWVlrFLe6qNWtxWb6oXunWfuGvt0hlloPjzo74/TEOhjUNFxG52ucHOT0MUn5e
iXzBUSLbuW/8DlzCLY9ACdHsebcTpMRa0srSFthckRFinj0wQ1gFQbQcqWUtw18=
=J64o
-----END PGP SIGNATURE-----
|
phillipj
force-pushed
the
build-release-posts
branch
from
03ded8d
to
a2e0fa1
Compare
|
top of my head:
|
|
Awesome feedback 👍 Tbh I would like to extract the logic around files into something reusable, as the download matrix on the downloads page is pretty much exactly the same thing. |
|
This is awesome :) |
phillipj
force-pushed
the
build-release-posts
branch
from
a2e0fa1
to
598cfc3
Compare
|
Decided to target node v4 in the first version of this script. Just pushed necessary URL adjustments to the list of files, re-arranged the items and used the same terms and order as we do on the download matrix on out downloads page. Are we going to have a unique URL per release on nodejs.org? Seems the old website did seeing the website URL in the release post, e.g. http://nodejs.org/docs/v0.12.7/ Just generated for v3.3.0: Windows 32-bit Installer: http://nodejs.org/dist/v3.3.0/node-v3.3.0-x86.msi
Windows 64-bit Installer: http://nodejs.org/dist/v3.3.0/node-v3.3.0-x64.msi
Windows 32-bit Binary: http://nodejs.org/dist/v3.3.0/win-x86/node.exe
Windows 64-bit Binary: http://nodejs.org/dist/v3.3.0/win-x64/node.exe
Mac OS X 64-bit Installer: http://nodejs.org/dist/v3.3.0/node-v3.3.0.pkg
Mac OS X 64-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-darwin-x64.tar.gz
Linux 32-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-linux-x86.tar.gz
Linux 64-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-linux-x64.tar.gz
SunOS 32-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-sunos-x86.tar.gz
SunOS 64-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-sunos-x64.tar.gz
ARMv6 32-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-linux-armv6l.tar.gz
ARMv7 32-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-linux-armv7l.tar.gz
ARMv8 64-bit Binary: http://nodejs.org/dist/v3.3.0/node-v3.3.0-linux-arm64.tar.gz
Source Code: http://nodejs.org/dist/v3.3.0/node-v3.3.0.tar.gz
Other release files: http://nodejs.org/dist/v3.3.0/
Website: http://nodejs.org/docs/v3.3.0/
Documentation: http://nodejs.org/docs/v3.3.0/api/ |
phillipj
force-pushed
the
build-release-posts
branch
from
598cfc3
to
a03b493
Compare
2 tasks
Stitches data from different sources into a release blog post about the latest version released.
phillipj
force-pushed
the
build-release-posts
branch
from
a03b493
to
aaa6aff
Compare
|
This is ready to go for its first debut. Into master or node-4.0-release @fhemberger? |
|
node-4.0-release, please. So we have everything we need in one place. |
|
Landed into node-4.0-release with fd14e76 |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stitches data from different sources into a release blog post about the latest version released. Its in dire need for some testing, I could take a look at that after getting some feedback on it as is.
Closes #47.
Generated for v0.12.7: