-
-
Notifications
You must be signed in to change notification settings - Fork 30
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.
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
Weekly Triage meetings: Jan-Jun 2023 #169
Comments
January 12, 2023
Before the meeting, 16 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 5 issues in Jupyter Notebook needed triage. After the meeting, 4 remain.
We did not triage JupyterLab Desktop issues today. |
January 19, 2023
Before the meeting, 14 issues in JupyterLab needed triage. After the meeting, 2 remain.
Before the meeting, 6 issues in Jupyter Notebook needed triage. After the meeting, 3 remain.
We did not triage JupyterLab Desktop issues today. |
January 26, 2023
Before the meeting, 10 issues in JupyterLab needed triage. After the meeting, 3 remain.
Before the meeting, 4 issues in Jupyter Notebook needed triage. After the meeting, one remains.
Before the meeting, 1 issue in JupyterLab Desktop needed triage. After the meeting, none remains. |
February 2, 2023
Before the meeting, 10 issues in JupyterLab needed triage. After the meeting, 2 remain.
Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, 2 remain.
Before the meeting, 4 issues in JupyterLab Desktop needed triage. After the meeting, 1 remains.
|
February 9, 2023
Before the meeting, 14 issues in JupyterLab needed triage. After the meeting, 5 remain.
Before the meeting, 7 issues in Jupyter Notebook needed triage. After the meeting, 3 remain.
No issues in JupyterLab Desktop needed triage. |
February 16, 2023
Before the meeting, 18 issues in JupyterLab needed triage. After the meeting, 5 remain.
Before the meeting, 5 issues in Jupyter Notebook needed triage. After the meeting, none remain.
Before the meeting, 9 issues in JupyterLab Desktop needed triage. After the meeting, 1 remains.
|
February 23, 2023
Before the meeting, 8 issues in JupyterLab needed triage. After the meeting, 4 remain.
No issues in Jupyter Notebook needed triage. Before the meeting, 6 issues in JupyterLab Desktop needed triage. After the meeting, 3 remain.
|
March 2, 2023
Before the meeting, 16 issues in JupyterLab needed triage. After the meeting, 2 remain.
Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, none remain.
Before the meeting, 8 issues in JupyterLab Desktop needed triage. After the meeting, 5 remain.
|
March 9, 2023
Before the meeting, 9 issues in JupyterLab needed triage. After the meeting, 2 remain.
Before the meeting, 1 issue in Jupyter Notebook needed triage. After the meeting, none remain. Before the meeting, 9 issues in JupyterLab Desktop needed triage. After the meeting, 5 remain.
|
As discussed earlier today, there will be no triage next week. Starting on March 21, 2023, triage moves to Tuesdays at 09:00 PDT (16:00 UTC). See you then! |
March 21, 2023
Before the meeting, 24 issues in JupyterLab needed triage. After the meeting, 6 remain.
Jupyter Notebook issues were not triaged this meeting. JupyterLab Desktop issues were not triaged this meeting. |
March 28, 2023
Before the meeting, 23 issues in JupyterLab needed triage. After the meeting, 5 remain.
Before the meeting, 16 issues in Notebook needed triage. After the meeting, 3 remain.
JupyterLab Desktop issues were not triaged this meeting. |
April 4, 2023
Before the meeting, 19 issues in JupyterLab needed triage. After the meeting, 3 remain.
Before the meeting, 5 issues in Notebook needed triage. After the meeting, 3 remain.
Before the meeting, 19 issues in JupyterLab Desktop needed triage. After the meeting, 7 remain.
|
April 11, 2023
Before the meeting, 21 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 6 issues in Notebook needed triage. After the meeting, 1 remains.
Before the meeting, 12 issues in JupyterLab Desktop needed triage. After the meeting, 5 remain.
|
April 18, 2023
Before the meeting, 20 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 1 issue in Notebook needed triage. After the meeting, 1 remains.
Before the meeting, 6 issues in JupyterLab Desktop needed triage. After the meeting, 4 remain.
|
April 25, 2023
Before the meeting, 13 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 5 issues in Notebook needed triage. After the meeting, 2 remain.
Before the meeting, 6 issues in JupyterLab Desktop needed triage. After the meeting, 4 remain.
|
May 2, 2023
Before the meeting, 19 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 3 issues in Notebook needed triage. After the meeting, 1 remains.
Before the meeting, 5 issues in JupyterLab Desktop needed triage. After the meeting, 2 remain.
|
May 16, 2023
Before the meeting, 16 issues in JupyterLab needed triage. After the meeting, 5 remain.
Before the meeting, 6 issues in Notebook needed triage. After the meeting, 4 remain.
Before the meeting, 5 issues in JupyterLab Desktop needed triage. After the meeting, 2 remain.
|
May 30, 2023
Before the meeting, 14 issues in JupyterLab needed triage. After the meeting, 3 remain.
Before the meeting, 7 issues in Notebook needed triage. After the meeting, 4 remain.
No issues in JupyterLab Desktop needed triage. Notebook 7.0 bugs triage during May 30 call to identify release blockers: |
June 6, 2023
Before the meeting, 13 issues in JupyterLab needed triage. After the meeting, 3 remain.
Before the meeting, 7 issues in Notebook needed triage. After the meeting, 2 remain.
Before the meeting, 2 issues in JupyterLab Desktop needed triage. After the meeting, 2 remain. |
June 13, 2023
Before the meeting, 10 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 7 issues in Notebook needed triage. After the meeting, 5 remain. We also discussed jupyter/notebook#6800, which was not in need of triage, but which may result in additional issues created for individual tasks within it.
Before the meeting, 5 issues in JupyterLab Desktop needed triage. After the meeting, 1 remains.
|
June 20, 2023
Before the meeting, 19 issues in JupyterLab needed triage. After the meeting, 2 remain.
Before the meeting, 6 issues in Notebook needed triage. After the meeting, 2 remain.
Before the meeting, 2 issues in JupyterLab Desktop needed triage. After the meeting, none remain. |
June 27, 2023
Before the meeting, 11 issues in JupyterLab needed triage. After the meeting, 2 remain.
Before the meeting, 10 issues in Notebook needed triage. After the meeting, 1 remains.
No issues in JupyterLab Desktop needed triage. |
Jupyter Issue Triaging
Triage issues in JupyterLab and corresponding projects.
Meeting is typically held at 10:00 US Pacific time on Thursdays.
Meeting info: https://zoom.us/my/jovyan?pwd=c0JZTHlNdS9Sek9vdzR3aTJ4SzFTQT09
HackMD: https://hackmd.io/HaQ3S_nPSbqaRtk9rj59iA
Previous notes:
Goals
Act on long-running, highly demanded, or highly discussed issues to get them ready for development work.
Resources
https://jupyterlab.readthedocs.io/en/latest/developer/contributing.html#submitting-a-pull-request-contribution
Triage Process
All requested information, where applicable, is provided. From the templates in JupyterLab’s issues:
For a bug:
For a feature request:
The issue should represent real, relevant, feasible work. In short, if a knowledgeable person were to be assigned this issue, they would be able to complete it with a reasonable amount of effort and assistance, and it furthers the goals of the Jupyter project.
a. good first issue
b. bug
c. feature parity
d. Tag milestones
Add milestone if you can achieve the goal.
Meetings
Primary focus:
Additional areas:
The text was updated successfully, but these errors were encountered: