1,138 bytes added ,  16 April 2019
wip
(wip)
(wip)
Line 171: Line 171:
}}
}}
{{AutonagRule
{{AutonagRule
   | Rule name =  
   | Rule name = Remind developers about tracked bugs
   | Purpose  =  
   | Purpose  = Make sure that bugs tracked for the next release are addressed
  | Action    =
   | Source    = query_creator.py
   | Source    =  
}}
}}
{{AutonagRule
{{AutonagRule
   | Rule name =  
   | Rule name = Reporter not answering to Needinfo request
   | Purpose  =  
   | Purpose  = identify bugs stalled because we need more information fron the reporter to reproduce it
  | Action    =
   | Source    = reporter_with_ni.py
   | Source    =  
}}
}}
{{AutonagRule
{{AutonagRule
   | Rule name =  
   | Rule name = Top crashers vs ''normal'' severity
   | Purpose  =  
   | Purpose  = Consistency and help getting traction on bugs
   | Action    =  
  | Example  = 1471692
   | Source    =  
  | Source    = topcrash_bad_severity.py
}}
{{AutonagRule
  | Rule name = Identify tracked bugs with a NeedInfo request
  | Purpose  = Make sure that bugs tracked for a release or nominated for tracking which also have a NeedInfo request do not get stuck
  | Action    = Send an email
  | Source    = tracked_needinfo.py
}}
{{AutonagRule
  | Rule name = Tracked bugs untouched for a week
  | Purpose  = Identify important bugs for a release which are not being acted upon
  | Action    = Send an email
  | Source    = tracking.py
}}
{{AutonagRule
  | Rule name = Regressed in upcoming release
  | Purpose  = Identify potential regression
  | Action    = Send an email with the list of bugs marked as non affecting a release but affecting the next one
  | Source    = unaffected_affected_no_reg.py
}}
{{AutonagRule
  | Rule name = Identify unlanded uplifts to Beta and ESR
  | Purpose  =  Make sure that we ship with the bugs that we need
  | Action    = Send an email wih the list of bugs with uplift requests not landed on the affected branch
  | Example  = 1509394
  | Source    = unlanded.py
}}
{{AutonagRule
  | Rule name = Bugs with high severity in Firefox::Untriaged
  | Purpose  = Identify potentially important issues left untriaged
  | Source    = untriage_important_sev.py
}}
{{AutonagRule
  | Rule name = <code>Version</code> set but not <code>status_firefox</code>
  | Purpose  = The <code>Version</code> value is set automatically by Bugzilla on landing a patch  but not the <code>status_firefoxXX</code>
  | Action    = Send an email
  | Source    = version_affected.py
}}
{{AutonagRule
  | Rule name = Check release dates on the Wiki
  | Purpose  = Verify the consistency of our release dates on wiki.mozilla.org as we use them in automation
  | Action    = Send an email
  | Source    = ../next_release.py
}}
{{AutonagRule
  | Rule name = Information about bugs landed during Soft Code Freeze
  | Purpose  = List fixed bug with patches  which landed in mozilla-central during the soft freeze week. The listing includes patch statistics.
  | Action    = Send an email
  | Source    = code_freeze_week.py
}}
{{AutonagRule
  | Rule name = Hightlight Fixed bugs in nightly we may want to uplift
  | Purpose  = Identify potentially upliftable  bugs.
  | Action    = Send an email with the recent fixes, the affected branches and metadata for prioritization
  | Source    = missed_uplifts.py
}}
{{AutonagRule
  | Rule name = New user with a Needinfo request
  | Purpose  = Help to identify potentiallyunactionnable bugs per lack of information
  | Action    = Send an email
  | Source    = newbie_with_ni.py
}}
{{AutonagRule
  | Rule name = Patch not landed
  | Purpose  = Identify bugs with an unlanded r+ patch. Maybe the patch is now obsolete or the bug needs to have a sheriff land the code with the <code>checkin-needed</code> keyword set.
   | Action    = Send an email
   | Source    = not_landed.py
}}
}}
| query_creator.py
| Send reminders to developer with assigned tracked bugs
| Make sure that bugs for the next release are addressed
| Not yet
|
|-
| reporter_with_ni.py
| Identify bugs with needinfo on the reporter without activity
| Usually a sign of a reporter not answering to more requests
| Not yet
|
|-
| topcrash_bad_severity.py
| Topcrash bugs with normal severity
| Consistency and help getting traction on bugs
| Not yet
| {{bug|1471692}}
|-
| tracked_needinfo.py
| Tracked or Nominated for Tracking with Need-Info?
| Make sure that bugs for the next release are addressed
| Email
|
|-
| tracking.py
| Get the tracked bugs in a release and untouched this week
| Identify inactive bugs
| Email
|
|-
| unaffected_affected_no_reg.py
| List bugs marked as non affecting a release but affecting the next one
| Sign of a regression
| Email
|
|-
| unlanded.py
| Patches which didn’t land on beta and esr
| Make sure that we ship with the bugs that we need
| Email
| {{bug|1509394}}
|-
| untriage_important_sev.py
| Firfox/untriaged with an important severity
| Identify potential important issues in untriage
| Not yet
|
|-
| version_affected.py
| Bug with version set but not status_firefox
| Version is set automatically by bugzilla but status_firefox isn’t
| Email
|
|-
| ../next_release.py
| Check if the release dates are consistent on the Wiki pages
| We use these dates in automation
| Email
|
|-
| code_freeze_week.py
| Fixed bug with patches which landed in mozilla-central during the soft freeze week
| Give some information like number of patches, number of changed lines, ...
| Email
|
|-
| missed_uplifts.py
| Fixed bug in nightly with patches and beta or release affected.
| Give some information about priority, severity, ...
| Email
|
|-
| newbie_with_ni.py
| Bug where the reporter has a needinfo and with no activity
| Help to identify probably unactionnable bugs because of lack of information
| Email
|
|-
| not_landed.py
| Bug with a r+ patch but the patch didn't land.
| Maybe a checkin-needed is required or the patch is obsolete
| Email
|
|}
[[category:Release_Management|Autonag]]
[[category:Release_Management|Autonag]]
Confirmed users
1,321

edits