Open mman opened 1 year ago
Assigning to @getsentry/support for routing, due by (sfo). ⏲️
Routing to @getsentry/product-owners-releases for triage, due by (sfo). ⏲️
Thanks @mman ! Good request
@getsentry/team-starfish I think this may make sense to be tracked by your team. Let me know.
This does sound a lot like what Starfish is working on. Going with Projects area (as in original ticket) to get this on @silent1mezzo's radar.
Routing to @getsentry/product-owners-projects for triage, due by (yyz). ⏲️
Ya we've been thinking about this at a very high level but we're a long way out. Will backlog it for now.
Routing to @getsentry/product-owners-projects-project-details for triage ⏲️
Problem Statement
When managing a big PRODUCT, that can be composed from smaller individual sentry products. Say for example:
All of these sentry products have unrelated release cycle, have a separate sentry project entry, versioning scheme, but are all tightly coupled together.
I would like to see them grouped together on the releases page so that I can quickly asses overal health of the top level PRODUCT and quickly identify issues with nested sentry products.
Solution Brainstorm
One way to achieve this at the moment is to create a release that is the same for all sentry products, and then they nicely group together as shown the projects section in sentry documentation. But this is impractical as it requires new builds of all nested projects even if they are unaffected.
Another way is to put related products on teams, but as far as I can see there is no easy and nice way to see team releases grouped nicely together.
I think the solution should involve grouping projects together via CLI or sentry web interface so that grouping can be done without requiring new build of each sentry project...
Product Area
Projects