From eeb513a684b2426db2ef9297df49fc3540fe4d7a Mon Sep 17 00:00:00 2001 From: "Tataw. Clarkson" <127490325+tataw-cl@users.noreply.github.com> Date: Tue, 5 Dec 2023 21:23:43 +0100 Subject: [PATCH] Update 2023-01-09.md Just corrected some typos and simplified the grammatical meaning of some sentences --- learning-team/2023/2023-01-09.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/learning-team/2023/2023-01-09.md b/learning-team/2023/2023-01-09.md index a234f9fe..7facee16 100644 --- a/learning-team/2023/2023-01-09.md +++ b/learning-team/2023/2023-01-09.md @@ -18,7 +18,7 @@ Add yourself to the list if you attend and check the box! ### Guests -- [] Your name here (INITIALS) +- [ ] Your name here (INITIALS) ## Weekly review @@ -38,16 +38,16 @@ We've not discussed who does it, and we don't know if RM is available to help. J AG will do the release, JG will share the experience. JG suggests to make the release process more collaborative (how to do it now), especially when debugging problems/fixing things locally. AG will make sure to sync information back to the group/documentation. -JW mostly the API docs are a problem, and sometimes the search index. With RM not around as much, and the release-tool needs some maintainance, so we might want to look into running the individual scripts. +JW mostly the API docs are a problem, and sometimes the search index. With RM not around as much, and the release-tool needs some maintenance, so we might want to look into running the individual scripts. Call scheduled 12:30 EST to do the release together. ### Deprecations -JW has been going to the framework meetings and the topic about deprecations, mismatched between deprecations and source, and missing guides. Katie is going through it. If you see deprecation-PR pop up review it and merge it if it looks okay. +JW has been going to the framework meetings and the topic about deprecations, there is a mismatch between deprecations and the source, and some guides are missing. Katie is going through it. If you see deprecation-PR pop up review it and merge it if it looks okay. PRs need to be approved and checked for the version and if the deprecation actually landed in the version before we merge them. -The versions being in URLs for the deprecations made it confusing in the guides. JW did not really understand it, we might need some more clarification. +The versions being in URLs for the deprecations made it confusing in the guides. JW did not really understand it, we might need further clarification. Framework team wants to put all the deprecation documentation in the codebase and have us pull it from there. Something for our long term ideas. @@ -60,4 +60,4 @@ Add writeup ideas / call for contributors / suggestions to [the latest PR](https ## Any Questions? -Questions, comments or concerns? Submit a comment or PR for this set of notes. +Questions, comments or concerns? Submit a comment or a PR for these notes.