You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Valentyn Tymofieiev <va...@google.com> on 2020/06/15 19:31:05 UTC
[PROPOSAL] Preparing for Beam 2.23.0 release
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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Valentyn Tymofieiev <va...@google.com>.
Thanks, Pablo, much appreciated!
On Wed, Jul 29, 2020 at 3:44 PM Pablo Estrada <pa...@google.com> wrote:
> I'll get on this. Thanks!
> -P.
>
> On Wed, Jul 29, 2020 at 3:40 PM Valentyn Tymofieiev <va...@google.com>
> wrote:
>
>> I need help from a PMC member to perform PMC-only actions in the release
>> guide[1].
>>
>> Also, a PMC could help update the Docker Hub page for Python 3.8 [2],
>> since we have released Py3.8 container images now. We can also remove
>> references to Apache Apex from this and other hub pages.
>>
>> Thank you!
>>
>> [1]
>> https://beam.apache.org/contribute/release-guide/#pmc-only-finalization
>> [2] https://hub.docker.com/r/apache/beam_python3.8_sdk
>>
>>
>> On Wed, Jul 8, 2020 at 10:33 AM Valentyn Tymofieiev <va...@google.com>
>> wrote:
>>
>>> Thank you, Kyle!
>>>
>>> On Wed, Jul 8, 2020 at 10:03 AM Kyle Weaver <kc...@google.com> wrote:
>>>
>>>> > I may need help with a Samza ValidatesRunner failure [1]. It has been
>>>> failing since at least June 24 [2].
>>>>
>>>> Looks like a duplicate of
>>>> https://issues.apache.org/jira/browse/BEAM-10025.
>>>>
>>>> > 1. Did this issue come up during earlier releases?
>>>>
>>>> Yes, this affected the 2.21 and 2.22 releases. tl;dr it was a newly
>>>> added test, so it most likely does not represent a regression.
>>>>
>>>> On Tue, Jul 7, 2020 at 8:54 PM Valentyn Tymofieiev <va...@google.com>
>>>> wrote:
>>>>
>>>>> 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?orgId=1
>>>>>
>>>>>
>>>>> On Tue, Jul 7, 2020 at 8:01 PM Valentyn Tymofieiev <
>>>>> valentyn@google.com> 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 it to .test-infra/jenkins/README.md
>>>>>> <https://github.com/apache/beam/blob/master/.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-blocking-issues-in-jira
>>>>>> <https://www.google.com/url?q=https://beam.apache.org/contribute/release-guide/%234-triage-release-blocking-issues-in-jira&sa=D&source=hangouts&ust=1594262748653000&usg=AFQjCNFZYd0JpuYxxvj44rxOu6f6twr76A>
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 6, 2020 at 9:47 AM Ahmet Altay <al...@google.com> wrote:
>>>>>>
>>>>>>> Done.
>>>>>>>
>>>>>>> On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev <
>>>>>>> valentyn@google.com> 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 <
>>>>>>>> valentyn@google.com> 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 <
>>>>>>>>> valentyn@google.com> wrote:
>>>>>>>>>
>>>>>>>>>> Great, thank you Tobiasz, I will take a look.
>>>>>>>>>>
>>>>>>>>>> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
>>>>>>>>>> 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 <al...@google.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Valentyn,
>>>>>>>>>>>>
>>>>>>>>>>>> +tobiasz.kedzierski@polidea.com
>>>>>>>>>>>> <to...@polidea.com> added 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 release
>>>>>>>>>>>> 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 <ru...@google.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <
>>>>>>>>>>>>>>> goenka@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 [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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>> Tobiasz Kędzierski
>>>>>>>>>>> Polidea <https://www.polidea.com/> | Junior Software Engineer
>>>>>>>>>>>
>>>>>>>>>>> E: tobiasz.kedzierski@polidea.com
>>>>>>>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>>>>>>>
>>>>>>>>>>> Check out our projects! <https://www.polidea.com/our-work>
>>>>>>>>>>> [image: Github] <https://github.com/Polidea> [image: Facebook]
>>>>>>>>>>> <https://www.facebook.com/Polidea.Software> [image: Twitter]
>>>>>>>>>>> <https://twitter.com/polidea> [image: Linkedin]
>>>>>>>>>>> <https://www.linkedin.com/company/polidea> [image: Instagram]
>>>>>>>>>>> <https://instagram.com/polidea> [image: Behance]
>>>>>>>>>>> <https://www.behance.net/polidea> [image: dribbble]
>>>>>>>>>>> <https://dribbble.com/polideadesign>
>>>>>>>>>>>
>>>>>>>>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Pablo Estrada <pa...@google.com>.
I'll get on this. Thanks!
-P.
On Wed, Jul 29, 2020 at 3:40 PM Valentyn Tymofieiev <va...@google.com>
wrote:
> I need help from a PMC member to perform PMC-only actions in the release
> guide[1].
>
> Also, a PMC could help update the Docker Hub page for Python 3.8 [2],
> since we have released Py3.8 container images now. We can also remove
> references to Apache Apex from this and other hub pages.
>
> Thank you!
>
> [1]
> https://beam.apache.org/contribute/release-guide/#pmc-only-finalization
> [2] https://hub.docker.com/r/apache/beam_python3.8_sdk
>
>
> On Wed, Jul 8, 2020 at 10:33 AM Valentyn Tymofieiev <va...@google.com>
> wrote:
>
>> Thank you, Kyle!
>>
>> On Wed, Jul 8, 2020 at 10:03 AM Kyle Weaver <kc...@google.com> wrote:
>>
>>> > I may need help with a Samza ValidatesRunner failure [1]. It has been
>>> failing since at least June 24 [2].
>>>
>>> Looks like a duplicate of
>>> https://issues.apache.org/jira/browse/BEAM-10025.
>>>
>>> > 1. Did this issue come up during earlier releases?
>>>
>>> Yes, this affected the 2.21 and 2.22 releases. tl;dr it was a newly
>>> added test, so it most likely does not represent a regression.
>>>
>>> On Tue, Jul 7, 2020 at 8:54 PM Valentyn Tymofieiev <va...@google.com>
>>> wrote:
>>>
>>>> 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?orgId=1
>>>>
>>>>
>>>> On Tue, Jul 7, 2020 at 8:01 PM Valentyn Tymofieiev <va...@google.com>
>>>> 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 it to .test-infra/jenkins/README.md
>>>>> <https://github.com/apache/beam/blob/master/.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-blocking-issues-in-jira
>>>>> <https://www.google.com/url?q=https://beam.apache.org/contribute/release-guide/%234-triage-release-blocking-issues-in-jira&sa=D&source=hangouts&ust=1594262748653000&usg=AFQjCNFZYd0JpuYxxvj44rxOu6f6twr76A>
>>>>>
>>>>>
>>>>> On Mon, Jul 6, 2020 at 9:47 AM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>> Done.
>>>>>>
>>>>>> On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev <
>>>>>> valentyn@google.com> 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 <
>>>>>>> valentyn@google.com> 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 <
>>>>>>>> valentyn@google.com> wrote:
>>>>>>>>
>>>>>>>>> Great, thank you Tobiasz, I will take a look.
>>>>>>>>>
>>>>>>>>> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
>>>>>>>>> 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 <al...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Valentyn,
>>>>>>>>>>>
>>>>>>>>>>> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added
>>>>>>>>>>> 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 release
>>>>>>>>>>> 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 <ru...@google.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <
>>>>>>>>>>>>>> goenka@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 [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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>> Tobiasz Kędzierski
>>>>>>>>>> Polidea <https://www.polidea.com/> | Junior Software Engineer
>>>>>>>>>>
>>>>>>>>>> E: tobiasz.kedzierski@polidea.com
>>>>>>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>>>>>>
>>>>>>>>>> Check out our projects! <https://www.polidea.com/our-work>
>>>>>>>>>> [image: Github] <https://github.com/Polidea> [image: Facebook]
>>>>>>>>>> <https://www.facebook.com/Polidea.Software> [image: Twitter]
>>>>>>>>>> <https://twitter.com/polidea> [image: Linkedin]
>>>>>>>>>> <https://www.linkedin.com/company/polidea> [image: Instagram]
>>>>>>>>>> <https://instagram.com/polidea> [image: Behance]
>>>>>>>>>> <https://www.behance.net/polidea> [image: dribbble]
>>>>>>>>>> <https://dribbble.com/polideadesign>
>>>>>>>>>>
>>>>>>>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Valentyn Tymofieiev <va...@google.com>.
I need help from a PMC member to perform PMC-only actions in the release
guide[1].
Also, a PMC could help update the Docker Hub page for Python 3.8 [2], since
we have released Py3.8 container images now. We can also remove references
to Apache Apex from this and other hub pages.
Thank you!
[1] https://beam.apache.org/contribute/release-guide/#pmc-only-finalization
[2] https://hub.docker.com/r/apache/beam_python3.8_sdk
On Wed, Jul 8, 2020 at 10:33 AM Valentyn Tymofieiev <va...@google.com>
wrote:
> Thank you, Kyle!
>
> On Wed, Jul 8, 2020 at 10:03 AM Kyle Weaver <kc...@google.com> wrote:
>
>> > I may need help with a Samza ValidatesRunner failure [1]. It has been
>> failing since at least June 24 [2].
>>
>> Looks like a duplicate of
>> https://issues.apache.org/jira/browse/BEAM-10025.
>>
>> > 1. Did this issue come up during earlier releases?
>>
>> Yes, this affected the 2.21 and 2.22 releases. tl;dr it was a newly added
>> test, so it most likely does not represent a regression.
>>
>> On Tue, Jul 7, 2020 at 8:54 PM Valentyn Tymofieiev <va...@google.com>
>> wrote:
>>
>>> 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?orgId=1
>>>
>>>
>>> On Tue, Jul 7, 2020 at 8:01 PM Valentyn Tymofieiev <va...@google.com>
>>> 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
>>>> it to .test-infra/jenkins/README.md
>>>> <https://github.com/apache/beam/blob/master/.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-blocking-issues-in-jira
>>>> <https://www.google.com/url?q=https://beam.apache.org/contribute/release-guide/%234-triage-release-blocking-issues-in-jira&sa=D&source=hangouts&ust=1594262748653000&usg=AFQjCNFZYd0JpuYxxvj44rxOu6f6twr76A>
>>>>
>>>>
>>>> On Mon, Jul 6, 2020 at 9:47 AM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> Done.
>>>>>
>>>>> On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev <
>>>>> valentyn@google.com> 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 <
>>>>>> valentyn@google.com> 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 <
>>>>>>> valentyn@google.com> wrote:
>>>>>>>
>>>>>>>> Great, thank you Tobiasz, I will take a look.
>>>>>>>>
>>>>>>>> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
>>>>>>>> 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 <al...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Valentyn,
>>>>>>>>>>
>>>>>>>>>> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added
>>>>>>>>>> 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 release
>>>>>>>>>> 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 <ru...@google.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <
>>>>>>>>>>>>> goenka@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 [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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> Tobiasz Kędzierski
>>>>>>>>> Polidea <https://www.polidea.com/> | Junior Software Engineer
>>>>>>>>>
>>>>>>>>> E: tobiasz.kedzierski@polidea.com
>>>>>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>>>>>
>>>>>>>>> Check out our projects! <https://www.polidea.com/our-work>
>>>>>>>>> [image: Github] <https://github.com/Polidea> [image: Facebook]
>>>>>>>>> <https://www.facebook.com/Polidea.Software> [image: Twitter]
>>>>>>>>> <https://twitter.com/polidea> [image: Linkedin]
>>>>>>>>> <https://www.linkedin.com/company/polidea> [image: Instagram]
>>>>>>>>> <https://instagram.com/polidea> [image: Behance]
>>>>>>>>> <https://www.behance.net/polidea> [image: dribbble]
>>>>>>>>> <https://dribbble.com/polideadesign>
>>>>>>>>>
>>>>>>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Valentyn Tymofieiev <va...@google.com>.
Thank you, Kyle!
On Wed, Jul 8, 2020 at 10:03 AM Kyle Weaver <kc...@google.com> wrote:
> > I may need help with a Samza ValidatesRunner failure [1]. It has been
> failing since at least June 24 [2].
>
> Looks like a duplicate of https://issues.apache.org/jira/browse/BEAM-10025
> .
>
> > 1. Did this issue come up during earlier releases?
>
> Yes, this affected the 2.21 and 2.22 releases. tl;dr it was a newly added
> test, so it most likely does not represent a regression.
>
> On Tue, Jul 7, 2020 at 8:54 PM Valentyn Tymofieiev <va...@google.com>
> wrote:
>
>> 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?orgId=1
>>
>>
>> On Tue, Jul 7, 2020 at 8:01 PM Valentyn Tymofieiev <va...@google.com>
>> 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
>>> it to .test-infra/jenkins/README.md
>>> <https://github.com/apache/beam/blob/master/.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-blocking-issues-in-jira
>>> <https://www.google.com/url?q=https://beam.apache.org/contribute/release-guide/%234-triage-release-blocking-issues-in-jira&sa=D&source=hangouts&ust=1594262748653000&usg=AFQjCNFZYd0JpuYxxvj44rxOu6f6twr76A>
>>>
>>>
>>> On Mon, Jul 6, 2020 at 9:47 AM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Done.
>>>>
>>>> On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev <va...@google.com>
>>>> 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 <
>>>>> valentyn@google.com> 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 <
>>>>>> valentyn@google.com> wrote:
>>>>>>
>>>>>>> Great, thank you Tobiasz, I will take a look.
>>>>>>>
>>>>>>> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
>>>>>>> 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 <al...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Valentyn,
>>>>>>>>>
>>>>>>>>> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added
>>>>>>>>> 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 release
>>>>>>>>> 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 <ru...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <
>>>>>>>>>>>> goenka@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 [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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Tobiasz Kędzierski
>>>>>>>> Polidea <https://www.polidea.com/> | Junior Software Engineer
>>>>>>>>
>>>>>>>> E: tobiasz.kedzierski@polidea.com
>>>>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>>>>
>>>>>>>> Check out our projects! <https://www.polidea.com/our-work>
>>>>>>>> [image: Github] <https://github.com/Polidea> [image: Facebook]
>>>>>>>> <https://www.facebook.com/Polidea.Software> [image: Twitter]
>>>>>>>> <https://twitter.com/polidea> [image: Linkedin]
>>>>>>>> <https://www.linkedin.com/company/polidea> [image: Instagram]
>>>>>>>> <https://instagram.com/polidea> [image: Behance]
>>>>>>>> <https://www.behance.net/polidea> [image: dribbble]
>>>>>>>> <https://dribbble.com/polideadesign>
>>>>>>>>
>>>>>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Kyle Weaver <kc...@google.com>.
> I may need help with a Samza ValidatesRunner failure [1]. It has been
failing since at least June 24 [2].
Looks like a duplicate of https://issues.apache.org/jira/browse/BEAM-10025.
> 1. Did this issue come up during earlier releases?
Yes, this affected the 2.21 and 2.22 releases. tl;dr it was a newly added
test, so it most likely does not represent a regression.
On Tue, Jul 7, 2020 at 8:54 PM Valentyn Tymofieiev <va...@google.com>
wrote:
> 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?orgId=1
>
>
> On Tue, Jul 7, 2020 at 8:01 PM Valentyn Tymofieiev <va...@google.com>
> 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
>> it to .test-infra/jenkins/README.md
>> <https://github.com/apache/beam/blob/master/.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-blocking-issues-in-jira
>> <https://www.google.com/url?q=https://beam.apache.org/contribute/release-guide/%234-triage-release-blocking-issues-in-jira&sa=D&source=hangouts&ust=1594262748653000&usg=AFQjCNFZYd0JpuYxxvj44rxOu6f6twr76A>
>>
>>
>> On Mon, Jul 6, 2020 at 9:47 AM Ahmet Altay <al...@google.com> wrote:
>>
>>> Done.
>>>
>>> On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev <va...@google.com>
>>> 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 <va...@google.com>
>>>> 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 <
>>>>> valentyn@google.com> wrote:
>>>>>
>>>>>> Great, thank you Tobiasz, I will take a look.
>>>>>>
>>>>>> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
>>>>>> 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 <al...@google.com> wrote:
>>>>>>>
>>>>>>>> Valentyn,
>>>>>>>>
>>>>>>>> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added
>>>>>>>> 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 release
>>>>>>>> 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 <ru...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>
>>>>>>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@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 [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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Tobiasz Kędzierski
>>>>>>> Polidea <https://www.polidea.com/> | Junior Software Engineer
>>>>>>>
>>>>>>> E: tobiasz.kedzierski@polidea.com
>>>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>>>
>>>>>>> Check out our projects! <https://www.polidea.com/our-work>
>>>>>>> [image: Github] <https://github.com/Polidea> [image: Facebook]
>>>>>>> <https://www.facebook.com/Polidea.Software> [image: Twitter]
>>>>>>> <https://twitter.com/polidea> [image: Linkedin]
>>>>>>> <https://www.linkedin.com/company/polidea> [image: Instagram]
>>>>>>> <https://instagram.com/polidea> [image: Behance]
>>>>>>> <https://www.behance.net/polidea> [image: dribbble]
>>>>>>> <https://dribbble.com/polideadesign>
>>>>>>>
>>>>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Valentyn Tymofieiev <va...@google.com>.
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?orgId=1
On Tue, Jul 7, 2020 at 8:01 PM Valentyn Tymofieiev <va...@google.com>
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 it
> to .test-infra/jenkins/README.md
> <https://github.com/apache/beam/blob/master/.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-blocking-issues-in-jira
> <https://www.google.com/url?q=https://beam.apache.org/contribute/release-guide/%234-triage-release-blocking-issues-in-jira&sa=D&source=hangouts&ust=1594262748653000&usg=AFQjCNFZYd0JpuYxxvj44rxOu6f6twr76A>
>
>
> On Mon, Jul 6, 2020 at 9:47 AM Ahmet Altay <al...@google.com> wrote:
>
>> Done.
>>
>> On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev <va...@google.com>
>> 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 <va...@google.com>
>>> 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 <va...@google.com>
>>>> wrote:
>>>>
>>>>> Great, thank you Tobiasz, I will take a look.
>>>>>
>>>>> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
>>>>> 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 <al...@google.com> wrote:
>>>>>>
>>>>>>> Valentyn,
>>>>>>>
>>>>>>> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added
>>>>>>> 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 release
>>>>>>> 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 <ru...@google.com> wrote:
>>>>>>>>
>>>>>>>>> Thank you Valentyn!
>>>>>>>>>
>>>>>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Thank you Valentyn!
>>>>>>>>>>
>>>>>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@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 [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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Tobiasz Kędzierski
>>>>>> Polidea <https://www.polidea.com/> | Junior Software Engineer
>>>>>>
>>>>>> E: tobiasz.kedzierski@polidea.com
>>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>>
>>>>>> Check out our projects! <https://www.polidea.com/our-work>
>>>>>> [image: Github] <https://github.com/Polidea> [image: Facebook]
>>>>>> <https://www.facebook.com/Polidea.Software> [image: Twitter]
>>>>>> <https://twitter.com/polidea> [image: Linkedin]
>>>>>> <https://www.linkedin.com/company/polidea> [image: Instagram]
>>>>>> <https://instagram.com/polidea> [image: Behance]
>>>>>> <https://www.behance.net/polidea> [image: dribbble]
>>>>>> <https://dribbble.com/polideadesign>
>>>>>>
>>>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Valentyn Tymofieiev <va...@google.com>.
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 it
to .test-infra/jenkins/README.md
<https://github.com/apache/beam/blob/master/.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-blocking-issues-in-jira
<https://www.google.com/url?q=https://beam.apache.org/contribute/release-guide/%234-triage-release-blocking-issues-in-jira&sa=D&source=hangouts&ust=1594262748653000&usg=AFQjCNFZYd0JpuYxxvj44rxOu6f6twr76A>
On Mon, Jul 6, 2020 at 9:47 AM Ahmet Altay <al...@google.com> wrote:
> Done.
>
> On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev <va...@google.com>
> 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 <va...@google.com>
>> 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 <va...@google.com>
>>> wrote:
>>>
>>>> Great, thank you Tobiasz, I will take a look.
>>>>
>>>> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
>>>> 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 <al...@google.com> wrote:
>>>>>
>>>>>> Valentyn,
>>>>>>
>>>>>> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added
>>>>>> 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 release
>>>>>> 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 <ru...@google.com> wrote:
>>>>>>>
>>>>>>>> Thank you Valentyn!
>>>>>>>>
>>>>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thank you Valentyn!
>>>>>>>>>
>>>>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@google.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Thanks Valentyn!
>>>>>>>>>>
>>>>>>>>>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Tobiasz Kędzierski
>>>>> Polidea <https://www.polidea.com/> | Junior Software Engineer
>>>>>
>>>>> E: tobiasz.kedzierski@polidea.com
>>>>> [image: Polidea] <https://www.polidea.com/>
>>>>>
>>>>> Check out our projects! <https://www.polidea.com/our-work>
>>>>> [image: Github] <https://github.com/Polidea> [image: Facebook]
>>>>> <https://www.facebook.com/Polidea.Software> [image: Twitter]
>>>>> <https://twitter.com/polidea> [image: Linkedin]
>>>>> <https://www.linkedin.com/company/polidea> [image: Instagram]
>>>>> <https://instagram.com/polidea> [image: Behance]
>>>>> <https://www.behance.net/polidea> [image: dribbble]
>>>>> <https://dribbble.com/polideadesign>
>>>>>
>>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Ahmet Altay <al...@google.com>.
Done.
On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev <va...@google.com>
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 <va...@google.com>
> 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 <va...@google.com>
>> wrote:
>>
>>> Great, thank you Tobiasz, I will take a look.
>>>
>>> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
>>> 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 <al...@google.com> wrote:
>>>>
>>>>> Valentyn,
>>>>>
>>>>> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added
>>>>> 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 release
>>>>> 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 <ru...@google.com> wrote:
>>>>>>
>>>>>>> Thank you Valentyn!
>>>>>>>
>>>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thank you Valentyn!
>>>>>>>>
>>>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@google.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks Valentyn!
>>>>>>>>>
>>>>>>>>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>>
>>>>>>>>>>>
>>>>
>>>> --
>>>>
>>>> Tobiasz Kędzierski
>>>> Polidea <https://www.polidea.com/> | Junior Software Engineer
>>>>
>>>> E: tobiasz.kedzierski@polidea.com
>>>> [image: Polidea] <https://www.polidea.com/>
>>>>
>>>> Check out our projects! <https://www.polidea.com/our-work>
>>>> [image: Github] <https://github.com/Polidea> [image: Facebook]
>>>> <https://www.facebook.com/Polidea.Software> [image: Twitter]
>>>> <https://twitter.com/polidea> [image: Linkedin]
>>>> <https://www.linkedin.com/company/polidea> [image: Instagram]
>>>> <https://instagram.com/polidea> [image: Behance]
>>>> <https://www.behance.net/polidea> [image: dribbble]
>>>> <https://dribbble.com/polideadesign>
>>>>
>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Valentyn Tymofieiev <va...@google.com>.
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 <va...@google.com>
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 <va...@google.com>
> wrote:
>
>> Great, thank you Tobiasz, I will take a look.
>>
>> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
>> 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 <al...@google.com> wrote:
>>>
>>>> Valentyn,
>>>>
>>>> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added
>>>> 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 release
>>>> 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 <ru...@google.com> wrote:
>>>>>
>>>>>> Thank you Valentyn!
>>>>>>
>>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com> wrote:
>>>>>>
>>>>>>> Thank you Valentyn!
>>>>>>>
>>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@google.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks Valentyn!
>>>>>>>>
>>>>>>>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>>
>>>>>>>>>>
>>>
>>> --
>>>
>>> Tobiasz Kędzierski
>>> Polidea <https://www.polidea.com/> | Junior Software Engineer
>>>
>>> E: tobiasz.kedzierski@polidea.com
>>> [image: Polidea] <https://www.polidea.com/>
>>>
>>> Check out our projects! <https://www.polidea.com/our-work>
>>> [image: Github] <https://github.com/Polidea> [image: Facebook]
>>> <https://www.facebook.com/Polidea.Software> [image: Twitter]
>>> <https://twitter.com/polidea> [image: Linkedin]
>>> <https://www.linkedin.com/company/polidea> [image: Instagram]
>>> <https://instagram.com/polidea> [image: Behance]
>>> <https://www.behance.net/polidea> [image: dribbble]
>>> <https://dribbble.com/polideadesign>
>>>
>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Valentyn Tymofieiev <va...@google.com>.
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 <va...@google.com>
wrote:
> Great, thank you Tobiasz, I will take a look.
>
> On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
> 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 <al...@google.com> wrote:
>>
>>> Valentyn,
>>>
>>> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added
>>> 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 release process.
>>>
>>> Ahmet
>>>
>>> On Tue, Jun 23, 2020 at 7:27 PM Valentyn Tymofieiev <va...@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 <ru...@google.com> wrote:
>>>>
>>>>> Thank you Valentyn!
>>>>>
>>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>> Thank you Valentyn!
>>>>>>
>>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks Valentyn!
>>>>>>>
>>>>>>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>>
>>>>>>>>>
>>
>> --
>>
>> Tobiasz Kędzierski
>> Polidea <https://www.polidea.com/> | Junior Software Engineer
>>
>> E: tobiasz.kedzierski@polidea.com
>> [image: Polidea] <https://www.polidea.com/>
>>
>> Check out our projects! <https://www.polidea.com/our-work>
>> [image: Github] <https://github.com/Polidea> [image: Facebook]
>> <https://www.facebook.com/Polidea.Software> [image: Twitter]
>> <https://twitter.com/polidea> [image: Linkedin]
>> <https://www.linkedin.com/company/polidea> [image: Instagram]
>> <https://instagram.com/polidea> [image: Behance]
>> <https://www.behance.net/polidea> [image: dribbble]
>> <https://dribbble.com/polideadesign>
>>
>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Valentyn Tymofieiev <va...@google.com>.
Great, thank you Tobiasz, I will take a look.
On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <
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 <al...@google.com> wrote:
>
>> Valentyn,
>>
>> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added 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 release process.
>>
>> Ahmet
>>
>> On Tue, Jun 23, 2020 at 7:27 PM Valentyn Tymofieiev <va...@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 <ru...@google.com> wrote:
>>>
>>>> Thank you Valentyn!
>>>>
>>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> Thank you Valentyn!
>>>>>
>>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@google.com>
>>>>> wrote:
>>>>>
>>>>>> Thanks Valentyn!
>>>>>>
>>>>>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>>
>>>>>>>>
>
> --
>
> Tobiasz Kędzierski
> Polidea <https://www.polidea.com/> | Junior Software Engineer
>
> E: tobiasz.kedzierski@polidea.com
> [image: Polidea] <https://www.polidea.com/>
>
> Check out our projects! <https://www.polidea.com/our-work>
> [image: Github] <https://github.com/Polidea> [image: Facebook]
> <https://www.facebook.com/Polidea.Software> [image: Twitter]
> <https://twitter.com/polidea> [image: Linkedin]
> <https://www.linkedin.com/company/polidea> [image: Instagram]
> <https://instagram.com/polidea> [image: Behance]
> <https://www.behance.net/polidea> [image: dribbble]
> <https://dribbble.com/polideadesign>
>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Tobiasz Kędzierski <to...@polidea.com>.
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 <al...@google.com> wrote:
> Valentyn,
>
> +tobiasz.kedzierski@polidea.com <to...@polidea.com> added 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 release process.
>
> Ahmet
>
> On Tue, Jun 23, 2020 at 7:27 PM Valentyn Tymofieiev <va...@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 <ru...@google.com> wrote:
>>
>>> Thank you Valentyn!
>>>
>>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Thank you Valentyn!
>>>>
>>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@google.com>
>>>> wrote:
>>>>
>>>>> Thanks Valentyn!
>>>>>
>>>>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>>
>>>>>>>
--
Tobiasz Kędzierski
Polidea <https://www.polidea.com/> | Junior Software Engineer
E: tobiasz.kedzierski@polidea.com
[image: Polidea] <https://www.polidea.com/>
Check out our projects! <https://www.polidea.com/our-work>
[image: Github] <https://github.com/Polidea> [image: Facebook]
<https://www.facebook.com/Polidea.Software> [image: Twitter]
<https://twitter.com/polidea> [image: Linkedin]
<https://www.linkedin.com/company/polidea> [image: Instagram]
<https://instagram.com/polidea> [image: Behance]
<https://www.behance.net/polidea> [image: dribbble]
<https://dribbble.com/polideadesign>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Ahmet Altay <al...@google.com>.
Valentyn,
+tobiasz.kedzierski@polidea.com <to...@polidea.com> added 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 release process.
Ahmet
On Tue, Jun 23, 2020 at 7:27 PM Valentyn Tymofieiev <va...@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 <ru...@google.com> wrote:
>
>> Thank you Valentyn!
>>
>> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com> wrote:
>>
>>> Thank you Valentyn!
>>>
>>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@google.com> wrote:
>>>
>>>> Thanks Valentyn!
>>>>
>>>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>>
>>>>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Valentyn Tymofieiev <va...@google.com>.
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 <ru...@google.com> wrote:
> Thank you Valentyn!
>
> On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com> wrote:
>
>> Thank you Valentyn!
>>
>> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@google.com> wrote:
>>
>>> Thanks Valentyn!
>>>
>>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>
>>>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Rui Wang <ru...@google.com>.
Thank you Valentyn!
On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <al...@google.com> wrote:
> Thank you Valentyn!
>
> On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@google.com> wrote:
>
>> Thanks Valentyn!
>>
>> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>
>>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Ahmet Altay <al...@google.com>.
Thank you Valentyn!
On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <go...@google.com> wrote:
> Thanks Valentyn!
>
> On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@google.com> wrote:
>
>> Sounds good, thanks Valentyn!
>>
>> On Mon, Jun 15, 2020 at 12:31 PM Valentyn Tymofieiev <va...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>
>>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Ankur Goenka <go...@google.com>.
Thanks Valentyn!
On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <kc...@google.com> wrote:
> Sounds good, thanks Valentyn!
>
> On Mon, Jun 15, 2020 at 12:31 PM Valentyn Tymofieiev <va...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>
>>
Re: [PROPOSAL] Preparing for Beam 2.23.0 release
Posted by Kyle Weaver <kc...@google.com>.
Sounds good, thanks Valentyn!
On Mon, Jun 15, 2020 at 12:31 PM Valentyn Tymofieiev <va...@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=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>
>