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

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

Closed
mhdawson opened this issue Mar 27, 2017 · 14 comments
Closed

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

mhdawson opened this issue Mar 27, 2017 · 14 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented 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.

@rvagg
Copy link
Member

rvagg commented Mar 27, 2017

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.

@jbergstroem
Copy link
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.

@rvagg
Copy link
Member

rvagg commented Mar 28, 2017

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

@williamkapke
Copy link

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.

@piccoloaiutante
Copy link
Member

I should be able to make it.

@mhdawson
Copy link
Member Author

mhdawson commented Mar 28, 2017

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

@gibfahn
Copy link
Member

gibfahn commented Mar 28, 2017

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

@richardlau
Copy link
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

@jbergstroem
Copy link
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.

@mhdawson
Copy link
Member Author

@williamkapke
Copy link

I asked a question in IRC

@gibfahn
Copy link
Member

gibfahn commented Mar 29, 2017

Minutes here: #665

@gibfahn
Copy link
Member

gibfahn commented Mar 31, 2017

Minutes landed, closing.

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