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.

Sign up for GitHub

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

Jump to bottom

Release WG meeting Tuesday 19th September 2017 #244

Closed
gibfahn opened this issue Sep 16, 2017 · 33 comments
Closed

Release WG meeting Tuesday 19th September 2017 #244

gibfahn opened this issue Sep 16, 2017 · 33 comments
Labels
lts-meeting

Comments

@gibfahn
Copy link
Member

gibfahn commented Sep 16, 2017 •
edited
Loading

Present

@nodejs/lts, maybe @nodejs/release if they're interested

When

Where

Hangouts on Air:

Agenda

nodejs/LTS

CTC lts-agenda issues and LTS lts-agenda issues

nodejs/node

https://github.com/nodejs/node/pulls?utf8=%E2%9C%93&q=is%3Aopen%20is%3Apr%20label%3Av6.x%20

https://github.com/nodejs/node/pulls?q=is%3Apr+label%3Alts-watch-v6.x+label%3Asemver-minor+is%3Aclosed

  • lib: var to const #13756
  • (v6.x backport) process: add --redirect-warnings command line argument #14480
  • [v6.x backport] doc,assert: document stackStartFunction in fail #14427
  • tracking issue: full VS2017 support #13052
  • (v6.x backport) src: allow CLI args in env with NODE_OPTIONS #12677
  • inspector: enable --inspect-brk in v6 #12615
  • Review semver-minor backports #228

other

Any questions in #node-dev on IRC or comments in this thread

@nodejs/lts Please 👍 if you can make the meeting, and 👎 if you cannot.
@gibfahn
Copy link
Member Author

gibfahn commented Sep 16, 2017

I've left the semver-minor commits on the agenda because I think it'd be good to agree on them now, we could wait another 3 weeks, but then we're getting very close to the 6.12.0 rc. Given that some of these have been waiting for ~5 months, and are IMO needed on v6.x, I'd rather we got them locked in now.

@MylesBorins
Copy link
Contributor

+1 to discussing the semver minors on monday

We want to add discussing V8 6.1 on 8.x LTS as well.

Unfortunately I'm going to be on a flight at the time of the meeting, would people be opposed to pushing it forward a couple hours?

@gibfahn
Copy link
Member Author

gibfahn commented Sep 16, 2017

So 7 pm UTC? Fine by me.

@MylesBorins
Copy link
Contributor

I was thinking forward rather than back.

Might even be easier to push by 24 hours if people are open.

If the scheduling doesn't work that is totally fine. I'm on flights from 8:40 am UTC -> 9:30 pm

@jasnell
Copy link
Member

jasnell commented Sep 16, 2017

Have a specific time in mind?

@MylesBorins
Copy link
Contributor

The simplest thing I could suggest would be pushing exactly 24 hours

@Fishrock123
Copy link
Contributor

I should be able to make it to either

@gibfahn
Copy link
Member Author

gibfahn commented Sep 16, 2017 •
edited
Loading

Tuesday 19th at 21:00 UTC SGTM. There's nothing else on in the calendar then. Given that pretty much everything on the agenda is v6.x backports, having you in the meeting seems pretty key @MylesBorins 😁 .

I'll change the agenda, we can change back if people can't make it.

EDIT: Do use the 👍 👎 to say whether you can make the new times.

@sam-github
Copy link
Contributor

That's 2pm pst, right? Works for me, though I have to walk out my door at exactly 3pm to meet the school bus at the end of the block.

@jasnell
Copy link
Member

jasnell commented Sep 17, 2017

If we're pushing to Tuesday, I have a conflict at 2pm PST. 1pm is open, however.

@sam-github
Copy link
Contributor

On Tuesday, anytime from 6am-8am, 9am-5pm PST works for me.

@gibfahn
Copy link
Member Author

gibfahn commented Sep 17, 2017 •
edited
Loading

Okay, pushed earlier an hour for James.

Is there anyone who can't make this time?

@hutson
Copy link
Contributor

hutson commented Sep 18, 2017

@gibfahn

  • Issue title, 18th => 19th
  • Under When, Monday => Tuesday

@sam-github sam-github changed the title Release WG meeting 18th September 2017 Release WG meeting Tuesday 19th September 2017 Sep 18, 2017
@sam-github
Copy link
Contributor

@MylesBorins @jasnell @mhdawson do you have power to update the meeting time in the node calendar?

@gibfahn
Copy link
Member Author

gibfahn commented Sep 18, 2017

@hbetts updated, I think it's correct now.

@Fishrock123
Copy link
Contributor

This might be early for @rvagg? I forget what time it was at before.

@gibfahn
Copy link
Member Author

gibfahn commented Sep 18, 2017

This might be early for @rvagg? I forget what time it was at before.

It's an hour earlier than it was before. Agreed that might be too early for @rvagg

@addaleax
Copy link
Member

8PM Tuesday September 19th UTC, or in your local timezone

The link there is wrong, no?

@Fishrock123
Copy link
Contributor

@addaleax appears to be, fixed it (I hope)

@mhdawson
Copy link
Member

Creating hangout since it does not look like there is one.

@mhdawson
Copy link
Member

Looks like I missed it, removing the links I added

@mhdawson
Copy link
Member

Did the meeting happen, I don't see a link to meeting minutes ?

@sam-github
Copy link
Contributor

@mhdawson check the issue history, the meeting got bumped to tomorrow, 8PM Tuesday September 19th UTC

@MylesBorins
Copy link
Contributor

MylesBorins commented Sep 18, 2017 via email

@rvagg
Copy link
Member

rvagg commented Sep 18, 2017

Shifting by a day works better for me (normal slot no longer works for me) but we're down to 6am, so I'm not going to commit but I'll try.

@mhdawson
Copy link
Member

@sam-github thanks, I caught the change in time but not the date.

@MylesBorins
Copy link
Contributor

Do we have a link for the hangout?

@sam-github
Copy link
Contributor

was just about to ask, seems not yet. @mhdawson can make one, or one of us could

@sam-github
Copy link
Contributor

I'm doing it.

@sam-github
Copy link
Contributor

https://hangouts.google.com/hangouts/_/ytl/FAKQ2SljNZeUb3zyu1Xn9fjys9nJPuijeuILWsADe1E=?eid=100598160817214911030&hl=en_US&authuser=0 <--- participants. looking for youtube link still

@abernix
Copy link

abernix commented Sep 19, 2017

https://www.youtube.com/watch?v=Y01b-pMIp8E

@sam-github
Copy link
Contributor

We often seem to go half an hour over, I wonder if we should just officially make the meeting longer when its next scheduled? Alternatively, we could try to have meetings more often. The long discussion about V8 6.1 might be considered a one-off, but unless my memory fails me, the last two meetings also went half an hour over, there always seems to be something to discuss.

gibfahn added a commit to gibfahn/Release that referenced this issue Sep 21, 2017
@gibfahn
doc: add meeting minutes for 2017-09-19
fb35293 
Fixes: nodejs#244
@gibfahn gibfahn mentioned this issue Sep 21, 2017
Merged
@gibfahn
Copy link
Member Author

gibfahn commented Sep 21, 2017

@sam-github probably worth raising a separate issue to discuss that.

@sam-github sam-github mentioned this issue Sep 21, 2017
Closed
gibfahn added a commit that referenced this issue Sep 22, 2017
@gibfahn
doc: add meeting minutes for 2017-09-19 (#248)
c7968b3 
Fixes: #244
@Fishrock123 Fishrock123 mentioned this issue Oct 9, 2017
Closed
ChALkeR pushed a commit to ChALkeR/LTS that referenced this issue Jun 30, 2018
@gibfahn @ChALkeR
doc: add meeting minutes for 2017-09-19 (nodejs#248)
b44fe62 
Fixes: nodejs#244
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lts-meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@sam-github @jasnell @rvagg @MylesBorins @abernix @addaleax @Fishrock123 @hutson @mhdawson @gibfahn