[docs] - communicate the maturity of each integration

[erinkcochran87]

Since this issue was created, we've added libs (x.y.z) to the version toggle in the docs to indicate library versions for a given release:

This section was also added to the Releases & Compatibility page.

I think it'd be neat/useful to add something to each integration's main page that indicates its current version, last updated date, and maybe even a changelog, when we get to the point that library versions take a different track. For now though, I'm inclined to close this unless you feel strongly about keeping it open.

[sryza]

Even though they have the same version numbering, I think our integrations have pretty different levels of maturity. E.g. our dbt and s3 integrations are very mature, and our mlflow integration is very immature. I don't think users have a great way of finding that out right now, so I still think it's worth finding a way to communicate these differences.

[erinkcochran87]

Ahh I see what you're saying. Do we have criteria for what makes an integration more or less mature?

[sryza]

@rexledesma - is this something you've thought about?

[edsoncezar16]

Hi, I think it is quite hard to define precise criteria for levels of maturity, but I would like to suggest a simpler yet effective step in that direction.

You could add a symbol, say a star, for the integrations that you, at Dagster Labs, either are actively developing, use internally, or at least still have on your roadmap.

In this way, we can make a more informed decision on whether it is worth using a certain integration or whether we are putting ourselves in the dark by using something that will not have support soon.