From MozillaWiki
Jump to: navigation, search

Weekly Report

Astley Chen

Boris Chiou

  • PTO


  • bug 1281971 - PROCESS-CRASH | layout/style/test/test_value_cloning.html
    • land
  • bug 652991- SVG path fill rendering can break after window.history.pushState
    • prototyping

Jeremy Chen

  • PTO 1 week

Tingyu Lin


Others (Provide information or comments, and triage bugs)


  • Q2 goals update and review
    • Q2 deliverables update would be ended after 6/30.
    • Q2 goals review will be at 7/6.
  • Q2 Performance Review Detailed Timeline
  • Q3 goals planning
    • Planning will get started from 7/1 and complete 1st drafting on 7/6.

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


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)