update schedule.json

[SEWeiTung]

1. According to our plan in https://nodejs.org/en/about/releases/, we've now published the 13th version of Nodejs, add this to the schedule for the maintance.

2. Add the missing coding name for v12.

[Trott]

Looks good to me but I never even noticed this file before (that I can remember anyway) so I'll leave the actual approving to others (which has already happened anyway).

[nschonni]

Should the build just curl this file from https://github.com/nodejs/Release/blob/master/schedule.json instead of keeping a separate copy?

[SEWeiTung]

@nschonni: Not sure yet, but according to your description, it seems this file here is duplicated?
@nodejs/release: It seems this file has been defined in the https://github.com/nodejs/Release/blob/master/schedule.json, so do we have to maintain this copy here? Just for a confirm.
If you think this file can be removed, I'll remove it.

[richardlau]

I think the file in the repository is a placeholder that gets overridden during build by load-schedule (called by deploy):

nodejs.org/package.json

Lines 12 to 14 in 575a47e

	"deploy": "npm-run-all load-schedule build:deploy external:survey gzip",
	"load-versions": "node scripts/load-versions.js",
	"load-schedule": "curl -sS https://raw.githubusercontent.com/nodejs/Release/master/schedule.json -o source/schedule.json",

(see #1890)

[XhmikosR]

Can't we remove the folder and the file completely?

[SEWeiTung]

I think the file in the repository is a placeholder that gets overridden during build by load-schedule (called by deploy):

nodejs.org/package.json

Lines 12 to 14 in 575a47e

	"deploy": "npm-run-all load-schedule build:deploy external:survey gzip",
	"load-versions": "node scripts/load-versions.js",
	"load-schedule": "curl -sS https://raw.githubusercontent.com/nodejs/Release/master/schedule.json -o source/schedule.json",

(see #1890)

So this file should be totally removed, or just run the script to update the file, just like what I submitted?

[XhmikosR]

This patch is moot since this is overwritten on build time. We should instead see if we can just remove the folder and the file.