RC1 is sufficiently ready for testing and validation. Please vote and discuss at that thread.
https://lists.apache.org/thread/xgx49zshms7253lfx6d6lsnvwf7tyyfp Robert Burke 2.50.0 Release Manager On 2023/08/17 02:30:00 Robert Burke wrote: > Despite my best efforts, python continues to vex me. RC1 is almost ready, > just missing the beam site and doc updates PR, and (optionally) the > typescript container. > > So I'm calling it a night, and will build and send out a partial docs PR in > the morning. > Robert Burke > 2.50.0 Release Manager > > On Wed, Aug 16, 2023, 8:08 AM Robert Burke <lostl...@apache.org> wrote: > > > Just a status update: Branch is cut and tagged > > > > https://github.com/apache/beam/tree/release-2.50.0 > > https://github.com/apache/beam/tree/v2.50.0-RC1 > > > > I'm working on the remaining bits to have an RC. The github > > build-release-artifacts action failed to > > build and publish the Java Artifacts and stage the Docker containers. > > > > The former says: > > > > Execution failed for task ':sdks:java:io:solr:compileTestJava'. > > GC overhead limit exceeded > > > > The latter is due to a partial application of the Multi-Arch build to the > > github actions, that has already been fixed. > > > > The Dataflow Legacy Java worker and associated containers have been built > > and published, and we apologize for the delay this caused. We're discussing > > how we presently interleave Google internal processes with the release, and > > how we can streamline things now that Dataflow is transitioning to RunnerV2 > > by default. In future releases, we may build the non-portable Dataflow Java > > workers after the first RC is tagged and the open side is on its way. > > > > The hope is RC1 will be available tonight. Either way, this thread will be > > updated with the status. > > > > Robert Burke > > Beam 2.50.0 Release Manager > > > > On 2023/08/14 21:51:47 Robert Burke wrote: > > > +1 to what XQ says. > > > > > > There will be a voting email thread once I've done the appropriate due > > > diligence to the branch, and finish with the Dataflow artifacts. > > > > > > Generally speaking, the best validation is something you're using > > already, > > > to make sure that the new version of Beam works for your usage. > > > > > > > > > On Mon, Aug 14, 2023, 2:41 PM XQ Hu via dev <dev@beam.apache.org> wrote: > > > > > > > Welcome to the Beam community! Our release managers usually follow this > > > > > > https://beam.apache.org/contribute/release-guide/#10-vote-and-validate-release-candidate > > > > to send the votes out and ask for any feedback regarding the release > > > > candidate. If you could help run any validation on your side and cast > > your > > > > vote, it would be greatly appreciated and helpful for the community. > > > > > > > > On Mon, Aug 14, 2023 at 12:23 PM Hong <h...@apache.org> wrote: > > > > > > > >> I see, thanks for clarifying, Robert! > > > >> > > > >> Is there anything I can help with validation? Is there a wiki page > > with > > > >> the expected validations I can help with? > > > >> > > > >> Best > > > >> Hong > > > >> > > > >> On 14 Aug 2023, at 14:34, Robert Burke <rob...@frantil.com> wrote: > > > >> > > > >> > > > >> The release branch was cut. Before yhe weekend, I was working on > > getting > > > >> the non-portable Dataflow Java worker built and available before > > producing > > > >> the RC1. The actual building bit doesn't take that long, but there's a > > > >> bunch of additional validation that goes along with it. > > > >> > > > >> The current target date for 2.50.0 is September 13th, but ultimately > > it's > > > >> as soon as we have a validated and voted on RC. > > > >> > > > >> On Mon, Aug 14, 2023, 3:43 AM Hong Liang <hlteo...@gmail.com> wrote: > > > >> > > > >>> Thanks for driving this Robert! > > > >>> > > > >>> It seems the two PRs specified have been merged. A little new to > > Beam, > > > >>> do we have an expected release date for the 2.50 release? > > > >>> > > > >>> Best, > > > >>> Hong > > > >>> > > > >>> On Thu, Aug 10, 2023 at 3:08 AM Robert Burke <lostl...@apache.org> > > > >>> wrote: > > > >>> > > > >>>> I'm in the process of producing the Cut branch, but due to various > > > >>>> delays on my part, it will not be cut today. > > > >>>> > > > >>>> There are two outstanding PRs blocking the cut, > > > >>>> https://github.com/apache/beam/pull/27947 and > > > >>>> https://github.com/apache/beam/pull/27939, but once those are in, > > I'll > > > >>>> proceed. Remaining new issues will be cherry picked as required. > > > >>>> > > > >>>> Thanks > > > >>>> Robert Burke > > > >>>> Beam 2.50.0 Release Manager > > > >>>> > > > >>>> On 2023/07/26 15:49:37 Robert Burke wrote: > > > >>>> > Hey Beam community, > > > >>>> > > > > >>>> > The next release (2.50.0) branch cut is scheduled on August 9th, > > 2023, > > > >>>> > according to > > > >>>> > the release calendar [1]. > > > >>>> > > > > >>>> > I volunteer to perform this release. My plan is to cut the branch > > on > > > >>>> that > > > >>>> > date, and cherrypick release-blocking fixes afterwards, if any. > > > >>>> > > > > >>>> > Please help me make sure the release goes smoothly by: > > > >>>> > - Making sure that any unresolved release blocking issues for > > 2.50.0 > > > >>>> should > > > >>>> > have their "Milestone" marked as "2.50.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]. > > > >>>> > > > > >>>> > Let me know if you have any comments/objections/questions. > > > >>>> > > > > >>>> > Thanks, > > > >>>> > > > > >>>> > Robert Burke (he/him) > > > >>>> > Beam Go Busybody > > > >>>> > > > > >>>> > [1] > > > >>>> > > > > >>>> > > https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com > > > >>>> > [2] https://github.com/apache/beam/milestone/14 > > > >>>> > [3] https://beam.apache.org/contribute/release-blocking/ > > > >>>> > > > > >>>> > > > >>> > > > > > >
