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

Semver Minor Tracking #298

Closed
MylesBorins opened this issue Jan 9, 2018 · 27 comments
Closed

Semver Minor Tracking #298

MylesBorins opened this issue Jan 9, 2018 · 27 comments

Comments

@MylesBorins
Copy link
Contributor

We have a month with 5 Tuesdays, this means we can do a Semver Minor release!!!

I'm thinking it makes sense for both 6.x and 8.x.

Will follow up with a list of potential commits soon (unless someone else wants to do it first :D)

@MylesBorins
Copy link
Contributor Author

@nodejs/lts quick ping, do people have time to meet and discuss this at all next week?

@gibfahn
Copy link
Member

gibfahn commented Jan 11, 2018

Next week SGTM

1 similar comment
@mhdawson
Copy link
Member

Next week SGTM

@MylesBorins
Copy link
Contributor Author

I've created two gists
node v6.x semver minors
node v8.x semver minors

I'm quite sick and may not have the ability to review this in a timely fashion

@nodejs/release @nodejs/lts @nodejs/collaborators @nodejs/tsc would people be able to review these lists and please request the semver minor commits you would like to see on the next LTS release on v6.x and v8.x

@TimothyGu
Copy link
Member

Let me know what I need to do to get nodejs/node#17365 into v6.x, or if it is already ready to be applied.

@mcollina
Copy link
Member

mcollina commented Jan 12, 2018

I would like to have:

nodejs/node@c5c4a534d1
nodejs/node@4b0c8759d3
nodejs/node@edb9846884

backported.

(edited by @addaleax: made commits clickable)

@MylesBorins
Copy link
Contributor Author

Another quick ping to @nodejs/collaborators to review these lists. I really would appreciate any work y'all can do.

@evanlucas
Copy link

I would like to see nodejs/node@8d90db5120 and the async_hooks commits land in v8.x

@AndreasMadsen
Copy link
Member

@evanlucas Indeed, I tried adding lts-watch-v8.x to all the async_hooks changes.

@MylesBorins
Copy link
Contributor Author

@AndreasMadsen would you be able to do a batch backport?

@AndreasMadsen
Copy link
Member

@MylesBorins I can definitely try.

@MylesBorins
Copy link
Contributor Author

@AndreasMadsen for async_hooks were you talking about 8.x or 6.x?

@MylesBorins
Copy link
Contributor Author

MylesBorins commented Jan 15, 2018

@MylesBorins
Copy link
Contributor Author

We would like to land nodejs/node#13467 but it requires manual backport of the documentation. Would someone be interested in taking that on?

@MylesBorins
Copy link
Contributor Author

@Trott would you want to backport nodejs/node#14910 to v6.x? nbd if you don't have time

@MylesBorins
Copy link
Contributor Author

@cjihrig would you want to backport nodejs/node#15034 to v6.x?

@MylesBorins
Copy link
Contributor Author

@nodejs/crypto would anyone want to backport nodejs/node#15206?

@MylesBorins
Copy link
Contributor Author

@danbev could you backport nodejs/node#16790

@gibfahn
Copy link
Member

gibfahn commented Jan 15, 2018

@maclover7 could you backport nodejs/node#16386 ?

@AndreasMadsen
Copy link
Member

AndreasMadsen commented Jan 16, 2018

async_hooks should not land in 6.x. I have already added dont-land labels for 6.x

@AndreasMadsen
Copy link
Member

AndreasMadsen commented Jan 16, 2018

I think this is the list of async_hooks commits there should be backported. Some of these are trace_events related, but async_hooks and trace_events becomes connected as we are now emitting async_hooks event through trace_events. I would be nice to backport the trace_events changes anyway. I will try and make a batch backport, although I might need help with nodejs/node#16565.

@gibfahn
Copy link
Member

gibfahn commented Jan 16, 2018

although I might need help with nodejs/node#16565.

If it'd make more sense for @yhwang to backport that one separately that's fine by me.

@AndreasMadsen
Copy link
Member

@gibfahn It wasn't too big of an issue. I have already backported the first 7 commits.

I hope to have it all done within the next 6 hours. I would appreciate if we can put v8.x-staging on hold until then, so I don't have to do all this again.

@AndreasMadsen
Copy link
Member

I was missing two commits there was under the async_wrap tag.

@AndreasMadsen
Copy link
Member

@MylesBorins @gibfahn @evanlucas I have finished the async_hooks backport, the list became quite long: nodejs/node#18179 Please merge this as fast as possible, I don't want to do it again because some commit got merged into v8.x-staging.

@TimothyGu
Copy link
Member

TimothyGu commented Jan 22, 2018

nodejs/node#17470 should also be included in the v6.x backport of WHATWG URL parser as it fixes a critical memory leak. It had not been landed yet at the time of my backport PR, and I neglected to add it in after it had by mistake.

@MylesBorins
Copy link
Contributor Author

@TimothyGu lands cleanly on v8.x with green tests. Doesn't work on v6.x as nodejs/node@9236dfe utilizes std::move. Requesting backport

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

No branches or pull requests

7 participants