Q2 2017 Boron (6.x) Release Schedule (Proposal)

[MylesBorins]

For Q2 of 2017 there will be an Active LTS release for Boron (6.x) on the first Tuesday of every month. A new r.c. will come out on the third Tuesday of each month.

Date	Release	Emoji
May 2nd	v6.10.3	🚀
May 16th	v6.11.0-rc	🐢
Jun 6th	v6.11.0	🎶

due to the month of May having 5 Tuesdays I've scheduled a minor release. This shortens the r.c. time to 3 weeks, we have traditionally done 4. I do not believe we will be assuming any extra risk and I find the schedule much easier to follow this way.

edit:

this schedule is currently a proposal and needs @nodejs/lts to review it first.

[jasnell]

A small tiny part of my brain now really wishes we would assign emoji's to each LTS release rather than codenames from the periodic table.

[jasnell]

This schedule LGTM

[gibfahn]

Schedule LGTM

[Fishrock123]

Schedule seems fine but I think specific emoji may just be more confusing that the numbers themselves.

[sam-github]

LGTM, will this go in the nodejs/LTS README?

I guess we don't need a 4.x release schedule because we intend to release now only on demand?

It would be nice to have a similar schedule for 7.x.

[MylesBorins]

Emojis were just meant to be fun... Not to be used during release. I can remove from initial comment

[MylesBorins]

We have generally kept these schedules in an issue. Afaik there are no more planned v7 releases We've only had a schedule like this for LTS

…

On May 24, 2017 11:38 AM, "Sam Roberts" ***@***.***> wrote: LGTM, will this go in the nodejs/LTS README? I guess we don't need a 4.x release schedule because we intend to release now only on demand? It would be nice to have a similar schedule for 7.x. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#206 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV35OeetBAJcJaCH0LQ7ZQDmpkWaeks5r9E8NgaJpZM4NIYSs> .

[evanlucas]

Afaik there are no more planned v7 releases

There probably should be. There is a regression in v7.10.0 that has uncatchable errors in http.request(). I doubt I'll have the time this week, but I could probably cut on early next week

[mhdawson]

Schedule LGTM

[MylesBorins]

Unfortunately the v6.11.1-rc is delayed due to our tooling not working. Changes to github's abuse detection mechanism are stopping branch-diff from doing it's thing.

I'm going to push to v6.11.1 release dates by one week to hopefully give us some time to figure this out

[MylesBorins]

v6.11.1 has been delay further due to security release. Expect a new schedule for the next quarter