Confirmed users
978
edits
User:Hsinyi/Gecko engineering: Difference between revisions
Jump to navigation
Jump to search
what to work on as a guide
(start to work on ...) |
(what to work on as a guide) |
||
| Line 2: | Line 2: | ||
* What should I work on? | * What should I work on? | ||
** We want to deliver a product with high qualities to our users, we want to bring new values to our users. This won't happen without collaboration with various teams and our community. Therefore, when we are thinking about what we should work on with which priority, we consider to unblock others and help others as well. | ** We want to deliver a product with high qualities to our users, we want to bring new values to our users. This won't happen without collaboration with various teams and our community. Therefore, when we are thinking about what we should work on with which priority, we consider to unblock others and help others as well. Here is a list (in descending order of priority) to show others how our work is being prioritized, not necessarily a how to strictly prioritize the work. | ||
#Catastrophic bugs: Blocks development/testing, may impact more than 25% of users, causes data loss, potential chemspill, and no workaround available | |||
##sec-crit security bugs | |||
##Sev-blocker | |||
##Including regressions | |||
#Review and needinfo requests to unblock others | |||
#Serious bugs: Major Functionality/product severely impaired and a satisfactory workaround doesn't exist | |||
##sec-high security bugs | |||
##Sev-critical bugs | |||
#Special programs e.g. WFH bugs, webcompat bugs | |||
#Important partner bug fixes | |||
#Bug fixes | |||
#New features | |||
* Bug triage | * Bug triage | ||
* Code review | * Code review | ||
* Release health and product quality | * Release health and product quality | ||
* Roadmap and status communication | * Roadmap and status communication | ||