Status and plan for v6 LTS

[Fishrock123]

cc @nodejs/lts we should come with an interim plan for v6 at least for now.

I worked on a script for the bot a lot last week which should help here but it's not quite "production-ready" yet I'd say: nodejs/github-bot#90

[jasnell]

Plan for what precisely?

[MylesBorins]

I was planning on doing a batch backport similar to what I've done for v4
in the past. having more people take on the responsibility would obviously
be awesome

On Mon, Nov 7, 2016, 9:57 AM James M Snell notifications@github.com wrote:

Plan for what precisely?

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
#153 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAecV-I3f4Xfe5K3hvxeg1Bwu_7xhhR_ks5q7zxSgaJpZM4KrSzp
.

[Fishrock123]

Plan for what precisely?

Upcoming releases &/or process

[jasnell]

If we can get automated checking/validation of backportable semver-patch PRs working reliably then that would definitely make things easier. Based on a number of conversations I've had with folks, I'm thinking that one release per month is a solid cadence.

[mhdawson]

I'm +1 on the 1/release per month cadence.

[bnoordhuis]

That doesn't mean delaying security fixes for up to a month, right? Only normal releases?

[evanlucas]

I'm +1 on 1/month with as many as needed for security releases

[Fishrock123]

@bnoordhuis correct.

[MylesBorins]

So I'm doing my first bit of backporting of both v4 and v6 right now and finding that it surprisingly does not add that much work. Since everything needs to be audited for both line it can be done in parallel. I'm still looking to get some help and I know that @gibfahn is interested in getting involve, but figured it would be good to report that I don't think managing 2x the LTS releases will be anywhere close to 2x the work

edit: this was definitely not the case for managing v0.10 and v0.12... but the delta there was substantially different

[MylesBorins]

Discussed in today's wg meeting. Going to open another issue to lay out released for next couple month's