Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-08-17 Thread Robert Burke
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. R

Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-08-16 Thread Robert Burke
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,

Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-08-16 Thread Robert Burke
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 t

Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-08-14 Thread Robert Burke
+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.

Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-08-14 Thread XQ Hu via dev
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

Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-08-14 Thread Hong
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?BestHongOn 14 Aug 2023, at 14:34, Robert Burke wrote:The release branch was cut. Before yhe weekend, I was working on getting the non-portable Data

Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-08-14 Thread Robert Burke
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

Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-08-14 Thread Hong Liang
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 wrote: > I'm in the process of producing the Cut branch, but due to various d

Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-08-09 Thread Robert Burke
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. Remainin

Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-07-28 Thread Ahmet Altay via dev
Thank you! On Wed, Jul 26, 2023 at 9:57 AM Kenneth Knowles wrote: > Hooray! > > Thanks for volunteering > > Kenn > > On Wed, Jul 26, 2023 at 11:49 AM Robert Burke wrote: > >> Hey Beam community, >> >> The next release (2.50.0) branch cut is scheduled on August 9th, 2023, >> according to >> the

Re: [PROPOSAL] Preparing for 2.50.0 Release

2023-07-26 Thread Kenneth Knowles
Hooray! Thanks for volunteering Kenn On Wed, Jul 26, 2023 at 11:49 AM 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 b