Skip to content

Build WG meeting 28 March 2017 - 4PM EST #660

Closed
Closed
Build WG meeting 28 March 2017 - 4PM EST#660

Description

@mhdawson
mhdawson
opened on Mar 27, 2017

When

Mar 28, 2017 4 PM EST

Where

Agenda

Extracted from wg-agenda issues and pull requests from this repo.

  • Move nodejs/readable-stream CI from Travis to Jenkins 657
  • Add Kunal Pathak to Build WG 649
  • file and directory names for downloads 515
  • Draft text for HSTS communication 484
  • TAP Plugin issues on Jenkins 453

All welcome of course, primarily @nodejs/build focused but we're happy to expand.

Activity

  1. rvagg commented on Mar 27, 2017

    @rvagg
    rvagg
    on Mar 27, 2017
    Member

    Question @ the Board for @nodejs/build: what is the level of concern re bus-factor for people and redundancy for build resources required for releases. The question is specifically around the ARM cluster and the planned outage we had there (I clarified that releases were not impacted), but from our perspective I think macOS redundancy is much more of a problem right now and the people bus-factor might be something else we should be putting our attention on.

  2. jbergstroem commented on Mar 27, 2017

    @jbergstroem
    jbergstroem
    on Mar 27, 2017
    Member

    I'd put macOS redundancy and perhaps my ability to a degree as well. I definitely haven't been as responsive and/or active this quarter as last quarter.

  3. rvagg commented on Mar 28, 2017

    @rvagg
    rvagg
    on Mar 28, 2017
    Member

    @mhdawson I don't think the 3pm one is right, that's 6am for me but I haven't ended DST yet, that'll happen next week and this slot will move to 5am, it's never been that early for me, it's always been 7am during DST and 6am during the rest of the year. I suspect that calendar entry was set to a US TZ and got shifted when the US hit DST when it should have been tied to UTC. Either way, can we do this at 4pm Eastern? Otherwise I'm won't make it.

  4. williamkapke commented on Mar 28, 2017

    @williamkapke
    williamkapke
    on Mar 28, 2017

    I added this to the calendar with EST timezone. I usually always add them as UTC but this one was - specifically stated at EST. I should have clarified. Happy to update to UTC - just LMK!

    image

    I'm confused at what time it's really happening now- the title of this issue says 4PM EST, the OP says 3PM EST.

  5. piccoloaiutante commented on Mar 28, 2017

    @piccoloaiutante
    piccoloaiutante
    on Mar 28, 2017
    Member

    I should be able to make it.

  6. mhdawson commented on Mar 28, 2017

    @mhdawson
    mhdawson
    on Mar 28, 2017
    MemberAuthor

    Ok, based on the input from @rvagg lets agree its 4pm EST.

  7. gibfahn commented on Mar 28, 2017

    @gibfahn
    gibfahn
    on Mar 28, 2017
    Member

    @williamkapke is that calendar linked from nodejs/node (or somewhere else, I haven't found the link yet)?

  8. richardlau commented on Mar 28, 2017

    @richardlau
    richardlau
    on Mar 28, 2017
    Member

    @gibfahn There's a link at the bottom of the TSC meeting minutes, e.g. https://github.com/nodejs/TSC/blob/master/meetings/2017-03-09.md

  9. williamkapke commented on Mar 28, 2017

    @williamkapke
    williamkapke
    on Mar 28, 2017

    @mhdawson I've updated it to use 8PM GMT:
    image

  10. jbergstroem commented on Mar 28, 2017

    @jbergstroem
    jbergstroem
    on Mar 28, 2017
    Member

    Sorry for my late notice but I won't be able to join. My efforts since last time:

    • jenkins master security updates, twice
    • play around with the tap2junit parser -- it will bail on citgm stuff; needs to be refactored
    • fix disk issues on joyent freebsd workers which seems to have changed how disk is mounted which led to disk issues.
    • housekeeping on a few workers

    ..as for my input:

    • I'd like to bring up MacOS workers for discussion. We had an interesting opportunity which led into this and back to sleep. After we've sorted that we can revisit the opportunity and increase both redundancy and os versions tested.
    • Bus factor: I like Michaels idea of primary/backup for positions. Which would these positions be though? My ambition is that everybody in the build group would help out with the level of access they have -- meaning all of our members should feel free to look at restarting/debugging individual workers. As for the higher tiers; we need to start by defining these positions.
    • Adding Kunal: SGTM 👍
    • I believe we were to remove the agenda label from a few of the raised topics as a result of previous meeting. Not sure that happened.

  11. mhdawson commented on Mar 28, 2017

    @mhdawson
    mhdawson
    on Mar 28, 2017
    MemberAuthor

    Link for participants: https://hangouts.google.com/hangouts/_/ytl/KOIfKbVSfs8CMc3OB3XsoxoKlDtgpIGkbsfAvJbRIe8=?eid=100598160817214911030&hl=en_US&authuser=0

  12. williamkapke commented on Mar 28, 2017

    @williamkapke
    williamkapke
    on Mar 28, 2017

    I asked a question in IRC

  13. gibfahn commented on Mar 29, 2017

    @gibfahn
    gibfahn
    on Mar 29, 2017
    Member

    Minutes here: #665

  14. gibfahn commented on Mar 31, 2017

    @gibfahn
    gibfahn
    on Mar 31, 2017
    Member

    Minutes landed, closing.

  15. gibfahn
    closed this as completedon Mar 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions