I just cut the 2.52.0 release branch <https://github.com/apache/beam/tree/release-2.52.0>. All commits after https://github.com/apache/beam/commit/ea8596f2df0e3e4b9da9f215ae6745c2ddfb6612 will be targeted for a later release.
There is currently still one open release blocker https://github.com/apache/beam/milestone/16 around a memory leak in the current proto version used by Python. This isn't a regression from 2.51 (it started in 2.47), but IMO it is likely severe enough to warrant a cherry-pick if the protobuf project is able to get the fix into their next release. We should have some idea of this in the next day or two. I will next start working on stabilizing the release branch and (eventually) preparing an RC1. Thanks, Danny On Wed, Oct 18, 2023 at 9:31 AM Danny McCormick <dannymccorm...@google.com> wrote: > Hey everyone, the next release (2.52.0) branch cut is scheduled for Nov 1, > 2023, 2 weeks from today, according to the release calendar [1]. I'd like > to perform this release; I will cut the branch on that date, and cherrypick > release-blocking fixes afterwards, if any. > > > Please help with the release by: > > > - Making sure that any unresolved release blocking issues have their > "Milestone" marked as "2.52.0 Release" as soon as possible. > > - Reviewing the current release blockers [2] and remove the Milestone if > they don't meet the criteria at [3]. There are currently 12 release > blockers. > > > Let me know if you have any comments/objections/questions. > > > Thanks, > > Danny > > > [1] > https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com > > [2] https://github.com/apache/beam/milestone/16 > > [3] https://beam.apache.org/contribute/release-blocking/ >
