Re: Beam Release DockerHub Group
Thank you for doing this! I try to stay engaged with the releases and would be happy to be kept on this list. At the same time I agree with Robert, release managers should take precedence over PMC members if we cannot get the number to 6. On Mon, Apr 17, 2023 at 10:32 AM Robert Bradshaw via dev < dev@beam.apache.org> wrote: > Well, I don't know that PMC should take precedence over release managers > if it comes to that. > > On Mon, Apr 17, 2023 at 10:11 AM Danny McCormick < > dannymccorm...@google.com> wrote: > >> I can ask if we can keep 6 seats instead of 5 (and keep Ahmet in that >> seat). If not, my vote would be to stick with the 5 that I suggested, but >> if that's not acceptable then I'll drop one of the people (probably myself >> since I just finished a release and will probably be last up out of the >> group). >> >> Thanks, >> Danny >> >> On Mon, Apr 17, 2023 at 12:34 PM Robert Bradshaw >> wrote: >> >>> I think it'd be good if the intersection between this list and the PMC >>> had cardinality greater than 1. Ahmet might be a good person to keep there. >>> >>> On Mon, Apr 17, 2023 at 9:25 AM Danny McCormick via dev < >>> dev@beam.apache.org> wrote: >>> Yeah, that is part of the proposal. To be clear, our end state would be a single group with - damccorm - jrmccluskey - kennknowles - lostluck - abacn Thanks, Danny On Mon, Apr 17, 2023 at 12:24 PM Kerry Donny-Clark wrote: > +1, should there also be an update to remove folks who are not active > on the project? > Kerry > > On Mon, Apr 17, 2023 at 11:40 AM Jack McCluskey via dev < > dev@beam.apache.org> wrote: > >> +1 to simplifying the infra side, especially with an aim towards >> automating the processes we can. The more we can streamline and simplify >> the better. >> >> On Mon, Apr 17, 2023 at 11:18 AM Danny McCormick via dev < >> dev@beam.apache.org> wrote: >> >>> Hey everyone, in an effort to reduce the burden of running a Beam >>> release, a few committers (self included) have volunteered to try to >>> take a >>> larger role in releases (including both running them and contributing to >>> making them better going forward). To aid in that process, I would like >>> to >>> request that they all be added to our Beam DockerHub group. Those >>> committers are: >>> >>> - damccorm >>> - jrmccluskey >>> - kennknowles >>> - lostluck >>> - abacn >>> >>> At the same time, Infra would like us to reduce the number of people >>> with DockerHub seats to 5 because they have a limited number of seats >>> for >>> all of Apache. Currently, we have 2 groups taking up 10 seats: Beam >>> admin >>> and Beam maintainers. >>> >>> Beam admin has admin privileges over most (though not quite all) of >>> our DockerHub repos and includes: >>> >>> - aaltay >>> - hannahjiang >>> - kileysok >>> - pabloem >>> - robertwb >>> >>> Beam maintainers has write privileges and some additional admin >>> privileges and includes: >>> >>> - aaltay >>> - chamikaramj >>> - kennknowles >>> - kileysok >>> - robertwb >>> >>> To get down to 5 seats, I propose we consolidate to a single group >>> with admin privileges and add just the committers I mentioned since they >>> will likely be the most actively involved in the release process in the >>> short term. A future goal of mine is to automate the DockerHub release >>> steps so that we just need 2 dockerhub seats: 1 for the automation and 1 >>> for an easy manual fallback (probably for the PMC chair). >>> >>> If you have any concerns (or would like to help with this effort), >>> please respond here. Otherwise I will follow up with infra to make this >>> change in a day. >>> >>> Thanks, >>> Danny >>> >>
Re: [VOTE] Vendored Dependencies Release
I'm happy to announce that we have unanimously approved this release. There are 3 approving votes, 3 of which are binding: * Kenneth Knowles * Chamikara Jayalath * Robert Bradshaw There are no disapproving votes. Thanks everyone! On Mon, Apr 17, 2023 at 6:11 PM Robert Bradshaw wrote: > +1 > > On Mon, Apr 17, 2023 at 11:20 AM Chamikara Jayalath via dev < > dev@beam.apache.org> wrote: > >> +1 >> >> Thanks, >> Cham >> >> On Mon, Apr 17, 2023 at 11:04 AM Kenneth Knowles wrote: >> >>> +1 >>> >>> On Fri, Apr 14, 2023 at 1:30 PM Yi Hu via dev >>> wrote: >>> Please review the release of the following artifacts that we vendor: * beam-vendor-grpc-1_54_0 Hi everyone, Please review and vote on the release candidate #1 for the version 0.1, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) The complete staging area is available for your review, which includes: * the official Apache source release to be deployed to dist.apache.org [1], which is signed with the key with fingerprint 2011EC936303D9A1DB662EE1CB6974C8170405CB [2], * all artifacts to be deployed to the Maven Central Repository [3], * commit hash "a38d9b94a738e4c488e7339ae3710fd5e1dc119e" [4], The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Thanks, Release Manager [1] https://dist.apache.org/repos/dist/dev/beam/vendor/ [2] https://dist.apache.org/repos/dist/dev/beam/KEYS [3] https://repository.apache.org/content/repositories/orgapachebeam-1308/ [4] https://github.com/apache/beam/commit/a38d9b94a738e4c488e7339ae3710fd5e1dc119e -- Yi Hu, (he/him/his) Software Engineer 919-641-8436 <(919)%20641-8436>
Beam High Priority Issue Report (29)
This is your daily summary of Beam's current high priority issues that may need attention. See https://beam.apache.org/contribute/issue-priorities for the meaning and expectations around issue priorities. Unassigned P1 Issues: https://github.com/apache/beam/issues/26343 [Bug]: apache_beam.io.gcp.bigquery_read_it_test.ReadAllBQTests.test_read_queries is flaky https://github.com/apache/beam/issues/26329 [Bug]: BigQuerySourceBase does not propagate a Coder to AvroSource https://github.com/apache/beam/issues/26126 [Failing Test]: beam_PostCommit_XVR_Samza permared validatesCrossLanguageRunnerGoUsingJava TestDebeziumIO_BasicRead https://github.com/apache/beam/issues/26041 [Bug]: Unable to create exactly-once Flink pipeline with stream source and file sink https://github.com/apache/beam/issues/25975 [Bug]: Reducing parallelism in FlinkRunner leads to a data loss https://github.com/apache/beam/issues/24776 [Bug]: Race condition in Python SDK Harness ProcessBundleProgress https://github.com/apache/beam/issues/24389 [Failing Test]: HadoopFormatIOElasticTest.classMethod ExceptionInInitializerError ContainerFetchException https://github.com/apache/beam/issues/24313 [Flaky]: apache_beam/runners/portability/portable_runner_test.py::PortableRunnerTestWithSubprocesses::test_pardo_state_with_custom_key_coder https://github.com/apache/beam/issues/23944 beam_PreCommit_Python_Cron regularily failing - test_pardo_large_input flaky https://github.com/apache/beam/issues/23709 [Flake]: Spark batch flakes in ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElement and ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundle https://github.com/apache/beam/issues/22913 [Bug]: beam_PostCommit_Java_ValidatesRunner_Flink is flakes in org.apache.beam.sdk.transforms.GroupByKeyTest$BasicTests.testAfterProcessingTimeContinuationTriggerUsingState https://github.com/apache/beam/issues/22605 [Bug]: Beam Python failure for dataflow_exercise_metrics_pipeline_test.ExerciseMetricsPipelineTest.test_metrics_it https://github.com/apache/beam/issues/21706 Flaky timeout in github Python unit test action StatefulDoFnOnDirectRunnerTest.test_dynamic_timer_clear_then_set_timer https://github.com/apache/beam/issues/21645 beam_PostCommit_XVR_GoUsingJava_Dataflow fails on some test transforms https://github.com/apache/beam/issues/21643 FnRunnerTest with non-trivial (order 1000 elements) numpy input flakes in non-cython environment https://github.com/apache/beam/issues/21469 beam_PostCommit_XVR_Flink flaky: Connection refused https://github.com/apache/beam/issues/21424 Java VR (Dataflow, V2, Streaming) failing: ParDoTest$TimestampTests/OnWindowExpirationTests https://github.com/apache/beam/issues/21262 Python AfterAny, AfterAll do not follow spec https://github.com/apache/beam/issues/21260 Python DirectRunner does not emit data at GC time https://github.com/apache/beam/issues/21121 apache_beam.examples.streaming_wordcount_it_test.StreamingWordCountIT.test_streaming_wordcount_it flakey https://github.com/apache/beam/issues/21104 Flaky: apache_beam.runners.portability.fn_api_runner.fn_runner_test.FnApiRunnerTestWithGrpcAndMultiWorkers https://github.com/apache/beam/issues/20976 apache_beam.runners.portability.flink_runner_test.FlinkRunnerTestOptimized.test_flink_metrics is flaky https://github.com/apache/beam/issues/20108 Python direct runner doesn't emit empty pane when it should https://github.com/apache/beam/issues/19814 Flink streaming flakes in ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundleStateful and ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElementStateful https://github.com/apache/beam/issues/19465 Explore possibilities to lower in-use IP address quota footprint. P1 Issues with no update in the last week: https://github.com/apache/beam/issues/23525 [Bug]: Default PubsubMessage coder will drop message id and orderingKey https://github.com/apache/beam/issues/21714 PulsarIOTest.testReadFromSimpleTopic is very flaky https://github.com/apache/beam/issues/21708 beam_PostCommit_Java_DataflowV2, testBigQueryStorageWrite30MProto failing consistently https://github.com/apache/beam/issues/21476 WriteToBigQuery Dynamic table destinations returns wrong tableId
