|
Summary: as I mentioned on the a11y meetings, one option to replace
the feature proposal is to create a list of target bugs to get
solved by 3.16. Is similar to the blocker list, but with "good to
have" and defined at the beginning of the cycle. We made something similar on previous meetings. I think that it would be good to "sync" with this proposal. I will add a topic to discuss about that on next meeting. BR -------- Forwarded Message --------
Hi all, I've been busy putting together a list of target bugs for 3.16. You can see them here: https://bugzilla.gnome.org/buglist.cgi?cf_gnome_target=3.16;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;bug_status=NEEDINFO Keeping the list to a manageable size is an obvious challenge, so I've been focusing on a subset of bugs for this initial round. This includes: * The most serious/visible bugs - those bugs that really irritate and/or detract from the overall experience in a significant way. * Basic content presentation - making sure that lists and grids of content items look nice, and are loaded smoothly and neatly. * Out of the box experience - so that we make a good first impression. So far there are around 20 bugs. Let me know if you think that number is about right. We could always add more (I have a wiki page with some candidates [1]). Please take a moment to look over the list, and add any bugs that you think should be on there. I'll share the list with d-d-l once the Release Team is happy with it. Allan [1] https://wiki.gnome.org/AllanDay/ThreePointSixteenTargetBugs _______________________________________________ release-team gnome org https://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions. |