User:Clouserw/AMO/Perf: Difference between revisions

Jump to navigation Jump to search
m
No edit summary
 
Line 19: Line 19:
* Create a CRUD form to enter this data
* Create a CRUD form to enter this data
** Group permissions are AddonPerf:Edit
** Group permissions are AddonPerf:Edit
** Form is accessible from a link associated with each version on the "Manage Status & Versions" page.  That is to say, Performance data is associated with add-on versions, not .xpi files.
** Form is associated with Add-on versions (not specific files)
** The form consists of:
** The form consists of:
*** (checkbox) Operating System:  '''No version'''.  Options: WINNT, Darwin, Linux, Android
*** (checkbox) Operating System:  '''No version'''.  Options: WINNT, Darwin, Linux, Android
Line 26: Line 26:
*** (radio) Severity: Options: no impact, small impact, major impact
*** (radio) Severity: Options: no impact, small impact, major impact
*** (textarea) Notes: An optional field for any notes from the reviewer.  Standard "some HTML allowed" textarea.
*** (textarea) Notes: An optional field for any notes from the reviewer.  Standard "some HTML allowed" textarea.
* backend of the form is a new db table which stores GUID, version, and associated data (similar to blocklisted guids table)
** There isn't an enforced FK to the add-ons table because we need to store info for non-hosted add-ons also
** Simple admin tool to search the table and allow results to be edited
** bonus points: for hosted add-ons add a link on their "Manage Status & Versions" pages
* Hook up the performance warning div's on the details pages, adjusting the wording for the new severity levels
* Hook up the performance warning div's on the details pages, adjusting the wording for the new severity levels
* Send the new performance data through the API (details below)
* Send the new performance data through the API (details below)
Confirmed users, Bureaucrats and Sysops emeriti
1,737

edits

Navigation menu