This issue is marked P1 but has had no recent status updates.

The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.

Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!

This issue is assigned to @sealesj but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

This issue was assigned to @sealesj but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.

Closing as stale. Please feel free to open a new issue with a strong justification for doing this.

(To be clear, the -release and -infra teams have no plans to work on this in the known future)