Outage tasks for 2023-03-16

[kltm]

• [x] Send reminder email to go-consortium mailing list
• [x] Run noctua-models-migration pipeline for @vanaukenk (automated to day before) to get report
  http://skyhook.berkeleybop.org/noctua-models-migrations/reports/
• [x] Refresh minerva code with latest from minerva master
• [x] Run replaced_by term update on blazegraph (@vanaukenk)
• [x] Update MF-MF relations in blazegraph https://github.com/geneontology/noctua/issues/813
  https://github.com/geneontology/noctua-models-migrations/pull/20
• [x] Cycle minerva to get latest ontology
• [x] Update NEO
• [x] Check if compaction is now working: https://github.com/geneontology/neo/issues/106
• [x] Check if ecoli is back https://github.com/geneontology/neo/issues/114
• [x] Prep ticket for next outage

[kltm]

@vanaukenk Report ready. Please add the Jim update to the list when we are sure we'll not have to have another outage to fix it.

[vanaukenk]

Ontology replacement checked; only one model affected as a result of this obsoletion:

https://github.com/geneontology/go-announcements/issues/485

[vanaukenk]

See comment on: https://github.com/geneontology/neo/issues/114

Otherwise, I think we're okay with this maintenance outage, but noting, as I looked at a lot of models for the MF-MF relations update, that there are increasingly more QC checks that we need to do on the GO-CAMs, even those with 'development' status.