Skip to content

Commit 6060db2

Browse files
committed
doc: add minutes for meeting 2022-04-14
Closes: nodejs#735
1 parent de90067 commit 6060db2

File tree

1 file changed

+47
-0
lines changed

1 file changed

+47
-0
lines changed

doc/meetings/2022-04-14.md

+47
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
# Node.js Release WorkGroup Meeting 2022-04-07
2+
3+
## Links
4+
5+
* **Recording**: https://www.youtube.com/watch?v=Y_1tB3YRG2A
6+
* **GitHub Issue**: https://github.com/nodejs/Release/issues/735
7+
8+
## Present
9+
10+
* Beth Griggs (@BethGriggs)
11+
* Bryan English (@bengl)
12+
* Danielle Adams (@danielleadams)
13+
* Juan Arboleda (@soyjuanarbol)
14+
* Richard Lau (@richardlau)
15+
16+
## Agenda
17+
18+
## Announcements
19+
20+
* Node.js 18 is due to be released on the 19th April.
21+
* Latest release candidate is available - https://nodejs.org/download/rc/v18.0.0-rc.3/.
22+
23+
### nodejs/Release
24+
25+
* Process for unintentional breaking changes [#728](https://github.com/nodejs/Release/issues/728)
26+
* The specific issue/PR that raised this has been addressed.
27+
* Some process documentation would be helpful.
28+
* Let’s untag from the agenda and add a comment stating our intent to create some guidance.
29+
* Create a guide on ‘What to do when a release is broken? [#558](https://github.com/nodejs/Release/issues/558)
30+
* Should form part of the same release guide.
31+
* Working out a policy around reverts for LTS branches [#535](https://github.com/nodejs/Release/issues/535)
32+
* Should form part of the same release guide.
33+
* Proposal to rename CITGM team to `release-automation` [#557](https://github.com/nodejs/Release/issues/557)
34+
* Plan was to grant releasers access to the automation repositories.
35+
* (Action) To confirm whether the access has been added.
36+
* Bryan worked on a fix for `branch-diff` - it would be good for us to have access to be able to merge it.
37+
* Release plan - v18.x Current [#737](https://github.com/nodejs/Release/issues/737)
38+
* Node.js 18 release plan issue has been following our typical schedule for current releases.
39+
* Release plan - v17.x Current [#703](https://github.com/nodejs/Release/issues/703)
40+
* No future releases planned - let’s close the issue.
41+
* Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658)
42+
* Danielle has been working on the semver minor release.
43+
* Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567)
44+
* Juan volunteered to do the next patch release.
45+
* Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494)
46+
* Issue closed as no further planned releases.
47+

0 commit comments

Comments
 (0)