Problem statement

In Sentry, we sometimes mark issues as resolved after we pushed a new UL that fixes something. But then it can happen that this issue is marked as a regression by an instance that has not updated yet to that UL (for whatever reason).

Proposal

Sentry has a nice release tracking feature. It seems easy enough to enable, and would answer a few problems we currently have.

For a given Sentry issue, the main pros for this is that we would then be able to mark it not just "Resolved", but "Resolved for UL-nn".

Also, once we enable this, Sentry automatically enables a few more dashboard to help us have a better view of the issues associated to a given UL and what has likely introduced it.