TPEGFX/2015-01-22: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 35: Line 35:


===Morris Tseng===
===Morris Tseng===
* {{Bug|1121353}} - The touch event which is fired by TabParent::InjectTouchEvent does not go through APZC.
** r?


* {{Bug|1120750}} - [Text Selection]Send out caret's position for the short cut mode
** WIP
* {{Bug|1120746}} - text_selection_test.js always failed when running gaia integration test on device.
** land


===Tingyu Lin===
===Tingyu Lin===

Revision as of 02:20, 22 January 2015

Weekly Report

Boris Chiou

Bug 1120781 - [LayerScope] Layerscope can't dump the buffer content for bidi text reftest page

Chiajung Hung

Ethan Lin

  • bug 753010 - Add a NEON optimized blur method
    • r+
  • bug 1121869 - [flatfish] build break by "Error: bad type in Neon instruction"
    • land
  • edit-mode performance
    • study
  • fence transport
    • study

Jeremy Chen

  • bug 1110917 - [Text Selection] [Email] CCP menu does not display when selecting text in the body of an email while focus is on another field
    • land
    • Wait for being uplifted to b2g37 (approval-mozilla-b2g37?)
  • bug 1120358 - [Text Selection] Selection carets does not update its position when selecting text in an unfocused content editable area
    • r+
    • Work on test case
  • Setup development environment
    • B2G desktop client , Gaia Integration tests, WebIDE

Jerry Shih

  • bug 1092978 - Integrate refresh driver
    • landed
  • bug 1123734 - Notify global VsyncSource in hwc
    • landed
  • bug 1123762 - [META] Turn on vsync-aligned refresh driver by default on b2g

Morris Tseng

  • bug 1121353 - The touch event which is fired by TabParent::InjectTouchEvent does not go through APZC.
    • r?
  • bug 1120750 - [Text Selection]Send out caret's position for the short cut mode
    • WIP
  • bug 1120746 - text_selection_test.js always failed when running gaia integration test on device.
    • land

Tingyu Lin

Peter Chang

Rule of Thumb

Status code:

  • OOAD: In analysis or design phase.
  • WIP: working on WIP patch.
  • feedback(f): feedback a patch
  • feedback?(f?): WIP is ready for feedback grant.
  • feedback+(f+): Get positive feedback.
  • feedback-(f-): Get negative feedback.
  • review(r): review a patch.
  • review?(r?): patch is under review
  • review+(r+): get review+ and ready to check-in
  • review-(r-): get negative review feedback. Fix problems and switch back to r? again.
  • land: patch check in.
  • debug: Figure out the root cause of a bug/ try to repro that bug, etc...
  • file: file a bug
  • PTO: take personal leave
  • interview(I)
  • study: Spend time on domain knowledge study, such as multimedia transport technology, compress format, real-time rendering.
  • presentation
    • Write a personal blog, which is relative to work, such as articles on MozTech, or what you experience in a work week.
    • WIKI/ MDN article writing.
    • If you write a technical blog or anything relative to work, it's welcome to share it on weekly report.
    • Do a presentation of technical topics

Status code combination rule
Combine status code with "|". For example

** OOAD|WIP

Which means you work on both OOAD and WIP in the last week.

land status code
If your patch is target for specific branch, instead of central, postfix branch version. For exp

** land(1.4)