Analysis documents
- Original mega sheet: https://docs.google.com/spreadsheets/d/1Kxj9p4fKVNo2h23yAQVoOGg77dZ4FLxeXuYrH-1CrPA/edit#gid=0
- Already is tracking specific 'things' which need to be addressed
- Redux: https://docs.google.com/spreadsheets/d/1Ncbgbg-ZPSSScOaGswQSJRtreuJOlizRCFln4KyfMWI/edit#gid=0
- Simply severity+importance.
- Deprecated
- Redux Redux: https://docs.google.com/spreadsheets/d/1btVdLuV59GZkQax8Hk0jkWDeyF5O_M5HkylWL0WxHxo/edit#gid=0
- Just severity
Technical Debt analysis plan / what happened
Working meeting #1 (50minutes, date/time: June 30th at 9am Pacific):
- List all software and services we maintain (25 minutes)
- etherpad list for pre-meeting work: https://etherpad.wikimedia.org/p/relengtechdebt-stuffwemaintain
- Make a list of criteria by which to evaluate the software and services (25 minutes)
- etherpad list for pre-meeting work: https://etherpad.wikimedia.org/p/relengtechdebt-criteria
- (between meetings: Greg to create/update the working spreadsheet(s) with the above etherpad content - T139111)
Working meeting #2 (80 minutes, date/time: July 6th at 9am Pacific):
- Identify all associated "technical debt" things in each criteria category (55 minutes)
- Review all related incident reports for incomplete tasks (20 minutes)
Team meetings discussion about insufficiencies in the process July 18th and 25th
- Mega spreadsheet wasn't a good entry point for dealing with this
- "Redux" and then "Redux Redux" versions made.
Fill out "Redux Redux" sheet (week of August 1st)
- done
Identify hot-spots (week of August 8th)
- release tooling" (which included "MW 3rd party releases", "l10nupdate", and will probably include any "swat deploy tooling" to address process tech debt)
- CI/Nodepool
Next steps
- Make changes to quarterly goals as appropriate (emphasizing the identified tech debt)