Auto Archive previous releases with Release Health

[test137E29B]

Problem Statement

The development team I lead releases quite a few updates across all our projects, and each one creates a new Sentry release. Currently we implement release health, though it's only really useful in persistent clients like iOS and Android. Once a backend or web service is updated, it's pretty much guaranteed that the new version is being used.

The problem I encounter is that old releases have to be archived manually one by one - this is quite a pain and leaves me just not bothering to archive them. I feel there could be some optional settings to archive a release after a period of time since a newer release reaches 100% adoption.

Solution Brainstorm

My idea is to add some kind of project level setting for releases to archive them under the following conditions:

• The release is not the latest release.
• The adoption of a newer release is 100% (maybe configurable, like 90%+)
• The release is more than n days old.

This would allow me to automatically have archived all releases that are not the latest, and are more than 7 days old, and where the user adoption rate is more than 90% or even is 100%.

This would reduce clutter in our Sentry dashboard, and probably also is better for Sentry to not be storing potentially hundreds or thousands of old unused releases across our many projects (and probably other's projects too!) should there be an option to auto-delete old (maybe archived) releases

Product Area

Releases

[getsantry[bot]]

Assigning to @getsentry/support for routing ⏲️

[getsantry[bot]]

Routing to @getsentry/product-owners-releases for triage ⏲️

[rachrwang]

Thanks for this feature suggestion, cc @jas-kas