Release 24.2.0

[azaslavsky]

24.1.2 | 24.2.0 | 24.3.0

• Release all components (replace items with publish repo issue links).
  • develop
  • relay
  • sentry
  • sentry-docs
  • snuba
  • symbolicator
  • vroom
• Release self-hosted.
  • Prepare the self-hosted release
  • Check to make sure the new release branch in self-hosted includes the appropriate CalVer images.
  • Accept (publish) the release.
  • Edit release notes.
• Follow up.
  • Create the next release issue and link it from this one.
  • Update the quarterly ticket.
  • Update the release issue template.
  • Create a PR to update relocation release tests to add the new version.

[aldy505]

As we have some PRs that modifies the sentry/sentry.conf.py file, I think it'd be best to tell everyone on the release notes (on repo's release page) that they need to check and do a diff between the previous version to update their sentry/sentry.conf.py file.

[hubertdeng123]

@aldy505 yeah you're right, thanks for the callout

[aldy505]

@hubertdeng123 some people are still missing that notes. See #2744 (comment) for one

cc @chadwhitacre

[chadwhitacre]

We need to get something in to fix up sentry.conf.py automatically prior to 24.2.0. We should rewrite the conf file automatically if it contains the default value, and we should report on what we did (whether rewrite or skip).

[chadwhitacre]

Reposted on #2728 and putting that in the TODO here.

[williamdes]

We need to get something in to fix up sentry.conf.py automatically prior to 24.2.0. We should rewrite the conf file automatically if it contains the default value, and we should report on what we did (whether rewrite or skip).

I my workflow I merge each release tag of this repo into my fork of this repo. The difference is that on my branch I have the final sentry.conf.py. Maybe add an opt out flag so people using their own config file can keep it unchanged? Or for example read only file systems.

[aldy505]

We need to get something in to fix up sentry.conf.py automatically prior to 24.2.0. We should rewrite the conf file automatically if it contains the default value, and we should report on what we did (whether rewrite or skip).

I'm not really good with Python but can we have 2 Python files that's merged or something?

• sentry.conf.py -> contains the changes needed. at the end of the file it imports the override file and replaces any exported variables.
• sentry.conf.override.py -> git ignored, custom config by users

Something similar to docker-compose and docker-compose.override maybe?

[chadwhitacre]

Maybe add an opt out flag so people using their own config file can keep it unchanged?

I'd be up for conf layering, not sure if we can get that done before the release.

[aldy505]

Also, this: #2751

Should be documented on sentry.conf.py

[chadwhitacre]

Sorry ... crossed wires. :)

Maybe add an opt out flag so people using their own config file can keep it unchanged?

I'd prefer not to add a flag to avoid complexity. If you have the updated value (PyMemcache or whatever) in your branch then a rewrite script under install.sh should be a no-op, right?

I'm not really good with Python but can we have 2 Python files that's merged or something?

I'd be up for conf layering, not sure if we can get that done before the release.

[williamdes]

I'd prefer not to add a flag to avoid complexity. If you have the updated value (PyMemcache or whatever) in your branch then a rewrite script under install.sh should be a no-op, right?

If it is a sed replaced sure, but is it is a file replacement then it will create some bugs
In my file I added more stuff from ENVs

[chadwhitacre]

Yeah I'm thinking sed.