Skip to content

Node.js Release WorkGroup Meeting 2024-11-14 #1056

Closed as not planned
Closed as not planned

Description

@mhdawson

Time

UTC Thu 14-Nov-2024 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Thu 14-Nov-2024 07:00 (07:00 AM)
US / Mountain Thu 14-Nov-2024 08:00 (08:00 AM)
US / Central Thu 14-Nov-2024 09:00 (09:00 AM)
US / Eastern Thu 14-Nov-2024 10:00 (10:00 AM)
EU / Western Thu 14-Nov-2024 15:00 (03:00 PM)
EU / Central Thu 14-Nov-2024 16:00 (04:00 PM)
EU / Eastern Thu 14-Nov-2024 17:00 (05:00 PM)
Moscow Thu 14-Nov-2024 18:00 (06:00 PM)
Chennai Thu 14-Nov-2024 20:30 (08:30 PM)
Hangzhou Thu 14-Nov-2024 23:00 (11:00 PM)
Tokyo Fri 15-Nov-2024 00:00 (12:00 AM)
Sydney Fri 15-Nov-2024 02:00 (02:00 AM)

Or in your local time:

Links

Agenda

Extracted from Release-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/Release

  • Enforce a more strict policy for semver-major releases #1054
  • Release plan - v23.x Current #1045
  • @nodejs/releasers health #1036
  • Creating a branch rule for non LTS staging branches #1004
  • Release plan - v22.x Active LTS #1001
  • Release plan - v20.x Maintenance LTS #855
  • Release plan - v18.x Maintenance LTS #737

nodejs/citgm

  • Node.js latest CITGM results #1060

Invited

  • Release team: @nodejs/release
  • LTS team: @nodejs/lts

Observers/Guests

Notes

The agenda comes from issues labelled with Release-agenda across 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

Join URL: https://zoom.us/j/157618869

Invitees

Please use the following emoji reactions in this post to indicate your
availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure

Activity

  1. self-assigned this
    on Nov 11, 2024
  2. richardlau commented on Nov 11, 2024

    @richardlau
    Member

    I'm not sure why nodejs/node#55510 wasn't picked up by the tooling.

    I won't be able to make the meeting this week, but the main point to discuss for nodejs/node#55510 is whether we should just drop the coverage threshold to allow the coverage workflows to work on v22.x-staging and v20.x-staging?

  3. RafaelGSS commented on Nov 11, 2024

    @RafaelGSS
    Member

    I'm not sure why nodejs/node#55510 wasn't picked up by the tooling.

    It might be because the label is not capitalised Release-agenda

  4. UlisesGascon commented on Nov 11, 2024

    @UlisesGascon
    Member

    I won't be bale to chair this time. Anyone is available to do it?

  5. RafaelGSS commented on Nov 11, 2024

    @RafaelGSS
    Member

    I can chair it if we have enough participants. I'll check the 👍 and 👎 in the meeting day and decide if we'll cancel

  6. RafaelGSS commented on Nov 14, 2024

    @RafaelGSS
    Member

    I got a last-minute appointment, so I won't be able to join anymore.

  7. marco-ippolito commented on Nov 14, 2024

    @marco-ippolito
    Member

    I think we can cancel

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

Metadata

Metadata

Assignees

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