We've been starting to post comments in bugs (you may have seen it!) during UX triage inquiring if bugs would be good candidates. It's especially a nice way to get some of these pesky polish bugs closed.
It would be awesome if people could help us identify what would be good first bugs as it's not clear to us the best route to get the bug fixed once we respond to our NI. Thanks! On Fri, Oct 16, 2015 at 9:42 AM, Naoki Hirata <[email protected]> wrote: > Hi all, > > 1) I would like to ask that we keep 319 MB bugs open and remove the 2.5?/+ > markers instead of just closing the bugs out. > a) the context is that it's easier to keep track of the open bugs than the > closed bugs. > b) Wilfred mentioned that they shouldn't be blocking 2.5. Having said > that, this doesn't mean that the bugs do not still exist. > c) We have had history where we went back and realized that we still have > to resolve those 319 MB issues. > d) we could always go back and close the bugs off as Won't fix when we > officially move to 512 MB. I don't see why we're busy closing these > specific bugs with a claim of we don't have the time to fix them when > there's many more that still sit in open status that are long outstanding > bugs of papercuts, backlogs, polish and more that people have decided not > to fix because they are lesser priority. > > 2) The other discussion is could developers start using "Good first bugs" > for bugs that they know are good for community members to fix up to help > improve the quality of our product? In desktop this is how it's used : > https://wiki.mozilla.org/Good_first_bug > > Thanks! > Naoki > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
