Hi Lucas, Good to know that! I was about to pick something with the polish label.
Thanks! On Wednesday, April 10, 2013, Lucas Adamski wrote: > Hi Henrique, > > I would recommend starting with the UX-most-wanted link at the bottom of > my email > (https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ux-most-wanted). > Thanks for contributing! > Lucas. > > On 4/9/2013 3:24 PM, Henrique Alves wrote: > > Hi Lucas, > > > > Talking about priorities. I just joined the community and I am trying to > figure out something to pick up. I was looking around on Bugzilla > (Gaia:polish). It seems a couple of them are marked as new but on GitHub > were already closed. Also it's really hard to define the priorities. Can > you give me a light please? > > > > Thanks, > > > > On Tuesday, 9 April 2013 02:22:21 UTC+1, Lucas Adamski wrote: > >> = 1.1/LEO priorities = > >> > >> > >> > >> There are three kinds of bugs on the LEO+ list: > >> > >> > >> > >> 1) Uncompleted features - those are #1 priority for LEO > >> > >> 2) Bugs that block partner milestones. The current big one is partner > CS, and those bugs are being tracked under "Blocking partner CS" here: > https://wiki.mozilla.org/B2G/Triage#1.1.0_.28Leo.29 > >> > >> 3) Bugs that Mozilla has marked as LEO+ because we believe they must be > fixed before we ship. These do not have an explicit deadline yet, but we > should expect that partners will also consider many of these to be blocking > their milestones and as such we should knock these down ASAP. > >> > >> > >> > >> = Overall priorities = > >> > >> 1.1 aside, we are NOT done with 1.0.1! The sooner we wrap up 1.0.1, > the sooner we can focus 100% on 1.1! > >> > >> > >> > >> General engineering priorities are: > >> > >> a) reviews for TEF+ bugs > >> > >> b) patches for TEF+ bugs > >> > >> c) reviews and patches for LEO+ features > >> > >> d) reviews and patches for LEO+ CS and other certification bugs > >> > >> e) reviews and patches for other LEO+ bugs > >> > >> g) tracking-b2g18+ and UX most wanted: > https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ux-most-wanted > >> > >> h) I doubt you'll get this far? > >> > >> > >> > >> If you aren't working on a) though g), please consider whether you are > using your time as wisely as you could. There is almost certainly > something on https://wiki.mozilla.org/B2G/Triage that you can help with. > >> > >> > >> > >> = Landing patches = > >> > >> - If you need to land something for 1.0.1, it needs to be marked TEF+. > Only our partners can set that now past CC. > >> > >> - If you need to land something for 1.1, it needs to be either LEO+ or > you need to ask for patch approval. Approval requests do NOT require > tracking-b2g18+. If you feel like your approval requests are not being > addressed in a timely manner, please reach out the Alex Keybl. We are still > handling blocking and landing approvals, and unlike 1.0.1 Mozilla will > continue to do so for non CS blocking bugs at least until the end of CS. > >> > >> Details: https://wiki.mozilla.org/Release_Management/B2G_Landing > >> > >> > >> > >> = Milestones = > >> > >> An important note on work, life and milestones: milestones are > thresholds that determine the schedule for us and our partners, but the > dates can change as our understanding of market needs and product readiness > evolves. Missing a milestone should be considered a schedule-impactful > event. Scope changes in turn should impact milestones, which impact > schedules. > >> > >> > >> > >> Hitting a milestones unfortunately does not imply an immediate > reduction in our workload. Please pick a cadence that you can maintain and > don't kill yourself trying to hit a milestone, as you will immediately face > another (if slightly different) climb. Estimate how long you think things > will really take, and please provide those your manager to ensure we are > estimating work with the human factors included, vs. per some sort of > idealized "work-week output". > >> > >> > >> > >> = Summary of useful links = > >> > >> Links to things to work on: https://wiki.mozilla.org/B2G/Triage > >> > >> Landing criteria: > https://wiki.mozilla.org/Release_Management/B2G_Landing > >> > >> Perf graphs: https://datazilla.mozilla.org/b2g/ > >> > >> - TEF+ bugs: http://bit.ly/16JZ6rQ > >> > >> - LEO+ CS bugs: http://bit.ly/10MBelE > >> > >> - LEO+ bugs: http://mzl.la/100cFkt > >> > >> UX most wanted: > https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ux-most-wanted > > _______________________________________________ > > dev-gaia mailing list > > [email protected] <javascript:;> > > https://lists.mozilla.org/listinfo/dev-gaia > > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
