Hey Aaron, ----- Original Message ----- > How frequent during this cycle will you be triaging associated all > dependencies off of new-about-home?
I'm keeping an eye on the dependencies every day. But our triage meeting is probably going to be where we'll actually do it. > Shall we continue to nominate via tracking-fennec or via a whiteboard tag? Let's use our usual process for nominating via tracking-fennec and make all fig-related bugs block the meta bug 862793. For instance, I've just nominated all P1 bugs we had in fig. We can discuss them in the triage meeting. > What are your criteria for prioritization for regressions here? For example, > what are you deeming a P1? (you already have classified a few) My approach for picking P1 bugs so far has been: - The automated tests that we've disabled because of the new UI. - Core parts of the UX that are missing e.g. certain animations, UI elements, etc. - Major regressions, crashes, clearly broken behaviour, etc. With that said, I was only using "P1" as an easy way to keep track of the important issues in fig. From now on though, I think we can simply keep an eye on the bugs marked as tracking 26. So, if you feel something is a "P1" bug, simply nominate it for tracking and we can decide about its importance during the triage meeting. --lucasr _______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
