Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 2023-01-09.md #561

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update 2023-01-09.md #561

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions learning-team/2023/2023-01-09.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -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.

Expand All @@ -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.