Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Schedule for v4.4.5 and v4.5.0 #102

Closed
MylesBorins opened this issue May 11, 2016 · 11 comments
Closed

Release Schedule for v4.4.5 and v4.5.0 #102

MylesBorins opened this issue May 11, 2016 · 11 comments
Labels

Comments

@MylesBorins
Copy link
Contributor

MylesBorins commented May 11, 2016

Hey All, I'd like to toss some dates around for upcoming LTS release to see if everyone is on the same page.

Are people open to

v4.4.5 released on Tuesday May 24th (with a release candidate next Tuesday May 17th)

v4.5.0 released on Tuesday June 14th (with a series of release candidates starting Tuesday May 31st)

edit: corrected date for v4.5.0

@Fishrock123
Copy link
Contributor

Fishrock123 commented May 11, 2016

@thealphanerd Why's v4.5.0 so far out? With this OpenSSL release schedule (~2 months?) that may run into a security release again.

@richardlau
Copy link
Member

@thealphanerd Presumably you mean Tuesday June (not July) 14th?

@MylesBorins
Copy link
Contributor Author

@richardlau indeed. Good eye!

@jasnell
Copy link
Member

jasnell commented May 16, 2016

That schedule looks fine for me. If there happens to be another OpenSSL release in that time we can deal with it then.

@mhdawson
Copy link
Member

Looks good to me.

@Fishrock123
Copy link
Contributor

I'm not comfortable with it. I'd like to ensure we can get a v4.5.0 out when we plan to.

@thealphanerd Any idea what minors are scheduled so far for that?

@MylesBorins
Copy link
Contributor Author

minors agreed upon:

minors with lts-watch flag but not discussed:

@Fishrock123 I'm unsure how to do an extended RC on a minor and not run the risk of a security fix pushing it off. How do you think we could better approach it?

@Fishrock123
Copy link
Contributor

@thealphanerd Should we just do RC's sooner? Do we need a second staging branch? I'm not sure. People have been waiting quite a few months for some of those and I'd hate to see it delayed again because of a semi-scheduled OpenSSL release-y thing again. :(

Remember we are already significantly behind the schedule we original had discussed for it, aka alongside v6.

If you need any help doing that, I should be able to jump it..

@Fishrock123
Copy link
Contributor

Fishrock123 commented May 19, 2016

Also nodejs/node#6404 probably doesn't need to be backported, one can just access the _connecting property.

Aside, I'd love to be able to land #108 in it, but that may be too short. Although by that time it will be almost 2 months anyways.

@MylesBorins
Copy link
Contributor Author

@Fishrock123 I can get an RC out next week soon after the v4.4.5 release, no objections regarding #108, wrote in the thread

@MylesBorins
Copy link
Contributor Author

I'm going to close this for now and open a new thread about release cadance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants