Re: 2.41.0 Release PMC Finalization

Thanks Cham! On Tue, Aug 23, 2022 at 5:33 PM Chamikara Jayalath wrote: > Should be done. > > Thanks, > Cham > > On Tue, Aug 23, 2022 at 4:53 PM Chamikara Jayalath > wrote: > >> I can look into it. >> >> On Tue, Aug 23, 2022 at 2:02 PM Kiley Sok via dev

2.41.0 Release PMC Finalization

Could a PMC member help with the PMC-only finalization steps for 2.41.0 [1]? Specifically: - Deploy source release to dist.apache.org - Recordkeeping with ASF Once those steps are done all that's left is to promote the release [2]. Thank you! Kiley [1]

[RESULT] [VOTE] Release 2.41.0, release candidate #2

I'm happy to announce that we have unanimously approved this release. There are 5 approving votes, 3 of which are binding: * Ahmet Altay * Alexey Romanenko * Chamikara Jayalath There are no disapproving votes. Thanks everyone!

[VOTE] Release 2.41.0, release candidate #2

Hi everyone, Please review and vote on the release candidate #1 for the version 2.41.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Reviewers are encouraged to test their own use cases with the release candidate, and vote +1 if no

Re: [VOTE] Release 2.41.0, release candidate #1

PR to revert the change for the release https://github.com/apache/beam/pull/22759 I'll rebuild a new RC once the tests pass and the PR is merged. On Wed, Aug 17, 2022 at 8:16 AM Liam Miller-Cushon wrote: > On Tue, Aug 16, 2022 at 2:42 PM Kiley Sok wrote: > >> Liam, are we okay to roll back

Re: [VOTE] Release 2.41.0, release candidate #1

and was a while ago too and our > postcommits did not catch it either. > > Kenn > > On Tue, Aug 16, 2022 at 12:50 PM Kiley Sok via dev > wrote: > >> cc: @Liam Miller-Cushon , who worked on the bytebuddy >> update. >> >> Liam, do you have any context o

Re: [VOTE] Release 2.41.0, release candidate #1

ould just be my setup then. >>> Feel free to close the Github issue. >>> > >>> > - Cham >>> > >>> >> >>> >> >>> >> On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada >>> wrote: >>> >>> >>> >>> +

Re: [VOTE] Release 2.41.0, release candidate #1

On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev > wrote: > >> +1 - I validated python quickstarts on direct runner. >> >> Thank you Kiley! >> >> >> >> On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev >> wrote: >> >>>

[VOTE] Release 2.41.0, release candidate #1

Hi everyone, Please review and vote on the release candidate #1 for the version 2.41.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Reviewers are encouraged to test their own use cases with the release candidate, and vote +1 if no

Re: [Release] 2.41.0 release update

There's one new issue found while building the RC. Looking into it now https://github.com/apache/beam/issues/22621 On Fri, Aug 5, 2022 at 10:21 AM Ahmet Altay wrote: > Kiley, do we still have the same blockers? Do you need any help? > > On Thu, Aug 4, 2022 at 12:18 PM Kiley Sok via dev

Re: [Release] 2.41.0 release update

Last remaining issue was cherry-picked. There may be one last issue with gRPC that's being investigated. https://github.com/apache/beam/issues/22283 On Thu, Jul 28, 2022 at 2:20 PM Kiley Sok wrote: > Quick update for today: > > I'm still working through the validation tests, but we currently

Re: [Release] 2.41.0 release update

Quick update for today: I'm still working through the validation tests, but we currently have 2 open issues: https://github.com/apache/beam/issues/22454 https://github.com/apache/beam/issues/22188 On Wed, Jul 27, 2022 at 5:03 PM Kiley Sok wrote: > Hi all, > > I've cut the release branch: >

[Release] 2.41.0 release update

Hi all, I've cut the release branch: https://github.com/apache/beam/tree/release-2.41.0 There's one known issue that needs to be cherry picked. Please let me know if you have a change that needs to go

[PROPOSAL] Preparing for 2.41.0 Release

Hi all, The next (2.41.0) release branch cut is scheduled for July 27th, according to the release calendar [1]. I would like to volunteer myself to do 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