Release 2.5.0

[replay]

This issue is tracking the progress of the release 2.5.0. The release candidate is scheduled for the week of 28th Nov.

2.5.0-rc.0

• [x] Write release notes document PR
• [x] PRs that should be merged before cutting the rc
  • [x] Fix panic in OTLP ingestion PR
  • [x] Hide TSDB block ranges period config from doc and mark it experimental PR
  • [x] Helm OTLP endpoint missing PR
  • [x] Remove "Inflight requests" from object store panels PR
• [x] PRs to cherry-pick after 2.5.0 was cut from r214
  • [x] Remove "Inflight requests" from object store panels original PR / backport PR
  • [x] Improve networking panels to work with read write deployment mode original PR / backport PR
  • [x] Refactoring: simplified dashboards resources and networking panels utilities original PR / backport PR
  • [x] Hide TSDB block ranges period config from doc and mark it experimental original PR / backport PR
  • [x] [otlp] Fix panic in dropped count (again!) original PR / backport PR
  • [x] Updated dashboard screenshots original PR / backport PR
  • [x] Fixed Changelog
    • [x] original PR1 / backport PR1
    • [x] original PR2 / backport PR2
• [x] Any feature we can promote to stable?
  • [x] None
• [x] Any deprecated features to drop?
  • [x] None
• [x] Check repo for TODOs that must be addressed in 2.5.0
• [x] Update CHANGELOG.md
  • [x] Add any missing CHANGELOG entry PR
  • [x] Sort CHANGELOG entries
  • [x] Cut the changelog PR (same as above)
• [x] Notify any open PR to rebase and move the CHANGELOG entry, using ./tools/release/notify-changelog-cut.sh
• [x] Update dashboard screenshots PR
• [x] Create release branch
• [x] Publish the release candidate
  • [x] Update VERSION and remove "main / unreleased" section from the CHANGELOG PR
  • [x] Tag the release
  • [x] Wait until the CI pipeline succeeds
  • [x] Create a pre-release on GitHub
  • [x] Merge the release branch release-x.y into main
  • [x] Announce the rc on social media (twitter / mastodon)
• [x] Publish the Helm rc
• [x] Vendor the release commit of Mimir into GEM (PR)

[replay]

In this comment I'm going to track the status of the stable release

• [x] Publish the Mimir stable release
  • [x] Write release notes
    • Ensure the any change to release notes in main has been cherry picked to the release branch
    • Backported release notes from main into release branch in https://github.com/grafana/mimir/pull/3724#pullrequestreview-1217477270
  • [x] Update version in release- branch: https://github.com/grafana/mimir/pull/3725
    • VERSION
    • CHANGELOG
    • operations/mimir/images.libsonnet (_images.mimir and _images.query_tee fields)
    • operations/mimir-rules-action/Dockerfile (grafana/mimirtool image tag)
  • [x] Tag the release
  • [x] Wait until the CI pipeline succeeds
  • [x] Create a release on GitHub
  • [x] Merge the release branch release- into main https://github.com/grafana/mimir/pull/3727
  • [x] Announce the release on socials (tweet)
  • [x] Open a PR to add the new version to the backward compatibility integration test (integration/backward_compatibility_test.go): https://github.com/grafana/mimir/pull/3726
  • [x] Publish dashboards to grafana.com
• [x] Publish the Helm release candidate
  • Ask people working on Helm to do it