nodejs / nodejs/build

Node.js Build WorkGroup Meeting 2025-01-01

Open
#3,992 0 comments 2 reactions 1 assignee View on GitHub

@mhdawson is already working on this.

Since Dec 30, 2024.

Dominant language
Jinja
Stars
541
Forks
185
Avg merge
22h 15m
Merged PRs (30d)
4

Description

Time

UTC Wed 01-Jan-2025 14:00 (02:00 PM):

Timezone Date/Time
US / Pacific Wed 01-Jan-2025 06:00 (06:00 AM)
US / Mountain Wed 01-Jan-2025 07:00 (07:00 AM)
US / Central Wed 01-Jan-2025 08:00 (08:00 AM)
US / Eastern Wed 01-Jan-2025 09:00 (09:00 AM)
EU / Western Wed 01-Jan-2025 14:00 (02:00 PM)
EU / Central Wed 01-Jan-2025 15:00 (03:00 PM)
EU / Eastern Wed 01-Jan-2025 16:00 (04:00 PM)
Moscow Wed 01-Jan-2025 17:00 (05:00 PM)
Chennai Wed 01-Jan-2025 19:30 (07:30 PM)
Hangzhou Wed 01-Jan-2025 22:00 (10:00 PM)
Tokyo Wed 01-Jan-2025 23:00 (11:00 PM)
Sydney Thu 02-Jan-2025 01:00 (01:00 AM)

Or in your local time:

Links

Agenda

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

nodejs/build
  • Equinix Metal sunset, June 2026 #3975
  • Jenkins LTS will drop support for Java 11 in October #3916
  • Infrastructure for Orka (2024 and beyond) #3686
  • New Machine requirement: Replacement for Equinix x64 servers #3597
  • macOS refuses to start node when downloaded from the tarball #3538
  • Discuss state of r2 migration on Build WG meeting #3508
nodejs/node
  • deps: update simdjson to 3.11.3 #56250
  • [do not land] update ada to v3.0-pre #56218

Invited

  • Build team: @nodejs/build
Observers/Guests

Notes

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


Invitees

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

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.