Repository navigation
Node.js v4.0.0 Release Checklist for nodejs.org #101
Description
Activity
- Run
scripts/load-versions.jsafter release once to get the full versions list (needed to determine current version and full release history). - Remove the comment here: https://github.com/nodejs/new.nodejs.org/blob/master/layouts/download-releases.hbs#L13 (and remove the class from h2, we're not using this style any longer).
I'd love to get #98 and #100 merged before the release as well.
- Run
- Repoint Changelog on front page from https://github.com/nodejs/node-v0.x-archive/blob/master/ChangeLog to https://github.com/nodejs/node/blob/master/CHANGELOG.md, reversing fix in New site is live with 0.12.7 everywhere, except link to changelog #84
I've created a separate node-4.0-release branch (I checked off the tasks which have already been done). Please commit required changes there, so we just need to merge it once the release is finished.
The
release-post.jsscript found in #88 could be worth testing, atleast for filling in the changelog, files and shasums. It'll createlocale/en/blog/release/v4.0.0.mdlocally and can be edited by hand from there..It fetches data from three different sources, which all have to be updated / merged into node's repo master before running the script:
@phillipj 👍 Let's do this.
So I can edit the resulting file and add some custom text about the release after it's been created? And
release-post.jsis run by hand to do the generating, not on the server at deploy time?So I can edit the resulting file and add some custom text about the release after it's been created?
Yes, followed by you commiting it to the repo.
It's all manual by hand atm. We could ofc discuss something fancier / automatic later.
- Update the ES6 documentation @ https://nodejs.org/en/docs/es6/, note the talk of arrow functions is no longer correct for v4. We need a volunteer to update this.
all done I think
@rvagg https://github.com/nodejs/node/blob/master/CHANGELOG.md still shows v3.3.0 as latest version.
fixed now with a merge of nodejs/node#2742, I probably could have got away with not waiting for review but pehaps we ought to use tagged links to CHANGELOG.md in future, e.g. https://github.com/nodejs/node/blob/v4.0.0/CHANGELOG.md
Yes, we have already switched the link on the home page to the tagged one.
See nodejs/node#2522 for ongoing details; the current plan is for it to be released in a bit over 24 hours from now so I want to make sure that (a) we have people available who can fix up the website if needed and (b) we capture all of the items that we know need doing on the website end.
The obvious differences between v4.x and v0.12.x for the website that I can think of are:
What do we need to get done?
Is there anything else I'm not seeing? I'm assuming that nodejs.org/dist/index.json will be automatically picked up and the downloads pages generated for them, is that correct?