Update before the weekend - I likely won't have an RC out until early next week. I'm currently running down the following issues with RC creation:
1) Publishing java artifacts is failing because of an illegal implicit gradle dependency [1]. I have a PR [2] and cherrypick PR [3] prepared which should hopefully fix this. 2) Publishing to dockerhub is failing because the Java 21 repo hasn't been created [4]. I have a Jira open with Infra to add it [5]. 3) There are multiple issues with staging the java/python source. I ran into some issues initially [6] which I think I have a PR to fix [7], but there seem to be more issues beyond that as well [8]. Likely some of these are around the move to pyproject.toml, but I haven't found a conclusive cause yet. I plan on continuing to work on fixes here, and am hopeful that I'll have an RC out early next week. [1] https://github.com/apache/beam/actions/runs/6747166089/job/18342723439 [2] https://github.com/apache/beam/pull/29296 [3] https://github.com/apache/beam/pull/29298 [4] https://github.com/apache/beam/actions/runs/6747166089/job/18342724190 [5] https://issues.apache.org/jira/browse/INFRA-25141 [6] https://github.com/apache/beam/actions/runs/6747166089/job/18342723732 [7] https://github.com/apache/beam/pull/29299 [8] https://github.com/apache/beam/actions/runs/6747240788/job/18342935430 Thanks, Danny On Wed, Nov 1, 2023 at 1:09 PM Danny McCormick <dannymccorm...@google.com> wrote: > 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/ >> >
