Node.js Technical Steering Committee (TSC) Meeting 2020-10-01 #933
Comments
|
Please read the conversation at nodejs/node#35250 and comment there. It would be great if we had informed TSC opinions on it ahead of the meeting. I know it's unrealistic to expect everyone to arrive having considered the issue, but if a critical mass could, it would help us avoid the stalling-PR issue here. |
|
Moderation team update: Blocked a user and deleted an issue. Details in https://github.com/nodejs/moderation/issues/347#issuecomment-699651964. @nodejs/moderation @nodejs/tsc @nodejs/community-committee |
|
Can we invite @bcoe as a guest to provide context for nodejs/node#35250 and answer questions that may come up? (@mhdawson Are you able to send a calendar invite?) |
|
Not a calendar invite but I can send the details to @bcoe |
|
Details/password sent to @bcoe |
|
I have a conflicting meeting, might join late. |
|
We can remove #33416 from the agenda |
|
@MylesBorins done. |
|
Hey all, I have an internal planning meeting that will cause me to be ~30 minutes lates. My sincere apologies. The npm team is in the process of doing the finishing touches on npm v7.0.0-rc.0 and I am expecting a PR to open against Node.js in the next hour or so. I would to have some time in this call to discuss the release get TSC approval to land 7.0.0 in node.js 15.x. This will be a Semver-Major change after the cutoff deadline. We currently have a targeted release date of Oct 13th to cut v7.0.0, and plan to cut rc's in between to fix bugs as they are identified. If the agenda is light and you get to this before the 30 minute mark please ping me and I'll drop from the planning call (twitter dm likely the fastest) |
In case I'm late or miss the meeting: I am supportive of including npm 7 in 15.x. I'm going to point out, because we so often forget, that the decision of what to include in a release is up to the Release WG and not the TSC. That said, it's probably good to on record as not opposing this, since the Release WG has always deferred to TSC on that. |
|
@Trott I was under the impression that TSC approval for Semver Major after cutoff was to the TSC. I'd personally be ok with us deferring to release for that. I am not finding any documented policy around this though. |
|
My understanding was that in this case it was the TSC who approved Semver Major's after the cutoff as well. |
It's briefly documented in https://github.com/nodejs/node/blob/master/doc/guides/releases.md#release-branch. It's not TSC approval -- it's no objections.
|
|
@richardlau thanks for finding the wording, it's what I think makes sense. The TSC should be aware, and not have any concerns/objections. |
|
Thanks @richardlau! Was looking in the wrong repo. That being documented in the release repo seems like the appropriate place. |
|
Startup performance update: creating the startup team in nodejs/node#35406, looking into mksnapshot error in v8 canary debug build nodejs/node-v8#175 (might be an upstream issue) I won't be able to join the meeting today |
|
@richardlau @mhdawson @MylesBorins Right, but the decision to make it require no objections from TSC is a Release WG decision. Oooofff. My head hurts. OK, joining the meeting now. |
|
PR for minutes: #934 |
Time
UTC Thu 01-Oct-2020 15:00 (03:00 PM):
Or in your local time:
Links
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
nodejs/admin
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
tsc-agendaacross all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
Zoom link: https://zoom.us/j/611357642
Regular password
Public participation
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: