| | Review documentation of process for isolating model removals as part of the release pipeline | | | | | Unresolved | Mar 17, 2017 | Mar 31, 2017 | | |
| | Decision about field deprecation recommendations | | | | | Unresolved | Mar 15, 2017 | Mar 31, 2017 | | |
| | Consider policy around expand/contract and relationship to Open edX releases | | | | | Unresolved | Mar 3, 2017 | Mar 3, 2017 | | |
| | Review migration issues found during Ficus | | | | | Done | Mar 3, 2017 | Mar 3, 2017 | | |
| | Discovery: tooling around mongo index migrations | | | | | Unresolved | Feb 17, 2017 | Feb 17, 2017 | | |
| | [Pipeline] Capture tables being impacted by migrations during process on stage | | | | | Unresolved | Feb 3, 2017 | Feb 17, 2017 | | |
| | [Pipeline] Alarm when migrations take over N seconds on stage | | | | | Done | Feb 3, 2017 | Feb 17, 2017 | | |
| | Identify options for alerting on tables reaching maximum PK size | | | | | Unresolved | Jan 23, 2017 | Jan 23, 2017 | | |
| | Discovery: Python libraries or other tools to detect slow/inefficient queries during development | | | | | Unresolved | Jan 6, 2017 | Jan 6, 2017 | | |
| | Is there anything more NewRelic can do to alert us of bad query patterns as they happen? | | | | | Done | Jan 6, 2017 | Feb 3, 2017 | | |
| | Is existing slow query log alerting sufficient? | | | | | Done | Jan 6, 2017 | Mar 3, 2017 | | |
| | Discovery: Options for CI or dev env testing tool to diff schemas between master and feature branch | | | | | Unresolved | Jan 6, 2017 | Mar 31, 2017 | | |
| | Capture tables being modified during stage migrations in pipeline | | | | | Unresolved | Jan 6, 2017 | Mar 23, 2017 | | |
| | Document common operations and steps for how to do them | | | | | Unresolved | Oct 17, 2016 | Jan 6, 2017 | | |
| | Evaluate nplusone lib | | | | | Unresolved | Mar 28, 2016 | Mar 17, 2017 | | |
| | Add list of busy and otherwise potentially problematic tables to migration review guidelines | | | | | Done | Mar 28, 2016 | Jan 6, 2017 | | |
| | Document Process for Adding to Migration Eval Committee | | | | | Done | Mar 7, 2016 | Sep 30, 2016 | | |
| | Form review committee for migration evals | | | | | Done | Mar 7, 2016 | Sep 30, 2016 | | |
| | Train all current engineers in migrations | | | | | Unresolved | Mar 7, 2016 | Mar 7, 2016 | | |
| | Create training for migration evaluation concepts | | | | | Unresolved | Mar 7, 2016 | Sep 30, 2016 | | |
| | Document recommendations, patterns and flags for migrations | | | | | Done | Mar 7, 2016 | Jan 6, 2017 | | |
| | Document and automate process of detecting potential migration issues | | | | | Unresolved | Feb 24, 2016 | Mar 17, 2017 | | |
| | Identify opportunities for internal training on data topics | | | | | Unresolved | Feb 24, 2016 | Feb 24, 2016 | | |
| | Create data model documentation for ORA2 | | | | | Unresolved | Feb 24, 2016 | Feb 24, 2016 | | |
| | Repeat DATA-1 for other services | | | | | Unresolved | Feb 24, 2016 | Feb 24, 2016 | | |
| | Proactive monitoring for potentially problematic data access patterns | | | | | Unresolved | Feb 24, 2016 | Jan 6, 2017 | | |
| | Create automated checks & tests for common data / ORM issues | | | | | Unresolved | Feb 24, 2016 | Feb 24, 2016 | | |
| | Create policies and tools to enable safe access to data | | | | | Unresolved | Feb 24, 2016 | Feb 24, 2016 | | |
| | Establish hiring criteria for knowledge of data layer topics | | | | | Unresolved | Feb 24, 2016 | Jan 6, 2017 | | |
| | Create better documentation of the existing edx-platform data model | | | | | Unresolved | Feb 24, 2016 | Feb 24, 2016 | | |
