Skip to content

Release WG meeting Tuesday 19th September 2017 #244

Description

@gibfahn

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.

Activity

  1. gibfahn commented on Sep 16, 2017

    @gibfahn
    MemberAuthor

    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.

  2. MylesBorins commented on Sep 16, 2017

    @MylesBorins
    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?

  3. gibfahn commented on Sep 16, 2017

    @gibfahn
    MemberAuthor

    So 7 pm UTC? Fine by me.

  4. MylesBorins commented on Sep 16, 2017

    @MylesBorins
    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

  5. jasnell commented on Sep 16, 2017

    @jasnell
    Member

    Have a specific time in mind?

  6. MylesBorins commented on Sep 16, 2017

    @MylesBorins
    Contributor

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

  7. Fishrock123 commented on Sep 16, 2017

    @Fishrock123
    Contributor

    I should be able to make it to either

  8. gibfahn commented on Sep 16, 2017

    @gibfahn
    MemberAuthor

    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.

  9. sam-github commented on Sep 17, 2017

    @sam-github
    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.

  10. jasnell commented on Sep 17, 2017

    @jasnell
    Member

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

  11. sam-github commented on Sep 17, 2017

    @sam-github
    Contributor

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

  12. gibfahn commented on Sep 17, 2017

    @gibfahn
    MemberAuthor

    Okay, pushed earlier an hour for James.

    Is there anyone who can't make this time?

  13. hutson commented on Sep 18, 2017

    @hutson
    Contributor

    @gibfahn

    • Issue title, 18th => 19th
    • Under When, Monday => Tuesday
  14. changed the title [-]Release WG meeting 18th September 2017[/-] [+]Release WG meeting Tuesday 19th September 2017[/+] on Sep 18, 2017
  15. 10 remaining items

  16. MylesBorins commented on Sep 18, 2017

    @MylesBorins
    Contributor
  17. rvagg commented on Sep 18, 2017

    @rvagg
    Member

    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.

  18. mhdawson commented on Sep 19, 2017

    @mhdawson
    Member

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

  19. MylesBorins commented on Sep 19, 2017

    @MylesBorins
    Contributor

    Do we have a link for the hangout?

  20. sam-github commented on Sep 19, 2017

    @sam-github
    Contributor

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

  21. sam-github commented on Sep 19, 2017

    @sam-github
    Contributor

    I'm doing it.

  22. sam-github commented on Sep 19, 2017

    @sam-github
    Contributor
  23. abernix commented on Sep 19, 2017

    @abernix
  24. sam-github commented on Sep 19, 2017

    @sam-github
    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.

  25. gibfahn commented on Sep 21, 2017

    @gibfahn
    MemberAuthor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions