My plan is to pick those to stable, then compact-edges here on secure, then compact-edges on the affected 130GB instance. There's some value in doing this sooner rather than later because the backups for 130GB of edge data are having some issues. The instance is a free test instance so this isn't a huge concern, but I'd sleep better if it was running smoothly. If you don't run compact-edges I think the worst those changes could really do is cause some kind of temporary display bug with new transactions, so the risk should be pretty small.

Bad news: data still has one reader/writer in the Asana-to-Revision linking implementation. So we can't completely get rid of that yet.

this can probably be figured out by examining the 2.16.0 release notes

T4675 survives this, because rendering policy controls on the client is very complicated.

T13049 is a followup about generalizing exporters.

This is quite old and I have no idea how to reproduce it and thus no idea how to fix it. Locally, I tried a few things and wasn't able to identify a case where the Herald field value differed from my actual project list.

I'm rolling this forward into T13049. See also D18919.

I think a reasonable path forward here is for Diviner to have a {symbol} sort of syntax which executes a symbol index query. The symbol index can already be configured to know how to offer links to external documentation.

Rename the field to "Reviewer (Legacy)", or move it to a "Legacy" category -- maybe improves things, but really just punts this.

In PHI311, I think we hit a race like this:

Presuming this is resolved since we've seen at least some confirmation that it fixed issues and aren't aware of any remaining outstanding problems.

Worth noting that the desirability of self-notifs is highly contextual. We use gmail, I was shocked to find there is no way to get gmail to let me see my own posts. But then I'm one of the few people using a local mail client, and it is actually kind of annoying when I have to slog thru the copies of the self-notifs on my phone to try and get to the one comment in the midst of potentially dozens of self-notifs.

See PHI185. This was fixed by D18753 but didn't get linked up.

Maybe this works now?

I'm going to roll this up into T13047 since this stuff needs a rebuild in general.

Per above, I think the pathway forward here is probably "tighter integration", not "merge/replace", i.e. tools for Diviner to automatically update Symbols, too. I'm just going to conceptually roll this up into T13047.