Latest revision as of 17:09, 4 October 2011

Redirect to:

ReleaseEngineering:Buildduty

This page deprecated, please see ReleaseEngineering:Buildduty

Each week there is one person from the Release Engineering team dedicated to helping out developers with releng-related issues. This person will be available during his or her regular work hours for the whole week. This is similar to the sheriff role that rotates through the developer community. To avoid confusion, the releng sheriff position is informally known as "buildduty." When nobody is on buildduty (off hours and weekends), consult #build with any issues - in most cases someone is available.

Schedule

Mozilla Releng Sheriff Schedule (Google Calendar|iCal|XML)

Duties

Buildduty will:

Manually kick off runs for try talos builds - file a ticket for this purpose, please
Keep build slaves humming along nicely
Monitor #developers irc channel for issues.
Monitor wait times emails and respond to any unusually long wait times
Schedule and lead downtimes (if needed) and coordinate with the developers as needed
Keep ReleaseEngineering:Maintenance up to date
Kick self-serve if needed Kicking
Take any bugs that are "shepherding" bugs requested by A-Team so that they have a point person to get to deployment with

@@ Line 1: / Line 1: @@
-Each week there will be one person from the Release Engineering team dedicated to helping out developers with build / unittest / talos issues.  This person will be available during his or her regular work hours for the whole week.
+#REDIRECT [[ReleaseEngineering:Buildduty]]
-= Duties =
+'''This page deprecated, please see [[ReleaseEngineering:Buildduty]]'''
-* Monitor the [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=release-eng-triage release-eng-triage] bug queue.  Ask in #mozbuild to see if anybody wants to take it on, otherwise move it to Future, or bring it up at the next team meeting.
+Each week there is one person from the Release Engineering team dedicated to helping out developers with releng-related issues.  This person will be available during his or her regular work hours for the whole week.  This is similar to the sheriff role that rotates through the developer community. To avoid confusion, the releng sheriff position is informally known as "'''buildduty'''."  When nobody is on buildduty (off hours and weekends), consult #build with any issues - in most cases someone is available.
-* Monitor the #developers irc channel for issues.  Make sure the sheriff knows who you are, and that they can contact you if they have any questions or issues.
-* Monitor the dev.tree-management newsgroup (by [https://lists.mozilla.org/listinfo/dev-tree-management email] or by [nntp://mozilla.dev.tree-management nntp])
 = Schedule =
-{| class="fullwidth-table"
-| '''Week'''
-| '''Person'''
-|-
-| style="background-color: lime" | Feb 17 - Feb 20, 2009
-| style="background-color: lime" | Chris AtLee (catlee)
-|-
-| Feb 23 - 27, 2009
-| Ben Hearsum (bhearsum)
-|}
-(hopefully we can get this moved onto the sheriff's calendar)
+Mozilla Releng Sheriff Schedule ([http://www.google.com/calendar/embed?src=aelh98g866kuc80d5nbfqo6u54%40group.calendar.google.com&ctz=America/New_York Google Calendar]|[http://www.google.com/calendar/ical/aelh98g866kuc80d5nbfqo6u54%40group.calendar.google.com/public/basic.ics iCal]|[http://www.google.com/calendar/feeds/aelh98g866kuc80d5nbfqo6u54%40group.calendar.google.com/public/basic XML])
+= Duties =
+Buildduty will:
+* Manually kick off runs for try talos builds - file a ticket for this purpose, please
+* Keep build slaves humming along nicely
+* Monitor #developers irc channel for issues.
+* Monitor wait times emails and respond to any unusually long wait times
+* Schedule and lead downtimes (if needed) and coordinate with the developers as needed
+* Keep [[ReleaseEngineering:Maintenance]] up to date
+* Kick self-serve if needed [https://wiki.mozilla.org/ReleaseEngineering/BuildAPI#Kicking Kicking]
+* Take any bugs that are "shepherding" bugs requested by A-Team so that they have a point person to get to deployment with

ReleaseEngineering/Sheriffing: Difference between revisions

Latest revision as of 17:09, 4 October 2011

Schedule

Duties