Skip to content

Commit b0488c1

Browse files
authored
Add notes from Aug WG (#137)
1 parent abd58c3 commit b0488c1

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

notes/2024/2024-08.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# GraphQL WG Notes - Aug 2024
2+
3+
**Watch the replays:**
4+
[GraphQL.js Working Group Meetings on YouTube](https://www.youtube.com/playlist?list=PLP1igyLx8foHghwopNuQM7weyP5jR147I)
5+
6+
- Intros, agreement, note taking volunteers and agenda review
7+
- Yaacov: discuss PR merge procedures
8+
- Link to PR https://github.com/graphql/graphql-js/pull/4172
9+
- Yaacov: we need flexibility in the merging policies
10+
- Yaacov: currently we need two reviews and wait two weeks so interested parties can review it
11+
- Yaacov: the rule would only be for medium-large PR’s (recommendation)
12+
- Yaacov: small changes would go along faster
13+
- Yaacov: purposefully vague about what is small-medium-large, people with merge permissions can have their own opinion.
14+
- Jovi: I think the main things that need waiting time/more reviews are spec-changes/new features
15+
- Lenz: will leave comment for getting to non-controversial wording
16+
- Yaacov: how to handle existing discrepancies between main/v17-alpha and v16
17+
- The main point coming down to, do we keep going the way we do by manually forwardporting or do we use merge commits
18+
- The clean diff for v15 vs v16 is also not there due to backporting commits going into v16
19+
- Action items
20+
- Yaacov to check whether there are any mandates from the linux foundation around merge processes
21+
- Yaacov to double check with the GraphQL JS discord

0 commit comments

Comments
 (0)