TPEGFX/2014-12-18

From MozillaWiki
Jump to: navigation, search

Weekly Report

Boris Chiou

  • bug 1098970 - [lollipop] Porting NativeWindow from LL to gonk
    • r?

Chiajung Hung

  • bug 1110625 - Minimize the overhead of app launch animation (>80ms)
    • Debug
    • Profile analysis, and found some hint to try
  • bug 1098970 - [lollipop] Porting NativeWindow from LL to gonk
    • review/study
    • Help review
  • bug 918984 - Direct video stream texturing support on WebGL
    • WIP/DEBUG
    • Basic refactor done, and added support for ImageElement.
    • CanvasElement need more test and rethink, maybe need polling.
  • PTO 1 day

Ethan Lin

  • bug 1042696 - TextureClient has its mAllocator member set twice
    • f?
  • bug 1103258 - MOZ_ASSERT(aRect.width != 0 && aRect.height != 0, "Trying to create a render target of invalid size")
    • debug
  • bug 1112433 - The screen shouldn't timeout when scrolling notifications on the lockscreen
    • file

Jeremy Chen

  • bug 1109486 - XMLHttpRequest.send(document) should unconditionally encode as UTF-8
    • landed

Jerry Shih

Morris Tseng

  • bug 1092888 - [Text selection] Enable selection carets for non-editable fields on B2G and fix the existing test case failures
    • Re-landed.
  • bug 1109800 - [Settings][Rocketbar] Keyboard pops up when open "Privacy Notice" link
    • r?
  • bug 1097419 - [Calendar][Text Selection] Selection bubble doesn't appear on account login
    • r?
    • Writing mochitest
  • bug 1101364 - Non-editable element content will be selected even the element already set user-select: none
    • landed

Tingyu Lin

Peter Chang

  • bug 1111433 - Close the text dialog when the focused content gets blur
    • r+
  • bug 1098161 - Trigger text dialog by long press when input filed is empty
    • r?
  • bug 1068474 - flicker to tilt mode when selection range is changed
    • r?
    • Verify the content editable and non-editable

Team

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)