TPEGFX/2014-12-25: Difference between revisions
< TPEGFX
Jump to navigation
Jump to search
Jeremychen (talk | contribs) |
|||
| Line 10: | Line 10: | ||
===Chiajung Hung=== | ===Chiajung Hung=== | ||
* {{bug|1110625}} - Minimize the overhead of app launch animation (>80ms) | |||
** Study | |||
** Study restyle system | |||
** Discuss some possible solution with thinker, alive | |||
===Ethan Lin=== | ===Ethan Lin=== | ||
Revision as of 03:24, 25 December 2014
Weekly Report
Boris Chiou
- bug 1098970 - [lollipop] Porting NativeWindow from LL to gonk
- r+ | land
- bug 1108449 - crash in libxul.so@0x6ca03b | mozilla::layers::ImageHost::Lock()
- debug | r+
- need to check
- bug 1098701 - [Silk] Gtest for project Silk
- study | OOAD
Chiajung Hung
- bug 1110625 - Minimize the overhead of app launch animation (>80ms)
- Study
- Study restyle system
- Discuss some possible solution with thinker, alive
Ethan Lin
- bug 1103258 - MOZ_ASSERT(aRect.width != 0 && aRect.height != 0, "Trying to create a render target of invalid size")
- r?
- bug 1042696 - TextureClient has its mAllocator member set twice
- land
- bug 1112031 - Internet Sharing Settings is not scrollable if HotSpot details panel closes with keyboard open
- f
- bug 1106909 - [System][Lockscreen] Notification Scrolling on the lock screen is slow to respond and choppy
- study
- ImageBridge workflow
- study
Jeremy Chen
- text selection/frame-displaylist-layer workflow
- study
Jerry Shih
- bug 1092978 - Integrate refresh driver
- got r+ except the ipc patch. Wait bent for reviewing.
Morris Tseng
Tingyu Lin
- 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
- Debug
- Add marionette test cases.
- bug 1114409 - [Text Selection] Check SelectionCarets behavior driven by APZ in the parent process
- file
- bug 1090682 - [Contacts]The delete function in contact details view does not work.
- r?
- 1114474 bug Bug 1114474 - Cannot launch reftest on b2g desktop
- file
- Waiting :jgriffin feedback.
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)