feat(releasing): Add release script to CDC

[fpacifici]

We will have to cut releases.

This now does not follow calver, but that is up for debate. CDC is not a core part of sentry, more of an external dependency (it is also not BSL @BYK what do you think? ).

[BYK]

We will have to cut releases.

Can you elaborate on why?

This now does not follow calver, but that is up for debate. CDC is not a core part of sentry, more of an external dependency (it is also not BSL @BYK what do you think? ).

If this is a project like Snuba, specific to Sentry and needs to go in lock-step, it should use CalVer and BSL. If it is a project that can be used outside of Sentry, like Symbolicator, then we should use Apache-2 and SemVer.

[fpacifici]

Can you elaborate on why?

I thought that would be the cleanest way to pin a release when we cut an on premise release. We could reference a specific commit otherwise.

If this is a project like Snuba, specific to Sentry and needs to go in lock-step, it should use CalVer and BSL. If it is a project that can be used outside of Sentry, like Symbolicator, then we should use Apache-2 and SemVer.

So semver. Thanks.

[BYK]

We could reference a specific commit otherwise.

The approach we have taken with Symbolicator is to take the latest published release instead of latest master commit SHA.

[fpacifici]

The approach we have taken with Symbolicator is to take the latest published release instead of latest master commit SHA.

Right, so we do have to cut and publish releases for that, or am I missing something?

[BYK]

Right, so we do have to cut and publish releases for that, or am I missing something?

Yes we do.