search

chicoxyzzy / node-releases

Node.js releases data
MIT License
36 stars 11 forks source link

Add Node.js release schedule #2

Closed vostrik closed 6 years ago

vostrik commented 6 years ago

Add Node.js release schedule according to this issue from browserslist: https://github.com/browserslist/browserslist/issues/75

ai commented 6 years ago

Should we normalize JSON in this package?

vostrik commented 6 years ago

This question for me or for @chicoxyzzy ? Excuse me, don't understand :)

chicoxyzzy commented 6 years ago

@ai do you mean changes in https://github.com/chicoxyzzy/node-releases/pull/2/files#diff-7cea08e9ebf9d883a3470167b9847dc3 (made by https://github.com/chicoxyzzy/node-releases/pull/2/files#diff-2abba6afacec5511aa533482df8a3b64L27)? If yes, then I'm not sure it has any value. This data is only needed for machines, not humans, so we can probably save some bytes. Though I don't have any strong opinion on that

ai commented 6 years ago

@chicoxyzzy I mean that JSON format in this PR is different than in project.

But it is up to you. It was just a suggestion. If a format is OK for you. Let’s keep it.

vostrik commented 6 years ago

@chicoxyzzy I replaced yarn.lock with package-lock.json.

chicoxyzzy commented 6 years ago

@ai you mean https://github.com/chicoxyzzy/node-releases/pull/2/files#diff-d23bac319c5786b53da435925e1b09ca? Yes, it's different from previous data. It's from another source and it contains additional info about major releases.