Compatibility/Meetings/Sync w Honza: Difference between revisions

meeting minutes july
(meeting minutes june)
(meeting minutes july)
Line 1: Line 1:
== July 11 2023 ==
=== Low number of opened issues for this Monday (SV) ===
We have seen a significantly low number of new issues this Monday, at least 50 issues below the average, since the dual form is deployed from this Wednesday for webcompat.com. When can we expect to triage them?
Honza: Yeah, most users reported the bugs with the simplified form which end up in our database for now.
The next steps is to provide a spread sheet for you to look over it. There might be an option to sort reports based if they have a description or not. Dennis might come up with something quickly.
If it turns out it needs more time, we might rollback the change on webcompat.com. We will see. From your side, any feedback related to the process is welcomed, how we can improve the process.
=== Expected high numbers of incomplete issues with the new report form (SV) ===
With the new report form, we may end up with a high number of incomplete issues. We are thinking to reduce the time frame for replies for which we are closing issues as incomplete, from 10 days (12 days for users reply) since our last comment on the issue, to 5 days (7 days for users reply).
Should we keep the same approach we used for our current triage process, where we can not extract any relevant details for incomplete issues, or should we try and dig deeper than usual?
Honza: We are looking to sort the newly received issues and to sort them.
Paul: For the new received reports, we might end up with them piling up in our repository at the end of the week (opened issues waiting for info).
Honza: I think the goal won't be to go over everything, it will be some grouping for the same domain. And we will prioritize where's the most info provided. It all depends on how it will go.
Paul: That's why we were asking, we are hoping towards a more simplified process of triaging issues from the QA point of view.
Honza: Hopefully we will have the spreadsheet soon.
=== New simplified report form - Operating System detection (SV) ===
Since the form is simplified how will we figure out on which operating system the issue happens? Will it be autodetected  and included in the bug report once it is submitted?
Honza: Yes, I think it is included by looking at the patch on: https://bugzilla.mozilla.org/show_bug.cgi?id=1833916
Honza: The report will include also the prefs.
Paul: We had something similar in Bugzilla, where data is extracted regarding user ID and Operating System.
Paul: Our concern was to see the exact Operating System where the issue is reproducible, and not the info about the Operating System is reported.
Honza: I see, that is a good point, I'll raise this concern.
Raul: Wouldn't it be better to include an optional screenshot field too? If we end up doing manual triage on the issues comming from simplified form, usually the screenshot is an important part in figuring out the issue.
Paul: As optional, it would be useful to have the Screenshot part at the beginning of the report, not at the end of the report, like we currently have.
Honza: There is an ongoing project where this option might be added in the new reporting tool in the Firefox Browser. The simplified report is to start building data for building the new reporting tool in Firefox.
=== Smoke testing for webcompat.com (SV) ===
With the new updated form, should we perform a smoke test on webcompat.com once all the data needed is extracted and the final conclusions are made?
Honza: Good point. The only question now is to see if we roll back or not. Once we have everything we need, that would be great.
Paul: What would cause a rollback?
Honza: That's only if Dennis needs more time in order to put it in place (eg. like 2 weeks).
Paul: So the simplified version is here to stay but the rollback is to give time to the dev team to finalize the form.
== June 27 2023 ==
== June 27 2023 ==


14

edits