Just before node v4 got released, a script (scripts/release-post.js) for automatically creating release blog post (locale/en/blog/release/v4.0.0.md) was created in #88, atleast a first draft of it.

I would like to create a list of tasks to further improve that script, but it requires feedback about the current state of it.

• Fetch changelog from tag instead of master
• Add CLI argument to specify version (w/fallback to https://nodejs.org/dist/index.json)
• Leave pleaceholder for shasums if they're not found in /dist/
• Check to see if all of the binaries are available before putting links to them
• Remove ## header from changelog
• Add Author: <full name> in blog header, see #186 comment for hints

Most importantly: was it useful at all while releasing v4 @rvagg? If not, what has to change?

Current flow

There were some assumptions made about how the latest version number should be resolved, what changelog too use etc.

a) Fetch latest version from https://nodejs.org/dist/index.json
    |
    v
b) Fetch changelog from node's master branch, find changelog for latest version
    |
    v
c) Fetch shasums for latest version from https://nodejs.org/dist/
    |
    v
d) Render blog post with Handlebars template ./scripts/release.hbs
    |
    v
c) Write content to file ./locale/en/blog/release/v<VERSION>.md

Changelog

One thing I got curious about while observing the release, was which changelog should be used. It didnt look the v4's changelog got merged into master at the time of creating the release blog post, therefore the changelog retrieval would probably fail due to version mismatch.

What would be best approach? (1) from the release proposal v4.0.0 or (2) v4.x tagged changelog?

Any other thoughts?