Confirmed users
391
edits
Buildduty/manifesto: Difference between revisions
m
Reorder hred in intro.
m (Add more hrefs.) |
m (Reorder hred in intro.) |
||
| Line 6: | Line 6: | ||
* [[ReleaseEngineering/Buildduty_manifesto#Monitoring_Firefox_CI_backlog/pending_counts| Monitoring Firefox CI backlog/pending counts]] | * [[ReleaseEngineering/Buildduty_manifesto#Monitoring_Firefox_CI_backlog/pending_counts| Monitoring Firefox CI backlog/pending counts]] | ||
* [[ReleaseEngineering/Buildduty_manifesto#Tree_closing_and_opening| Tree closing and opening]] | * [[ReleaseEngineering/Buildduty_manifesto#Tree_closing_and_opening| Tree closing and opening]] | ||
* [[ReleaseEngineering/Buildduty_manifesto#Loaning_Firefox_build/test_instances_to_developers| Loaning Firefox build/test instances to developers]] | |||
* [[ReleaseEngineering/Buildduty_manifesto#Upload_new_packages_or_Python_modules_to_our_internal mirrors| Upload new packages or Python modules to our internal mirrors]] | |||
* [[ReleaseEngineering/Buildduty_manifesto#Routine_maintenance_of_the_Firefox_CI_configuration| Routine maintenance of the Firefox CI configuration]] | * [[ReleaseEngineering/Buildduty_manifesto#Routine_maintenance_of_the_Firefox_CI_configuration| Routine maintenance of the Firefox CI configuration]] | ||
While team’s responsibilities cover a wide variety of tasks, people sometimes contact them for (or file bugs in their queue for) '''''issues that don’t''''' fall under their area of expertise. The following are some of the most common examples: | While team’s responsibilities cover a wide variety of tasks, people sometimes contact them for (or file bugs in their queue for) '''''issues that don’t''''' fall under their area of expertise. The following are some of the most common examples: | ||