+1

I ran the release candidate verification script and updated the spreadsheet
[1]
Also, verified signature and checksums of some of the artifacts.

Thanks,
Cham

[1]
https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=283321283


On Thu, Feb 18, 2021 at 2:19 PM Brian Hulette <[email protected]> wrote:

> +1 (non-binding)
>
> Built and ran a streaming SQL in Python pipeline and a DataFrame API
> pipeline on Dataflow
>
> On Thu, Feb 18, 2021 at 1:00 PM Pablo Estrada <[email protected]> wrote:
>
>> +1 (binding)
>>
>> Built and ran basic tests for existing Dataflow templates
>>
>> On Wed, Feb 17, 2021 at 8:06 PM Chamikara Jayalath <[email protected]>
>> wrote:
>>
>>> Repositories were merged into [1]. So this RC validation thread can
>>> continue.
>>>
>>> Thanks,
>>> Cham
>>>
>>> [1]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1161/
>>>
>>> On Wed, Feb 17, 2021 at 10:41 AM Chamikara Jayalath <
>>> [email protected]> wrote:
>>>
>>>> Thanks.
>>>>
>>>> FYI: I noticed that one of the Java artifacts was pushed into a
>>>> separate Nexus repository for some reason.
>>>> https://issues.apache.org/jira/browse/BEAM-11813 is tracking this and
>>>> we are trying to get the two repos merged but this should not block release
>>>> candidate validation.
>>>>
>>>> Thanks,
>>>> Cham
>>>>
>>>> On Wed, Feb 17, 2021 at 10:32 AM Valentyn Tymofieiev <
>>>> [email protected]> wrote:
>>>>
>>>>> +1.
>>>>> I ran several Python pipelines on Direct and Dataflow runner
>>>>> and inspected Dataflow container images.
>>>>>
>>>>> CHANGES.md[1]  has a nice long list of new features. I encourage
>>>>> authors of the features to verify them on the RC and vote here.
>>>>> [1] https://github.com/chamikaramj/beam/blob/blog_2_28_0/CHANGES.md
>>>>>
>>>>> On Mon, Feb 15, 2021 at 12:02 PM Chamikara Jayalath <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Hi everyone,
>>>>>>
>>>>>> Please review and vote on the release candidate #1 for the version
>>>>>> 2.28.0, as follows:
>>>>>> [ ] +1, Approve the release
>>>>>> [ ] -1, Do not approve the release (please provide specific comments)
>>>>>>
>>>>>>
>>>>>> Reviewers are encouraged to test their own use cases with the release
>>>>>> candidate, and vote +1 if no issues are found.
>>>>>>
>>>>>> The complete staging area is available for your review, which
>>>>>> includes:
>>>>>> * JIRA release notes [1],
>>>>>> * the official Apache source release to be deployed to
>>>>>> dist.apache.org [2], which is signed with the key with fingerprint
>>>>>> 0CCD5EB2A718A56E [3],
>>>>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>>>>> * source code tag "v2.28.0-RC1" [5],
>>>>>> * website pull request listing the release [6], publishing the API
>>>>>> reference manual [7], and the blog post [8].
>>>>>> * Java artifacts were built with Maven 3.3.9 and OpenJDK/Oracle JDK
>>>>>> 1.8.0_181.
>>>>>> * Python artifacts are deployed along with the source release to the
>>>>>> dist.apache.org [2].
>>>>>> * Validation sheet with a tab for 2.28.0 release to help with
>>>>>> validation [9].
>>>>>> * Docker images published to Docker Hub [10].
>>>>>>
>>>>>> The vote will be open for at least 72 hours. It is adopted by
>>>>>> majority approval, with at least 3 PMC affirmative votes.
>>>>>>
>>>>>> Thanks,
>>>>>> Cham
>>>>>>
>>>>>> [1]
>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12349499
>>>>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.28.0/
>>>>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>>>>> [4]
>>>>>> https://repository.apache.org/content/repositories/orgapachebeam-1161/
>>>>>> [5] https://github.com/apache/beam/tree/v2.28.0-RC1
>>>>>> [6] https://github.com/apache/beam/pull/13991
>>>>>> [7] https://github.com/apache/beam-site/pull/611
>>>>>> [8] https://github.com/apache/beam/pull/13992
>>>>>> [9]
>>>>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=283321283
>>>>>> [10] https://hub.docker.com/search?q=apache%2Fbeam&type=image
>>>>>>
>>>>>

Reply via email to