Is it time to update release date information?

[sam-github]

Could the release dates for LTS, current, and next (12.x) get updated?

https://github.com/nodejs/Release/wiki has (or links to) the various locations of this information. I think it could be brought together a bit more, but as long as its findable, it works.

It would be nice to have the 10.x schedule extended to the next semver-minor (10.17). That would give me a target for TLS1.3 in 10.x (for example).

I think 10.16.0 is being done by @BethGriggs not @MylesBorins, so https://github.com/nodejs/Release/wiki#q2-2019-dubnium-10x-release-schedule-draft may need updating.

Now that 12.x is almost here, I think its time to extend https://github.com/nodejs/Release#release-schedule with 13.x and 14.x. I've been doing some extrapolating lately on when I thnk they'd be based on old dates to see if we will have a FIPS gap (see nodejs/TSC#677). It would help to have the LTS group's expected dates here.

11.x had a good list in #397, but its almost to the end. I think it doesn't need to be extended because the very last release by @codebytere will be the last? Perhaps its EOL date should be added.

[MylesBorins]

@sam-github we just updated the dates in the wiki, does that look better to you?

[sam-github]

@MylesBorins It would help if the 10.x plan went until 10.17.0, and 13.x and 14.x had predictions.

This might seem far away, but its so I can predict when semver-minors might next be released on 10.x if they miss 10.16.0, and for 13.x & 14.x, without dates for them I can't predict the "fips gap" very accurately in nodejs/TSC#677.

If not now, perhaps when or shortly after 12.x and 10.16.0 are released, the next LTS and minor cycle (respectively) can be added?

[MylesBorins]

We’ve generally been doing this on a quarterly basis… we can plan out 10.17, but TBH there was an intention of thinking about that until the end of Q2. We could just pick dates for 13 / 14 now if we want, easily enough.

…

On Apr 4, 2019, at 5:27 PM, Sam Roberts ***@***.***> wrote: @MylesBorins <https://github.com/MylesBorins> It would help if the 10.x plan went until 10.17.0, and 13.x and 14.x had predictions. This might seem far away, but its so I can predict when semver-minors might next be released on 10.x if they miss 10.16.0, and for 13.x & 14.x, without dates for them I can't predict the "fips gap" very accurately in nodejs/TSC#677 <nodejs/TSC#677>. If not now, perhaps when or shortly after 12.x and 10.16.0 are released, the next LTS and minor cycle (respectively) can be added? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#431 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV6sj7mtJM3XXvN3JMz30e1ZuxGosks5vdm4sgaJpZM4cWBla>.

[jasonkarns]

According to the schedule.json, 11 is in maintenance mode as of a week ago (2019-04-01), but 12 doesn't start until 2019-04-23. That puts us in a "temporal dead zone" from 4-1 to 4-23 where there is (strictly speaking) no "Current Release".

For users seeing "11.13.0 Current" on nodejs.org is no big deal for users. But it's problematic for tooling that consumes the schedule.json file directly.

I don't have any solutions or requests here. But the gap in the dates is causing a bit of a problem for nodenv/node-build whereby our tooling is attempting to warn users that 11.13.0 is in maintenance mode, but there isn't a "Current" release to point them to.

So I guess maybe this is a request for clarification, if the date gap was accidental (perhaps the dates were intended to overlap?) or perhaps the change to schedule.json was just made prematurely? Any guidance or input here?

[BethGriggs]

I think all of this was covered by the updates in #434