From dev-return-24033-archive-asf-public=cust-asf.ponee.io@beam.apache.org Wed Jul 8 03:54:19 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id CECB1180656 for ; Wed, 8 Jul 2020 05:54:18 +0200 (CEST) Received: (qmail 65875 invoked by uid 500); 8 Jul 2020 03:54:17 -0000 Mailing-List: contact dev-help@beam.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@beam.apache.org Delivered-To: mailing list dev@beam.apache.org Received: (qmail 65860 invoked by uid 99); 8 Jul 2020 03:54:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jul 2020 03:54:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 84DAF18144F for ; Wed, 8 Jul 2020 03:54:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -14.282 X-Spam-Level: X-Spam-Status: No, score=-14.282 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.2, KAM_SHORT=0.001, MISSING_HEADERS=1.207, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=google.com Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id sVbPdfyycUhB for ; Wed, 8 Jul 2020 03:54:13 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1450:4864:20::12d; helo=mail-lf1-x12d.google.com; envelope-from=valentyn@google.com; receiver= Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id 01EC27F667 for ; Wed, 8 Jul 2020 03:54:12 +0000 (UTC) Received: by mail-lf1-x12d.google.com with SMTP id g139so26046599lfd.10 for ; Tue, 07 Jul 2020 20:54:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:cc; bh=Yxs1NP6gIp5SdAgDafuyb2btLA+4MLfmhx1UNcZKNv0=; b=S7EHPLZ1rdi4+JFxxYl901+oK2AsGusi0lI1ner+L33imDHQss363kVGrghIOrCr9s 6GtHaiG5R1osH1PT/qDmKHyeqtaU9qkQAd3goDQZQVtqg2zpWcLbw0QLPsraM0910i7f AADSxPP9V8pGrEMoaP/NX4ON8gu+oo6olBrL3nPbJWAiAm8OXmQ3rqpgSYcA7uPtEWym 1dAzNA7xPIql4MO04nTmmSc6NKIH3jUr2QmSwmzmfKkgEaoY9/V5DtPbDZffsj60DD7q sXh0f4cocbiz1hi8cvS+DIFpmTxo8L7dGMKTbIIBdoWeIyYYB3IANhgosFfhUh0QLt1N qrIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:cc; bh=Yxs1NP6gIp5SdAgDafuyb2btLA+4MLfmhx1UNcZKNv0=; b=GMyuwYnMdpkn3A6tsydXabBo1bKFRyJmZeYzX9Bq/th6hF3su7axleiNClZ6lwfFPE +X1PCNZl1vZyGxNQTzrARdBWUZ+UOgLDLg7cSfM5FOR0S+6C4+/gFL5QkHr9GgqGZQZD uigt2rVrhX1WYt/Pj8FMuGwONlUG9EbtoJ1TgS79vpo0setnAvgTRjp3UVPTV9tpQRi/ 2zFggwXcX84HDJJ34ENv/Pffm7WFXGbZCa3bbyuMGbvKIcWgB+g6Ns/dwC1F6/LNnh7s OIxdLHbOKmtAKqXuL65kGFe/jan4htq84wCQRT1ghiQ0DgqWVrq3pbmUCB9FjC39Z31p BJCQ== X-Gm-Message-State: AOAM531FyfaDkDBvyqNvhurtdbG8W0XklGi67jKDnLfr49aM1FaZDvsi M9w4DE2/6XxKr+6tOmpNbiZtFb8+b5GrDeC/vmUWCZ6Nignmyg== X-Google-Smtp-Source: ABdhPJzGcDrLDt0A0N5eko7PicABkVP8DYSwcPXT7Qw9WtwNr8NWHRfazxj7Ak8uucwNMFK4dsNZXhoLCE95v/oAwCA= X-Received: by 2002:ac2:5e6e:: with SMTP id a14mr34915041lfr.79.1594180445788; Tue, 07 Jul 2020 20:54:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Valentyn Tymofieiev Date: Tue, 7 Jul 2020 20:53:28 -0700 Message-ID: Subject: Re: [PROPOSAL] Preparing for Beam 2.23.0 release Cc: dev Content-Type: multipart/alternative; boundary="0000000000002e53f105a9e60fd2" --0000000000002e53f105a9e60fd2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable There are some test failures on the release branch that need to be addressed. I may need help with a Samza ValidatesRunner failure [1]. It has been failing since at least June 24 [2]. 1. Did this issue come up during earlier releases? 2. Do we know why this suite is not visible in Beam metrics dashboard[3]? If it was, it would have been easier to see when it started failing. Can Samza runner maintainers please advise? Thank you. [1] https://issues.apache.org/jira/browse/BEAM-10424 [2] https://ci-beam.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza/ [3] http://metrics.beam.apache.org/d/D81lW0pmk/post-commit-test-reliability?org= Id=3D1 On Tue, Jul 7, 2020 at 8:01 PM Valentyn Tymofieiev wrote: > So far the release process is going well. > > Currently running several release validation suites[1], and plan to send > out an RC once these are completed. > > Here is how the community can help: > > 1. If there is a test suite that you've added recently, but did not add i= t > to .test-infra/jenkins/README.md > , > feel free to trigger it on the PR[1], and add the trigger command to > README.MD. > 2. Please add any noteworthy changes to the change log [3]. > 3. I have received several inquiries off-the-list about > cherry-picking changes to the release branch (which would be blocking > further steps in the release process), so I would like to remind the > current guideline[4]: *An issue should not block the release if the > problem exists in the current released version or is a bug in new > functionality that does not exist in the current released version. It > should be a blocker if the bug is a regression between the currently > released version and the release in progress and has no easy workaround.* > > Thanks, > Valentyn > > [1] https://github.com/apache/beam/pull/12194 > [2] > https://github.com/apache/beam/blob/master/.test-infra/jenkins/README.md > [3] https://github.com/apache/beam/blob/master/CHANGES.md > [4] > https://beam.apache.org/contribute/release-guide/#4-triage-release-blocki= ng-issues-in-jira > > > > On Mon, Jul 6, 2020 at 9:47 AM Ahmet Altay wrote: > >> Done. >> >> On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev >> wrote: >> >>> Can somebody please add my pypi username (tvalentyn) to the list of >>> apache-beam maintainers on PyPi: https://pypi.org/project/apache-beam/ >>> ? >>> Thank you! >>> >>> On Wed, Jul 1, 2020 at 4:51 PM Valentyn Tymofieiev >>> wrote: >>> >>>> Release branch has been cut. >>>> >>>> As a reminder, please do not merge commits into the release branch >>>> directly, instead, loop in the release manager if any cherry-picks are >>>> required. >>>> >>>> Thank you. >>>> >>>> On Wed, Jul 1, 2020 at 9:25 AM Valentyn Tymofieiev >>>> wrote: >>>> >>>>> Great, thank you Tobiasz, I will take a look. >>>>> >>>>> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz K=C4=99dzierski < >>>>> tobiasz.kedzierski@polidea.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I've just created PR introducing usage of GH-Actions to release >>>>>> process >>>>>> https://github.com/apache/beam/pull/12150 >>>>>> >>>>>> Let me know what you think, maybe you have some suggestions on what >>>>>> may be improved. >>>>>> >>>>>> BR >>>>>> Tobiasz >>>>>> >>>>>> On Wed, Jul 1, 2020 at 6:08 AM Ahmet Altay wrote: >>>>>> >>>>>>> Valentyn, >>>>>>> >>>>>>> +tobiasz.kedzierski@polidea.com ad= ded >>>>>>> a github action for building python wheel files ( >>>>>>> https://github.com/apache/beam/pull/11877). You should be able to >>>>>>> build the wheel files using this github action instead of using the >>>>>>> beam-wheels repo and Travis. Please give it a try during the releas= e >>>>>>> process. >>>>>>> >>>>>>> Ahmet >>>>>>> >>>>>>> On Tue, Jun 23, 2020 at 7:27 PM Valentyn Tymofieiev < >>>>>>> valentyn@google.com> wrote: >>>>>>> >>>>>>>> Friendly reminder that the release cut is slated next week. >>>>>>>> >>>>>>>> If you are aware of *release-blocking* issues, please open a JIRA >>>>>>>> and set the "Fix version" to be 2.23.0. >>>>>>>> >>>>>>>> Please do not set "Fix version" for open non-blocking issues, >>>>>>>> instead set "Fix version" once the issue is actually resolved. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Valentyn >>>>>>>> >>>>>>>> On Mon, Jun 15, 2020 at 1:14 PM Rui Wang wrote= : >>>>>>>> >>>>>>>>> Thank you Valentyn! >>>>>>>>> >>>>>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Thank you Valentyn! >>>>>>>>>> >>>>>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Thanks Valentyn! >>>>>>>>>>> >>>>>>>>>>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver < >>>>>>>>>>> kcweaver@google.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Sounds good, thanks Valentyn! >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Jun 15, 2020 at 12:31 PM Valentyn Tymofieiev < >>>>>>>>>>>> valentyn@google.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi all, >>>>>>>>>>>>> >>>>>>>>>>>>> According to the Beam release calendar [1], the next (2.23.0) >>>>>>>>>>>>> release branch cut is scheduled for July 1. >>>>>>>>>>>>> >>>>>>>>>>>>> I would be happy to help with this release and volunteer >>>>>>>>>>>>> myself to be the next release manager. >>>>>>>>>>>>> >>>>>>>>>>>>> As usual, the plan is to cut the branch on that date, >>>>>>>>>>>>> and cherrypick release-blocking fixes afterwards if any. >>>>>>>>>>>>> >>>>>>>>>>>>> Any unresolved release blocking JIRA issues for 2.23.0 should >>>>>>>>>>>>> have their "Fix Version/s" marked as "2.23.0". >>>>>>>>>>>>> >>>>>>>>>>>>> Any comments or objections? >>>>>>>>>>>>> >>>>>>>>>>>>> [1] >>>>>>>>>>>>> https://calendar.google.com/calendar/embed?src=3D0p73sl034k80= oob7seouanigd0%40group.calendar.google.com >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Tobiasz K=C4=99dzierski >>>>>> Polidea | Junior Software Engineer >>>>>> >>>>>> E: tobiasz.kedzierski@polidea.com >>>>>> [image: Polidea] >>>>>> >>>>>> Check out our projects! >>>>>> [image: Github] [image: Facebook] >>>>>> [image: Twitter] >>>>>> [image: Linkedin] >>>>>> [image: Instagram] >>>>>> [image: Behance] >>>>>> [image: dribbble] >>>>>> >>>>>> >>>>> --0000000000002e53f105a9e60fd2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
There are some test failures on the release branch that ne= ed to be addressed.=C2=A0

I may need help with a Samza V= alidatesRunner failure [1]. It has been failing since at least June 24 [2].= =C2=A0

1. Did this issue come up during earlier re= leases?=C2=A0
2. Do we know why this suite is not visible in Beam= metrics dashboard[3]? If it was, it would have been easier to see when it = started failing.=C2=A0

Can Samza runner maintainer= s please advise?

Thank you.

[1]=C2=A0ht= tps://issues.apache.org/jira/browse/BEAM-10424

On Tue, Jul 7, 2020 at 8:01 PM Valentyn Tymofieiev <= valentyn@google.com> wrote:
=
So far the release process is going well.=C2=A0<= br>

Currently running several release validation suites[= 1], and plan to send out an RC once these are completed.=C2=A0
Here is how the community can help:

1= . If there is a test suite that you've added recently, but did not add = it to=C2=A0.test-infra/jenkins/README.md, f= eel free to trigger it on the PR[1], and add the trigger command to README.= MD.
2. Please add any noteworthy changes to the change log [3].
3. I have received=C2=A0several inquiries off-the-list about cherr= y-picking=C2=A0changes to the release branch (which would be blocking furth= er steps in the release process), so I would like to remind the current gui= deline[4]:=C2=A0An issue should not block the release if the probl= em exists in the current released version or is a bug in new functionality = that does not exist in the current released version. It should be a blocker= if the bug is a regression between the currently released version and the = release in progress and has no easy workaround.
=

Thanks,
Valentyn

<= /div>

On Mon, Jul 6, 2020 at 9:47 AM Ahmet Altay <altay@google.com> w= rote:
Done.

On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev <valentyn@google.com> wrote:
Thank you!

On Wed, Jul 1, 2020 = at 4:51 PM Valentyn Tymofieiev <valentyn@google.com> wrote:
Release branch has bee= n cut.=C2=A0

As a reminder, please do not merge commits = into the release branch directly, instead, loop in the release manager if a= ny cherry-picks are required.=C2=A0

Thank you.
=

On Wed, Jul 1, 2020 at 9:25 AM Valentyn Tymofieiev <valentyn@google.com> wrot= e:
Great, thank you Tobiasz, I will take a=C2=A0look.

On Wed, Jul 1, 2020 = at 7:27 AM Tobiasz K=C4=99dzierski <tobiasz.kedzierski@polidea.com> wrot= e:
Hi,

I've just created PR introducing usage of GH-Actions to = release process
https://github.com/apache/beam/pull/12150

Let me= know what you think, maybe you have some suggestions on what may be improv= ed.

BR
Tobiasz

On Wed, Jul 1, 2020 at 6:08 AM Ahmet Altay &l= t;altay@google.com> wrote:
Valentyn,

+tobiasz.kedzierski@polidea.com=C2=A0added a github action for bu= ilding python wheel files (https://github.com/apache/beam/pull/11877). You= should be able to build the wheel files using this github action instead o= f using the beam-wheels repo and Travis. Please give it a try during the re= lease process.

Ahmet

On Tue, Jun 23, 2020= at 7:27 PM Valentyn Tymofieiev <valentyn@google.com> wrote:
Friendly reminder tha= t the release cut is slated next week.=C2=A0

If you are aware = of *release-blocking* issues, please open a JIRA and set the "Fix vers= ion" to be 2.23.0.

Please do not set "Fi= x version" for open non-blocking issues, instead set "Fix version= " once the issue is actually resolved.

= Thanks,
Valentyn

On Mon, Jun 15, 2020 at 1:14 PM Rui Wang &l= t;ruwang@google.com<= /a>> wrote:
<= div dir=3D"ltr">Thank you Valentyn!

On Mon, Jun 15, 2020 at 1:08 PM Ahmet Al= tay <altay@google.= com> wrote:
Thank you Valentyn!

On Mon, Jun 15, 2020 at 12:46 PM= Ankur Goenka <go= enka@google.com> wrote:
Thanks Valentyn!

On Mon, Jun 15, 2020 at 12:= 41 PM Kyle Weaver <kcweaver@google.com> wrote:
Sounds good, thanks Valentyn!
=
On Mon= , Jun 15, 2020 at 12:31 PM Valentyn Tymofieiev <valentyn@google.com> wrote:
Hi all= ,

According to the Beam release calendar=C2=A0[1], the n= ext (2.23.0) release branch cut is scheduled for July 1.

I would be happy to help with this release and=C2=A0volunteer<= /span>=C2=A0myself=C2=A0to be the next release=C2=A0manager.

As usual, the plan= is to cut the branch on that date, and=C2=A0cherrypick=C2=A0release-<= /span>blocking fixes afterwards if any.

<= span style=3D"color:rgb(0,0,0)">Any unresolved release blocking JIRA issues= for 2.23.0 should have their "Fix Version/s" marked as "2.2= 3.0".

Any comments or objections?=C2=A0




--
<= /tr>

Tob= iasz K=C4=99dzierski
Polidea=C2=A0| Junior Software Engineer

E:=C2=A0tob= iasz.kedzierski@polidea.com

Check out=C2=A0o= ur projects!

3D"G=3D"Facebook"= 3D"Twitter"3D"Linkedin"3D"Instagram"3D"B=3D"dribbble"
--0000000000002e53f105a9e60fd2--