Skip to content

Commit af6b75f

Browse files
UlisesGasconruyadorno
authored andcommitted
docs: add meeting notes for 2024-07-25
1 parent d90daee commit af6b75f

File tree

1 file changed

+60
-0
lines changed

1 file changed

+60
-0
lines changed

doc/meetings/2024-07-25.md

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
# Node.js Release WorkGroup Meeting 2024-07-25
2+
3+
## Links
4+
5+
* **Recording**: https://www.youtube.com/watch?v=elnbwd3VL4c
6+
* **GitHub Issue**: https://github.com/nodejs/Release/issues/1026
7+
* **Minutes Google Doc**: https://docs.google.com/document/d/1BRJuBAZ7oTvgA9uFxKo1714Mnh6gHJGK-gpfq0dTo5s/edit
8+
9+
## Present
10+
11+
* Release team: @nodejs/release
12+
* LTS team: @nodejs/lts
13+
* Marco Ippolito @marco-ippolito
14+
* Richard Lau @richardlau
15+
* Ruy Adorno @ruyadorno
16+
* Ulises Gascón @ulisesgascon
17+
18+
19+
## Agenda
20+
21+
## Announcements
22+
23+
No announcements
24+
25+
### nodejs/Release
26+
27+
* Current status of LTS group/ backporters [#1012](https://github.com/nodejs/Release/issues/1012)
28+
* Keep backporters to allow non-releasers to prepare releases
29+
* The LTS team was created before the release WG (Historical context)
30+
* Later on the idea was to focus the team on LTS policy efforts
31+
* Note: this team does not provide you access to additional infra resources or permissions
32+
* Next action: Seems like we can remove the team, Marco will lead this.
33+
* Creating a branch rule for non LTS staging branches [#1004](https://github.com/nodejs/Release/issues/1004)
34+
* Consensus on adding backporters team to the rule and also agreement for sign commits. For reference: https://github.com/nodejs/Release/issues/1004#issuecomment-2196798542
35+
* Next step: Add a note in the issue and apply the change. Also inform the TC. (Potentially Richard can lead it in a few week’s time)
36+
* Onboarding @aduh95 as a releaser [#999](https://github.com/nodejs/Release/issues/999)
37+
* No objections from the team so far, we feel confident. Waiting for Antoine decision.
38+
* Release plan - v22.x Current [#1001](https://github.com/nodejs/Release/issues/1001)
39+
* Rafael volunteer
40+
* Release plan - v20.x Active LTS [#855](https://github.com/nodejs/Release/issues/855)
41+
* Marco can volunteer
42+
* Release plan - v18.x Maintenance LTS [#737](https://github.com/nodejs/Release/issues/737)
43+
* No rush to make a release with the current changes in staging. Probably we do a release before the end of the year.
44+
45+
### nodejs/citgm
46+
47+
* Node.js latest CITGM results [#1060](https://github.com/nodejs/citgm/issues/1060)
48+
* Discussion around potential ways to improve the current situation
49+
50+
51+
52+
53+
## Q&A, Other
54+
55+
## Upcoming Meetings
56+
57+
* **Node.js Project Calendar**: <https://nodejs.org/calendar>
58+
59+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
60+

0 commit comments

Comments
 (0)