ma 14. syysk. 2020 klo 23.49 Tyler Cipriani (tcipriani@wikimedia.org) kirjoitti:
The number of new tasks being created with this tag in a given week is outpacing the number of tasks being closed in a given week: this past week we added 41 tasks and only closed 22.
Majority of the recently created tasks are frontend JavaScript errors. The logging of these errors have only started recently. These issues may have been present for years already, but they are reported now.
This is beginning to be unsustainable :(
If there is an increase in the amount of real new issues and/or decrease in the amount of issues fixed, then I would be worried. Given what I said above, it's difficult to see if this is the case.
Regardless, I do agree that we should aim to minimize production errors to make it easier to spot any new issues. I would encourage all maintainers and development teams to ensure that they have a regular process to check if they have and triage any production issues in code they maintain.
I think we should expect the number to go up while the backlog of unreported frontend errors are being reported, and then it would start going down as developers work on to reduce the backlog of reported issues. It will probably stabilize at some level, higher than previously, indicating that some areas of code lack maintainers or maintenance resources.
Ending with a question: do we want to have both frontend and backend errors on the same tag/board, or should they be on separate ones?
-Niklas