TPEGFX/2015-03-26

From MozillaWiki
Jump to: navigation, search

Weekly Report

Boris Chiou

  • bug 1144012 - Wrap HAL code from HwcComposer2D
    • OOAD | WIP
    • Try to remove all ANDROID_VERSION in HwcComposer2D
    • Fix according to Peter and Jerry's feedbacks

Chiajung Hung

  • bug 1146214 - Refactor fence delivery to reduce ipc messages and code duplication
    • feedback
  • bug 1143064 - A simple cache for decision results during BuildDisplayList
    • study/debug
  • bug 1118139 - [FFOS7715 v2.1] [dolphin][Youtube video] 7715 FFOS shows black screen on launching some video, while audio can be heared while using Youtube app or Youtube site
    • debug
    • give some proposal
  • BuildDisplayList
    • study

Ethan Lin

  • bug 1146214 - Refactor fence delivery to reduce ipc messages and code duplication
    • f+
  • The flow of BuildLayer
    • study

Jeremy Chen

Jerry

  • bug 1145015 - crash in gfx/layers/opengl/OGLShaderProgram
    • r+
    • Data racing problem in ShareBufferManager. Remove the data racing problem and clean up shadowLayerUtilGralloc.
  • HWC partial composition
    • MDP-base device could use partial, but I would like to clean up HWC::Render().
  • HWC virtual display
    • Test hwc list outbuf field.

Morris Tseng

  • bug 1143139 - Intermittent test_selectioncarets.py | application crashed [@ mozilla::SelectionCarets::DispatchSelectionStateChangedEvent(mozilla::dom::Selection *,mozilla::dom::Sequence<mozilla::dom::SelectionState> const &)]
    • land
  • bug 1021499 - [Text Selection] carets might be truncated by keyboard
    • r?
    • Has a dependent bug, bug 1147279.
  • bug 1147279 - The event region seems wrong if element becomes image layer.
    • file, debug
  • bug 1146753 - When test text_selection_test.js, we should wait for caret time before proceeding next action.
    • land

Tingyu Lin

Peter Chang

  • bug 1144990 - Dump display items with class id and name
    • wip
  • bug 1127170 - Layer transaction spends more than 150ms when switch app
    • r+
    • wait for gaia patch review

Team

  • 績效面談
  • Personal sharing
    • How to improve

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)