Release 22.10.0

[hubertdeng123]

22.9.0 | 22.10.0 | 22.11.0

https://github.com/getsentry/self-hosted/releases/tag/22.10.0

• publish: getsentry/relay@22.10.0 publish#1465
• publish: getsentry/snuba@22.10.0 publish#1467
• publish: getsentry/sentry@22.10.0 publish#1466
• publish: getsentry/sentry-docs@22.10.0 publish#1470
• publish: getsentry/develop@22.10.0 publish#1468
• publish: getsentry/self-hosted@22.10.0 publish#1469
• make 22.11.0 issue
• Verify that sentry-cli is tagging the release properly in prod -> Fix release tagging in self-hosted dogfooding #1757
• Note default branch name change in a future release (TBD) in release notes
• Deal with Fresh install error: AssertionError sentry.eventstream.kafka.backend in _build_consumer  sentry#40120
• Note kafka topic changes due to ^
• force opt in for issue reporting bumped to Release 22.11.0 #1754

[aminvakil]

I do not remember if we had another release on weekend or not 😃

Are we going to have a release today for October?

[hubertdeng123]

release is happening today!

[chadwhitacre]

We broke builds again. Post-mortem ...

What happened?

1. noticed "force opt in for issue reporting" at the last minute
2. attempted to address with Enforce error reporting for self-hosted #1753
3. asked the right question but ended up with the wrong answer - we switched away from .reporterrors in Switch from .reporterrors file to flag + envvar #1697
4. merged Enforce error reporting for self-hosted #1753 and broke builds

How do we get the release back on track?

Two options:

1. Kick "force opt in for issue reporting" can down the road.
2. Implement "force opt in for issue reporting" properly.

What can we do to prevent this from happening again?

1. Standardize e2e testing #1756
2. Learn to recognize a risky situation and escalate (from IC pov) or pay more attention (from EM pov).
3. Practice more attention to detail.

[chadwhitacre]

Now working through options on getsentry/sentry#40120 ...

1. Set up a second container for the additional post process forwarder.
2. Pin to an old snuba version.

[chadwhitacre]

We are trying to land #1759 and then will delete the release branch and rerun the prepare action.

[chadwhitacre]

Action items re: the Snuba changes ... would be caught earlier with:

• Make e2e tests more thorough #1761
• Check health of containers in e2e tests #1762