Compatibility/Meetings/Sync w Honza: Difference between revisions
OanaArbuzov (talk | contribs) m (OanaArbuzov moved page Talk:Compatibility/Meetings/Sync w Honza to Compatibility/Meetings/Sync w Honza: Main meeting.) |
OanaArbuzov (talk | contribs) (Added meeting minutes from 14.06.2022) |
||
| Line 1: | Line 1: | ||
== June 14 2022 == | |||
=== Firefox Release vs Firefox Nightly reproducibility (SV) === | |||
Currently, issues that are reproducible on Release but they are not reproducible on Nightly, we close them as Won't fix, with the message for the user to test on the next release. | |||
We previously agree to this approach with Karl. Should we continue doing so? | |||
honza: we can keep this approach | |||
=== [FYI] Bug reported QA flow (SV) === | |||
We've created a chart and some guidelines on the work performed by SV QA team after a bug is reported on webcompat.com platform. | |||
Chart with the QA flow: https://drive.google.com/file/d/16Y3XwBIZArdySUvZAzcql8AiHetu5Sql/view?usp=sharing | |||
Guidelines - flow explained: https://docs.google.com/document/d/190-mh_vNzrso2RaEQ5OULii-YsN3d5sUt8AZVSOUH5A/edit?usp=sharing | |||
honza: can this be shared with Webcompat team? | |||
oana: yes, I've created a copy for the team using a Mozilla account, everyone should have now access to view and comment | |||
=== [Honza] WebCompat Repos === | |||
What is the relation and how the process looks like? | |||
* [webcompat/web-bugs](https://github.com/webcompat/web-bugs) | |||
* [webcompat/web-bugs-private](https://github.com/webcompat/web-bugs-private) | |||
honza: we discussed it, all good | |||
=== Fast Response Triage details (SV) === | |||
Are there any updates on this topic? | |||
honza: things are moving, work in progress, I'll keep you updated | |||
paul: this will be helpful since all the team members are working on it | |||
== May 31 2022 == | == May 31 2022 == | ||
Revision as of 08:42, 17 June 2022
June 14 2022
Firefox Release vs Firefox Nightly reproducibility (SV)
Currently, issues that are reproducible on Release but they are not reproducible on Nightly, we close them as Won't fix, with the message for the user to test on the next release.
We previously agree to this approach with Karl. Should we continue doing so?
honza: we can keep this approach
[FYI] Bug reported QA flow (SV)
We've created a chart and some guidelines on the work performed by SV QA team after a bug is reported on webcompat.com platform.
Chart with the QA flow: https://drive.google.com/file/d/16Y3XwBIZArdySUvZAzcql8AiHetu5Sql/view?usp=sharing Guidelines - flow explained: https://docs.google.com/document/d/190-mh_vNzrso2RaEQ5OULii-YsN3d5sUt8AZVSOUH5A/edit?usp=sharing
honza: can this be shared with Webcompat team?
oana: yes, I've created a copy for the team using a Mozilla account, everyone should have now access to view and comment
[Honza] WebCompat Repos
What is the relation and how the process looks like?
- [webcompat/web-bugs](https://github.com/webcompat/web-bugs)
- [webcompat/web-bugs-private](https://github.com/webcompat/web-bugs-private)
honza: we discussed it, all good
Fast Response Triage details (SV)
Are there any updates on this topic?
honza: things are moving, work in progress, I'll keep you updated
paul: this will be helpful since all the team members are working on it
May 31 2022
Welcome Honza
Introduction to webcompat. QA tasks.