Skip to content

Commit 5c9c1f3

Browse files
authored
doc: add minutes for 2020-03-12 (#551)
Fixes: #546
1 parent fe52572 commit 5c9c1f3

1 file changed

Lines changed: 69 additions & 0 deletions

File tree

‎doc/meetings/2020-03-12.md‎

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
# Node.js Release WorkGroup Meeting 2020-03-12
2+
3+
## Links
4+
5+
* **Recording**: https://www.youtube.com/watch?v=eTMv2pQIKfU
6+
* **GitHub Issue**: https://github.com/nodejs/Release/issues/546
7+
* **Minutes Google Doc**: https://docs.google.com/document/d/1AuGvlqPg_XVihWPFOaOJKYeXD8wDZN3DKyQeYQFtY9w/edit
8+
9+
## Present
10+
11+
* Beth Griggs (@BethGriggs)
12+
* Darcy Clarke (@darcyclarke)
13+
* Michael Zasso (@targos)
14+
* Myles Borins (@mylesborins)
15+
* Richard Lau (@richardlau)
16+
* Shelley Vohr (@codebytere)
17+
18+
## Agenda
19+
20+
## Announcements
21+
22+
* Nominating Richard Lau (@richardlau) for the LTS and backporters team [#550](https://github.com/nodejs/Release/issues/550)
23+
24+
### nodejs/Release
25+
26+
* Working out a policy around reverts for LTS branches [#535](https://github.com/nodejs/Release/issues/535)
27+
* Discussed last meeting - no specific actions.
28+
* Should it be reverted on master first, and then bubble down to LTS?
29+
* Consensus was that we should decide on a case-by-case basis.
30+
* Documentation on what we should do if a release has a confirmed bug.
31+
* Potentially including raising an issue on Release repository when something goes wrong.
32+
* We should aim to revert PRs in master as soon as possible.
33+
34+
* Dropping the backporters team - [#547](https://github.com/nodejs/Release/issues/547)
35+
* Myles suggestion in [#547](https://github.com/nodejs/Release/issues/547#issuecomment-596644900)
36+
* We’re currently mixing the model of IAM and working streams.
37+
* We want to encourage more people backporting.
38+
* Should more than just releasers/backporters land on staging branches?
39+
* At the moment it’s a small group so we don’t conflict with each other when landing PRs on staging branches and backports.
40+
* Bottleneck is the time it takes for backport PRs.
41+
* Do we want the LTS team to be able to have an opinion on what should land without having access to land PRs on staging branches?
42+
* The questions we’re trying to answer are:
43+
* Who has permission to land things on the branches?
44+
* And who can participate in the discussions?
45+
46+
## Q&A, Other
47+
48+
* The definition of done is currently when a commit lands on master - maybe we should change this?
49+
* (Shelley) Checks API to show if a PR will land cleanly on LTS branches.
50+
* (Richard) Is there a risk of alienating drive-by contributors?
51+
* (Shelley) Doesn’t need to block merge.
52+
* (Myles) We could show through labels - we already use `backport-requested` labels.
53+
* (Myles) We want to avoid premature backports.
54+
* (Beth) Does this mean backports could be raised before the LTS team has audited eligibility?
55+
* (Richard) We should work on the flow.
56+
* **Action**: Raise an issue to discuss flow and/or prototype.
57+
58+
* Create an offboarding document [#542](https://github.com/nodejs/Release/issues/542)
59+
* `node-core-utils` now has an option for landing backports `git node land --backport`
60+
* Shelley is working on automating the steps involved with creating release commits in `node-core-utils`
61+
* Call for releasers to try it out and review.
62+
63+
## Upcoming Meetings
64+
65+
* **Node.js Foundation Calendar**: https://nodejs.org/calendar
66+
67+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
68+
69+

0 commit comments

Comments
 (0)