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

[Robert Burke]

That was due to having the image part of the release changes for 2.27.0 in
a bit too early (and partially complete at the time). My understanding is
the separate java8 and java11 containers weren't to be available until
2.27.0, so 2.26.0 is the last release with the single beam_java_sdk build.

On Mon, Dec 28, 2020, 9:34 AM Ismaël Mejía  wrote:

> It seems the tag of the docker image for java8 was not updated after the
> release went out, can somebody please fix this.
>
>
> https://hub.docker.com/r/apache/beam_java8_sdk/tags?page=1=last_updated
>
>
> On Sat, Dec 12, 2020 at 7:19 AM Jean-Baptiste Onofre 
> wrote:
>
>> +1 (binding)
>>
>> Sorry for the delay.
>>
>> Regards
>> JB
>>
>> Le 10 déc. 2020 à 17:40, Tyson Hamilton  a écrit :
>>
>> +1 from me. I validated Nexmark performance tests.
>>
>> On Tue, Dec 8, 2020 at 7:53 PM Robert Burke  wrote:
>>
>>> I'm +1 on RC1 based on the 7 tests I know I can check successfully.
>>> I'll be trying more tomorrow, but remember that release validation requires
>>> the community to validate it meets our standards, and I can't do it alone.
>>>
>>> Remember you can participate in the release validation by reviewing
>>> parts of the documentation being published as well, not just by running the
>>> Pyhton and Java artifacts.
>>>
>>>  If you have contributed new python or java docs into this release,
>>> they'll appear in the to be published docs.
>>>
>>> Cheers,
>>> Robert Burke
>>> 2.26.0 release manager
>>>
>>> On Mon, Dec 7, 2020, 6:25 PM Robert Burke  wrote:
>>>
 Turns out no changes required affecting the dataflow artifacts this
 time around, so Dataflow is cleared for testing.

 Cheers.
 Robert Burke
 2.26.0 Release Manager

 On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:

>
> Robert Burke 
> Thu, Dec 3, 8:01 PM (4 days ago)
> to dev
> Hi everyone,
> Please review and vote on the release candidate #1 for the version
> 2.26.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
> A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2].
> * Validation sheet with a tab for 2.26.0 release to help with
> validation [9].
> * Docker images published to Docker Hub [10].
>
> The vote will be open for at least 72 hours (10th ~6pm PST). It is
> adopted by majority approval, with at least 3 PMC affirmative votes.
>
> Thanks,
> Robert Burke
> 2.26.0 Release Manager
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
> [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/org apache
> beam-1144/
> [5] https://github.com/apache/beam/tree/v2.26.0-RC1
> [6] https://github.com/apache/beam/pull/13481
> [7] https://github.com/apache/beam-site/pull/609
> [8] https://github.com/apache/beam/pull/13482
> [9]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>
> PS. New Dataflow artifacts likely need to be built and published but
> this doesn't block vetting the remainder of the RC at this time. Thank you
> for your patience.
>
>
>>

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

[Ismaël Mejía]

It seems the tag of the docker image for java8 was not updated after the
release went out, can somebody please fix this.

https://hub.docker.com/r/apache/beam_java8_sdk/tags?page=1=last_updated


On Sat, Dec 12, 2020 at 7:19 AM Jean-Baptiste Onofre 
wrote:

> +1 (binding)
>
> Sorry for the delay.
>
> Regards
> JB
>
> Le 10 déc. 2020 à 17:40, Tyson Hamilton  a écrit :
>
> +1 from me. I validated Nexmark performance tests.
>
> On Tue, Dec 8, 2020 at 7:53 PM Robert Burke  wrote:
>
>> I'm +1 on RC1 based on the 7 tests I know I can check successfully.  I'll
>> be trying more tomorrow, but remember that release validation requires the
>> community to validate it meets our standards, and I can't do it alone.
>>
>> Remember you can participate in the release validation by reviewing parts
>> of the documentation being published as well, not just by running the
>> Pyhton and Java artifacts.
>>
>>  If you have contributed new python or java docs into this release,
>> they'll appear in the to be published docs.
>>
>> Cheers,
>> Robert Burke
>> 2.26.0 release manager
>>
>> On Mon, Dec 7, 2020, 6:25 PM Robert Burke  wrote:
>>
>>> Turns out no changes required affecting the dataflow artifacts this time
>>> around, so Dataflow is cleared for testing.
>>>
>>> Cheers.
>>> Robert Burke
>>> 2.26.0 Release Manager
>>>
>>> On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:
>>>

 Robert Burke 
 Thu, Dec 3, 8:01 PM (4 days ago)
 to dev
 Hi everyone,
 Please review and vote on the release candidate #1 for the version
 2.26.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
 A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
 * all artifacts to be deployed to the Maven Central Repository [4],
 * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
 * Python artifacts are deployed along with the source release to the
 dist.apache.org [2].
 * Validation sheet with a tab for 2.26.0 release to help with
 validation [9].
 * Docker images published to Docker Hub [10].

 The vote will be open for at least 72 hours (10th ~6pm PST). It is
 adopted by majority approval, with at least 3 PMC affirmative votes.

 Thanks,
 Robert Burke
 2.26.0 Release Manager

 [1]
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
 [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
 [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 [4] https://repository.apache.org/content/repositories/org apache
 beam-1144/
 [5] https://github.com/apache/beam/tree/v2.26.0-RC1
 [6] https://github.com/apache/beam/pull/13481
 [7] https://github.com/apache/beam-site/pull/609
 [8] https://github.com/apache/beam/pull/13482
 [9]
 https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
 [10] https://hub.docker.com/search?q=apache%2Fbeam=image

 PS. New Dataflow artifacts likely need to be built and published but
 this doesn't block vetting the remainder of the RC at this time. Thank you
 for your patience.


>

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

[Jean-Baptiste Onofre]

+1 (binding)

Sorry for the delay.

Regards
JB

> Le 10 déc. 2020 à 17:40, Tyson Hamilton  a écrit :
> 
> +1 from me. I validated Nexmark performance tests.
> 
> On Tue, Dec 8, 2020 at 7:53 PM Robert Burke  > wrote:
> I'm +1 on RC1 based on the 7 tests I know I can check successfully.  I'll be 
> trying more tomorrow, but remember that release validation requires the 
> community to validate it meets our standards, and I can't do it alone.
> 
> Remember you can participate in the release validation by reviewing parts of 
> the documentation being published as well, not just by running the Pyhton and 
> Java artifacts.
> 
>  If you have contributed new python or java docs into this release, they'll 
> appear in the to be published docs.
> 
> Cheers,
> Robert Burke
> 2.26.0 release manager
> 
> On Mon, Dec 7, 2020, 6:25 PM Robert Burke  > wrote:
> Turns out no changes required affecting the dataflow artifacts this time 
> around, so Dataflow is cleared for testing.
> 
> Cheers.
> Robert Burke
> 2.26.0 Release Manager
> 
> On Mon, Dec 7, 2020, 6:03 PM Robert Burke  > wrote:
> 
> Robert Burke mailto:r...@google.com>>
> Thu, Dec 3, 8:01 PM (4 days ago)
> 
> to dev
> Hi everyone,
> Please review and vote on the release candidate #1 for the version 2.26.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 
> A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
> * Python artifacts are deployed along with the source release to the 
> dist.apache.org  [2].
> * Validation sheet with a tab for 2.26.0 release to help with validation [9].
> * Docker images published to Docker Hub [10].
> 
> The vote will be open for at least 72 hours (10th ~6pm PST). It is adopted by 
> majority approval, with at least 3 PMC affirmative votes.
> 
> Thanks,
> Robert Burke
> 2.26.0 Release Manager
> 
> [1] 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
>  
> 
> [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/ 
> 
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS 
> 
> [4] https://repository.apache.org/content/repositories/org 
>  apache beam-1144/
> [5] https://github.com/apache/beam/tree/v2.26.0-RC1 
> 
> [6] https://github.com/apache/beam/pull/13481 
> 
> [7] https://github.com/apache/beam-site/pull/609 
> 
> [8] https://github.com/apache/beam/pull/13482 
> 
> [9] 
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
>  
> 
> [10] https://hub.docker.com/search?q=apache%2Fbeam=image 
> 
> 
> PS. New Dataflow artifacts likely need to be built and published but this 
> doesn't block vetting the remainder of the RC at this time. Thank you for 
> your patience.
> 

[RESULT] [VOTE] Release 2.26.0, release candidate #1

[Robert Burke]

I'm happy to announce that we have unanimously approved this release.

There are 7 approving votes, 3 of which are binding:
* Robert Bradshaw
* Pablo Estrada
* Ahmet Altay

There are no disapproving votes.

Thanks everyone! I'll be working on finalizing the release this afternoon

Robert Burke
2.26.0 Release Manager

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

[Ahmet Altay]

+1 (binding)

On Thu, Dec 10, 2020 at 6:05 PM Robert Burke  wrote:

> Hello All!
> The minimum vote time has elapsed with six +1 votes, two of which are
> binding, which is not enough for me to start finalization processes.
>
> I'm happy to extend the period until the sooner of the 2.27.0 branch is
> cut and it's first RC is built (sometime on/after the 16th according to the
> schedule) or we get an additional binding vote for this RC.
>
> Binding votes may only be cast by Apache Beam PMC members, but all
> validation is incredibly valuable in ensuring the release meets the
> community's standards.
>
> Thank you all for your patience and participation so far!
> Robert Burke
> 2.26.0 Release Manager
>
> On Thu, 10 Dec 2020 at 14:59, Pablo Estrada  wrote:
>
>> +1 (binding)
>> I've built and ran basic tests for existing Dataflow templates.
>> Best
>> -P.
>>
>> On Thu, Dec 10, 2020 at 11:31 AM Robert Bradshaw 
>> wrote:
>>
>>> +1 (binding). I've verified the release artifacts and signatures, and
>>> validated some simple pipelines with a freshly installed wheel.
>>>
>>> On Thu, Dec 10, 2020 at 10:00 AM Brian Hulette 
>>> wrote:
>>>
 +1 (non-binding). Ran a Python pipeline using DataframeTransform on
 DirectRunner and DataflowRunner (woohoo!)

 On Thu, Dec 10, 2020 at 8:48 AM Chamikara Jayalath <
 chamik...@google.com> wrote:

> +1 (non-binding). Validated multi-language pipelines for Kafka/SQL.
>
> Thanks,
> Cham
>
> On Thu, Dec 10, 2020 at 8:41 AM Tyson Hamilton 
> wrote:
>
>> +1 from me. I validated Nexmark performance tests.
>>
>> On Tue, Dec 8, 2020 at 7:53 PM Robert Burke 
>> wrote:
>>
>>> I'm +1 on RC1 based on the 7 tests I know I can check successfully.
>>> I'll be trying more tomorrow, but remember that release validation 
>>> requires
>>> the community to validate it meets our standards, and I can't do it 
>>> alone.
>>>
>>> Remember you can participate in the release validation by reviewing
>>> parts of the documentation being published as well, not just by running 
>>> the
>>> Pyhton and Java artifacts.
>>>
>>>  If you have contributed new python or java docs into this release,
>>> they'll appear in the to be published docs.
>>>
>>> Cheers,
>>> Robert Burke
>>> 2.26.0 release manager
>>>
>>> On Mon, Dec 7, 2020, 6:25 PM Robert Burke 
>>> wrote:
>>>
 Turns out no changes required affecting the dataflow artifacts this
 time around, so Dataflow is cleared for testing.

 Cheers.
 Robert Burke
 2.26.0 Release Manager

 On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:

>
> Robert Burke 
> Thu, Dec 3, 8:01 PM (4 days ago)
> to dev
> Hi everyone,
> Please review and vote on the release candidate #1 for the version
> 2.26.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 A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
> * Python artifacts are deployed along with the source release to
> the dist.apache.org [2].
> * Validation sheet with a tab for 2.26.0 release to help with
> validation [9].
> * Docker images published to Docker Hub [10].
>
> The vote will be open for at least 72 hours (10th ~6pm PST). It is
> adopted by majority approval, with at least 3 PMC affirmative votes.
>
> Thanks,
> Robert Burke
> 2.26.0 Release Manager
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
> [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/org apache
> beam-1144/
> [5] https://github.com/apache/beam/tree/v2.26.0-RC1
> [6] https://github.com/apache/beam/pull/13481
> [7] https://github.com/apache/beam-site/pull/609
> [8] 

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

[Robert Burke]

Hello All!
The minimum vote time has elapsed with six +1 votes, two of which are
binding, which is not enough for me to start finalization processes.

I'm happy to extend the period until the sooner of the 2.27.0 branch is cut
and it's first RC is built (sometime on/after the 16th according to the
schedule) or we get an additional binding vote for this RC.

Binding votes may only be cast by Apache Beam PMC members, but all
validation is incredibly valuable in ensuring the release meets the
community's standards.

Thank you all for your patience and participation so far!
Robert Burke
2.26.0 Release Manager

On Thu, 10 Dec 2020 at 14:59, Pablo Estrada  wrote:

> +1 (binding)
> I've built and ran basic tests for existing Dataflow templates.
> Best
> -P.
>
> On Thu, Dec 10, 2020 at 11:31 AM Robert Bradshaw 
> wrote:
>
>> +1 (binding). I've verified the release artifacts and signatures, and
>> validated some simple pipelines with a freshly installed wheel.
>>
>> On Thu, Dec 10, 2020 at 10:00 AM Brian Hulette 
>> wrote:
>>
>>> +1 (non-binding). Ran a Python pipeline using DataframeTransform on
>>> DirectRunner and DataflowRunner (woohoo!)
>>>
>>> On Thu, Dec 10, 2020 at 8:48 AM Chamikara Jayalath 
>>> wrote:
>>>
 +1 (non-binding). Validated multi-language pipelines for Kafka/SQL.

 Thanks,
 Cham

 On Thu, Dec 10, 2020 at 8:41 AM Tyson Hamilton 
 wrote:

> +1 from me. I validated Nexmark performance tests.
>
> On Tue, Dec 8, 2020 at 7:53 PM Robert Burke 
> wrote:
>
>> I'm +1 on RC1 based on the 7 tests I know I can check successfully.
>> I'll be trying more tomorrow, but remember that release validation 
>> requires
>> the community to validate it meets our standards, and I can't do it 
>> alone.
>>
>> Remember you can participate in the release validation by reviewing
>> parts of the documentation being published as well, not just by running 
>> the
>> Pyhton and Java artifacts.
>>
>>  If you have contributed new python or java docs into this release,
>> they'll appear in the to be published docs.
>>
>> Cheers,
>> Robert Burke
>> 2.26.0 release manager
>>
>> On Mon, Dec 7, 2020, 6:25 PM Robert Burke  wrote:
>>
>>> Turns out no changes required affecting the dataflow artifacts this
>>> time around, so Dataflow is cleared for testing.
>>>
>>> Cheers.
>>> Robert Burke
>>> 2.26.0 Release Manager
>>>
>>> On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:
>>>

 Robert Burke 
 Thu, Dec 3, 8:01 PM (4 days ago)
 to dev
 Hi everyone,
 Please review and vote on the release candidate #1 for the version
 2.26.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
 A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
 * all artifacts to be deployed to the Maven Central Repository [4],
 * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
 * Python artifacts are deployed along with the source release to
 the dist.apache.org [2].
 * Validation sheet with a tab for 2.26.0 release to help with
 validation [9].
 * Docker images published to Docker Hub [10].

 The vote will be open for at least 72 hours (10th ~6pm PST). It is
 adopted by majority approval, with at least 3 PMC affirmative votes.

 Thanks,
 Robert Burke
 2.26.0 Release Manager

 [1]
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
 [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
 [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 [4] https://repository.apache.org/content/repositories/org apache
 beam-1144/
 [5] https://github.com/apache/beam/tree/v2.26.0-RC1
 [6] https://github.com/apache/beam/pull/13481
 [7] https://github.com/apache/beam-site/pull/609
 [8] https://github.com/apache/beam/pull/13482
 [9]
 https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
 [10] https://hub.docker.com/search?q=apache%2Fbeam=image

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

[Pablo Estrada]

+1 (binding)
I've built and ran basic tests for existing Dataflow templates.
Best
-P.

On Thu, Dec 10, 2020 at 11:31 AM Robert Bradshaw 
wrote:

> +1 (binding). I've verified the release artifacts and signatures, and
> validated some simple pipelines with a freshly installed wheel.
>
> On Thu, Dec 10, 2020 at 10:00 AM Brian Hulette 
> wrote:
>
>> +1 (non-binding). Ran a Python pipeline using DataframeTransform on
>> DirectRunner and DataflowRunner (woohoo!)
>>
>> On Thu, Dec 10, 2020 at 8:48 AM Chamikara Jayalath 
>> wrote:
>>
>>> +1 (non-binding). Validated multi-language pipelines for Kafka/SQL.
>>>
>>> Thanks,
>>> Cham
>>>
>>> On Thu, Dec 10, 2020 at 8:41 AM Tyson Hamilton 
>>> wrote:
>>>
 +1 from me. I validated Nexmark performance tests.

 On Tue, Dec 8, 2020 at 7:53 PM Robert Burke  wrote:

> I'm +1 on RC1 based on the 7 tests I know I can check successfully.
> I'll be trying more tomorrow, but remember that release validation 
> requires
> the community to validate it meets our standards, and I can't do it alone.
>
> Remember you can participate in the release validation by reviewing
> parts of the documentation being published as well, not just by running 
> the
> Pyhton and Java artifacts.
>
>  If you have contributed new python or java docs into this release,
> they'll appear in the to be published docs.
>
> Cheers,
> Robert Burke
> 2.26.0 release manager
>
> On Mon, Dec 7, 2020, 6:25 PM Robert Burke  wrote:
>
>> Turns out no changes required affecting the dataflow artifacts this
>> time around, so Dataflow is cleared for testing.
>>
>> Cheers.
>> Robert Burke
>> 2.26.0 Release Manager
>>
>> On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:
>>
>>>
>>> Robert Burke 
>>> Thu, Dec 3, 8:01 PM (4 days ago)
>>> to dev
>>> Hi everyone,
>>> Please review and vote on the release candidate #1 for the version
>>> 2.26.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
>>> A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
>>> * Python artifacts are deployed along with the source release to the
>>> dist.apache.org [2].
>>> * Validation sheet with a tab for 2.26.0 release to help with
>>> validation [9].
>>> * Docker images published to Docker Hub [10].
>>>
>>> The vote will be open for at least 72 hours (10th ~6pm PST). It is
>>> adopted by majority approval, with at least 3 PMC affirmative votes.
>>>
>>> Thanks,
>>> Robert Burke
>>> 2.26.0 Release Manager
>>>
>>> [1]
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> [4] https://repository.apache.org/content/repositories/org apache
>>> beam-1144/
>>> [5] https://github.com/apache/beam/tree/v2.26.0-RC1
>>> [6] https://github.com/apache/beam/pull/13481
>>> [7] https://github.com/apache/beam-site/pull/609
>>> [8] https://github.com/apache/beam/pull/13482
>>> [9]
>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
>>> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>>>
>>> PS. New Dataflow artifacts likely need to be built and published but
>>> this doesn't block vetting the remainder of the RC at this time. Thank 
>>> you
>>> for your patience.
>>>
>>>

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

[Robert Bradshaw]

+1 (binding). I've verified the release artifacts and signatures, and
validated some simple pipelines with a freshly installed wheel.

On Thu, Dec 10, 2020 at 10:00 AM Brian Hulette  wrote:

> +1 (non-binding). Ran a Python pipeline using DataframeTransform on
> DirectRunner and DataflowRunner (woohoo!)
>
> On Thu, Dec 10, 2020 at 8:48 AM Chamikara Jayalath 
> wrote:
>
>> +1 (non-binding). Validated multi-language pipelines for Kafka/SQL.
>>
>> Thanks,
>> Cham
>>
>> On Thu, Dec 10, 2020 at 8:41 AM Tyson Hamilton 
>> wrote:
>>
>>> +1 from me. I validated Nexmark performance tests.
>>>
>>> On Tue, Dec 8, 2020 at 7:53 PM Robert Burke  wrote:
>>>
 I'm +1 on RC1 based on the 7 tests I know I can check successfully.
 I'll be trying more tomorrow, but remember that release validation requires
 the community to validate it meets our standards, and I can't do it alone.

 Remember you can participate in the release validation by reviewing
 parts of the documentation being published as well, not just by running the
 Pyhton and Java artifacts.

  If you have contributed new python or java docs into this release,
 they'll appear in the to be published docs.

 Cheers,
 Robert Burke
 2.26.0 release manager

 On Mon, Dec 7, 2020, 6:25 PM Robert Burke  wrote:

> Turns out no changes required affecting the dataflow artifacts this
> time around, so Dataflow is cleared for testing.
>
> Cheers.
> Robert Burke
> 2.26.0 Release Manager
>
> On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:
>
>>
>> Robert Burke 
>> Thu, Dec 3, 8:01 PM (4 days ago)
>> to dev
>> Hi everyone,
>> Please review and vote on the release candidate #1 for the version
>> 2.26.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
>> A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
>> * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2].
>> * Validation sheet with a tab for 2.26.0 release to help with
>> validation [9].
>> * Docker images published to Docker Hub [10].
>>
>> The vote will be open for at least 72 hours (10th ~6pm PST). It is
>> adopted by majority approval, with at least 3 PMC affirmative votes.
>>
>> Thanks,
>> Robert Burke
>> 2.26.0 Release Manager
>>
>> [1]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4] https://repository.apache.org/content/repositories/org apache
>> beam-1144/
>> [5] https://github.com/apache/beam/tree/v2.26.0-RC1
>> [6] https://github.com/apache/beam/pull/13481
>> [7] https://github.com/apache/beam-site/pull/609
>> [8] https://github.com/apache/beam/pull/13482
>> [9]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
>> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>>
>> PS. New Dataflow artifacts likely need to be built and published but
>> this doesn't block vetting the remainder of the RC at this time. Thank 
>> you
>> for your patience.
>>
>>

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

[Brian Hulette]

+1 (non-binding). Ran a Python pipeline using DataframeTransform on
DirectRunner and DataflowRunner (woohoo!)

On Thu, Dec 10, 2020 at 8:48 AM Chamikara Jayalath 
wrote:

> +1 (non-binding). Validated multi-language pipelines for Kafka/SQL.
>
> Thanks,
> Cham
>
> On Thu, Dec 10, 2020 at 8:41 AM Tyson Hamilton  wrote:
>
>> +1 from me. I validated Nexmark performance tests.
>>
>> On Tue, Dec 8, 2020 at 7:53 PM Robert Burke  wrote:
>>
>>> I'm +1 on RC1 based on the 7 tests I know I can check successfully.
>>> I'll be trying more tomorrow, but remember that release validation requires
>>> the community to validate it meets our standards, and I can't do it alone.
>>>
>>> Remember you can participate in the release validation by reviewing
>>> parts of the documentation being published as well, not just by running the
>>> Pyhton and Java artifacts.
>>>
>>>  If you have contributed new python or java docs into this release,
>>> they'll appear in the to be published docs.
>>>
>>> Cheers,
>>> Robert Burke
>>> 2.26.0 release manager
>>>
>>> On Mon, Dec 7, 2020, 6:25 PM Robert Burke  wrote:
>>>
 Turns out no changes required affecting the dataflow artifacts this
 time around, so Dataflow is cleared for testing.

 Cheers.
 Robert Burke
 2.26.0 Release Manager

 On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:

>
> Robert Burke 
> Thu, Dec 3, 8:01 PM (4 days ago)
> to dev
> Hi everyone,
> Please review and vote on the release candidate #1 for the version
> 2.26.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
> A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2].
> * Validation sheet with a tab for 2.26.0 release to help with
> validation [9].
> * Docker images published to Docker Hub [10].
>
> The vote will be open for at least 72 hours (10th ~6pm PST). It is
> adopted by majority approval, with at least 3 PMC affirmative votes.
>
> Thanks,
> Robert Burke
> 2.26.0 Release Manager
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
> [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/org apache
> beam-1144/
> [5] https://github.com/apache/beam/tree/v2.26.0-RC1
> [6] https://github.com/apache/beam/pull/13481
> [7] https://github.com/apache/beam-site/pull/609
> [8] https://github.com/apache/beam/pull/13482
> [9]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>
> PS. New Dataflow artifacts likely need to be built and published but
> this doesn't block vetting the remainder of the RC at this time. Thank you
> for your patience.
>
>

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

[Chamikara Jayalath]

+1 (non-binding). Validated multi-language pipelines for Kafka/SQL.

Thanks,
Cham

On Thu, Dec 10, 2020 at 8:41 AM Tyson Hamilton  wrote:

> +1 from me. I validated Nexmark performance tests.
>
> On Tue, Dec 8, 2020 at 7:53 PM Robert Burke  wrote:
>
>> I'm +1 on RC1 based on the 7 tests I know I can check successfully.  I'll
>> be trying more tomorrow, but remember that release validation requires the
>> community to validate it meets our standards, and I can't do it alone.
>>
>> Remember you can participate in the release validation by reviewing parts
>> of the documentation being published as well, not just by running the
>> Pyhton and Java artifacts.
>>
>>  If you have contributed new python or java docs into this release,
>> they'll appear in the to be published docs.
>>
>> Cheers,
>> Robert Burke
>> 2.26.0 release manager
>>
>> On Mon, Dec 7, 2020, 6:25 PM Robert Burke  wrote:
>>
>>> Turns out no changes required affecting the dataflow artifacts this time
>>> around, so Dataflow is cleared for testing.
>>>
>>> Cheers.
>>> Robert Burke
>>> 2.26.0 Release Manager
>>>
>>> On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:
>>>

 Robert Burke 
 Thu, Dec 3, 8:01 PM (4 days ago)
 to dev
 Hi everyone,
 Please review and vote on the release candidate #1 for the version
 2.26.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
 A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
 * all artifacts to be deployed to the Maven Central Repository [4],
 * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
 * Python artifacts are deployed along with the source release to the
 dist.apache.org [2].
 * Validation sheet with a tab for 2.26.0 release to help with
 validation [9].
 * Docker images published to Docker Hub [10].

 The vote will be open for at least 72 hours (10th ~6pm PST). It is
 adopted by majority approval, with at least 3 PMC affirmative votes.

 Thanks,
 Robert Burke
 2.26.0 Release Manager

 [1]
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
 [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
 [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 [4] https://repository.apache.org/content/repositories/org apache
 beam-1144/
 [5] https://github.com/apache/beam/tree/v2.26.0-RC1
 [6] https://github.com/apache/beam/pull/13481
 [7] https://github.com/apache/beam-site/pull/609
 [8] https://github.com/apache/beam/pull/13482
 [9]
 https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
 [10] https://hub.docker.com/search?q=apache%2Fbeam=image

 PS. New Dataflow artifacts likely need to be built and published but
 this doesn't block vetting the remainder of the RC at this time. Thank you
 for your patience.

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

[Tyson Hamilton]

+1 from me. I validated Nexmark performance tests.

On Tue, Dec 8, 2020 at 7:53 PM Robert Burke  wrote:

> I'm +1 on RC1 based on the 7 tests I know I can check successfully.  I'll
> be trying more tomorrow, but remember that release validation requires the
> community to validate it meets our standards, and I can't do it alone.
>
> Remember you can participate in the release validation by reviewing parts
> of the documentation being published as well, not just by running the
> Pyhton and Java artifacts.
>
>  If you have contributed new python or java docs into this release,
> they'll appear in the to be published docs.
>
> Cheers,
> Robert Burke
> 2.26.0 release manager
>
> On Mon, Dec 7, 2020, 6:25 PM Robert Burke  wrote:
>
>> Turns out no changes required affecting the dataflow artifacts this time
>> around, so Dataflow is cleared for testing.
>>
>> Cheers.
>> Robert Burke
>> 2.26.0 Release Manager
>>
>> On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:
>>
>>>
>>> Robert Burke 
>>> Thu, Dec 3, 8:01 PM (4 days ago)
>>> to dev
>>> Hi everyone,
>>> Please review and vote on the release candidate #1 for the version
>>> 2.26.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
>>> A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
>>> * Python artifacts are deployed along with the source release to the
>>> dist.apache.org [2].
>>> * Validation sheet with a tab for 2.26.0 release to help with validation
>>> [9].
>>> * Docker images published to Docker Hub [10].
>>>
>>> The vote will be open for at least 72 hours (10th ~6pm PST). It is
>>> adopted by majority approval, with at least 3 PMC affirmative votes.
>>>
>>> Thanks,
>>> Robert Burke
>>> 2.26.0 Release Manager
>>>
>>> [1]
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> [4] https://repository.apache.org/content/repositories/org apache
>>> beam-1144/
>>> [5] https://github.com/apache/beam/tree/v2.26.0-RC1
>>> [6] https://github.com/apache/beam/pull/13481
>>> [7] https://github.com/apache/beam-site/pull/609
>>> [8] https://github.com/apache/beam/pull/13482
>>> [9]
>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
>>> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>>>
>>> PS. New Dataflow artifacts likely need to be built and published but
>>> this doesn't block vetting the remainder of the RC at this time. Thank you
>>> for your patience.
>>>
>>>

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

[Robert Burke]

I'm +1 on RC1 based on the 7 tests I know I can check successfully.  I'll
be trying more tomorrow, but remember that release validation requires the
community to validate it meets our standards, and I can't do it alone.

Remember you can participate in the release validation by reviewing parts
of the documentation being published as well, not just by running the
Pyhton and Java artifacts.

 If you have contributed new python or java docs into this release, they'll
appear in the to be published docs.

Cheers,
Robert Burke
2.26.0 release manager

On Mon, Dec 7, 2020, 6:25 PM Robert Burke  wrote:

> Turns out no changes required affecting the dataflow artifacts this time
> around, so Dataflow is cleared for testing.
>
> Cheers.
> Robert Burke
> 2.26.0 Release Manager
>
> On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:
>
>>
>> Robert Burke 
>> Thu, Dec 3, 8:01 PM (4 days ago)
>> to dev
>> Hi everyone,
>> Please review and vote on the release candidate #1 for the version
>> 2.26.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
>> A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
>> * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2].
>> * Validation sheet with a tab for 2.26.0 release to help with validation
>> [9].
>> * Docker images published to Docker Hub [10].
>>
>> The vote will be open for at least 72 hours (10th ~6pm PST). It is
>> adopted by majority approval, with at least 3 PMC affirmative votes.
>>
>> Thanks,
>> Robert Burke
>> 2.26.0 Release Manager
>>
>> [1]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4] https://repository.apache.org/content/repositories/org apache
>> beam-1144/
>> [5] https://github.com/apache/beam/tree/v2.26.0-RC1
>> [6] https://github.com/apache/beam/pull/13481
>> [7] https://github.com/apache/beam-site/pull/609
>> [8] https://github.com/apache/beam/pull/13482
>> [9]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
>> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>>
>> PS. New Dataflow artifacts likely need to be built and published but this
>> doesn't block vetting the remainder of the RC at this time. Thank you for
>> your patience.
>>
>>

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

[Robert Burke]

Turns out no changes required affecting the dataflow artifacts this time
around, so Dataflow is cleared for testing.

Cheers.
Robert Burke
2.26.0 Release Manager

On Mon, Dec 7, 2020, 6:03 PM Robert Burke  wrote:

>
> Robert Burke 
> Thu, Dec 3, 8:01 PM (4 days ago)
> to dev
> Hi everyone,
> Please review and vote on the release candidate #1 for the version 2.26.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
> A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2].
> * Validation sheet with a tab for 2.26.0 release to help with validation
> [9].
> * Docker images published to Docker Hub [10].
>
> The vote will be open for at least 72 hours (10th ~6pm PST). It is adopted
> by majority approval, with at least 3 PMC affirmative votes.
>
> Thanks,
> Robert Burke
> 2.26.0 Release Manager
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
> [2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/org apache
> beam-1144/
> [5] https://github.com/apache/beam/tree/v2.26.0-RC1
> [6] https://github.com/apache/beam/pull/13481
> [7] https://github.com/apache/beam-site/pull/609
> [8] https://github.com/apache/beam/pull/13482
> [9]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
> [10] https://hub.docker.com/search?q=apache%2Fbeam=image
>
> PS. New Dataflow artifacts likely need to be built and published but this
> doesn't block vetting the remainder of the RC at this time. Thank you for
> your patience.
>
>

[VOTE] Release 2.26.0, release candidate #1

[Robert Burke]

Robert Burke 
Thu, Dec 3, 8:01 PM (4 days ago)
to dev
Hi everyone,
Please review and vote on the release candidate #1 for the version 2.26.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
A52F5C83BAE26160120EC25F3D56ACFBFB2975E1 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v2.26.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.6.0 and OpenJDK 1.8.0_275.
* Python artifacts are deployed along with the source release to the
dist.apache.org [2].
* Validation sheet with a tab for 2.26.0 release to help with validation
[9].
* Docker images published to Docker Hub [10].

The vote will be open for at least 72 hours (10th ~6pm PST). It is adopted
by majority approval, with at least 3 PMC affirmative votes.

Thanks,
Robert Burke
2.26.0 Release Manager

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12348833
[2] https://dist.apache.org/repos/dist/dev/beam/2.26.0/
[3] https://dist.apache.org/repos/dist/release/beam/KEYS
[4] https://repository.apache.org/content/repositories/org apache beam-1144/
[5] https://github.com/apache/beam/tree/v2.26.0-RC1
[6] https://github.com/apache/beam/pull/13481
[7] https://github.com/apache/beam-site/pull/609
[8] https://github.com/apache/beam/pull/13482
[9]
https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=475997301
[10] https://hub.docker.com/search?q=apache%2Fbeam=image

PS. New Dataflow artifacts likely need to be built and published but this
doesn't block vetting the remainder of the RC at this time. Thank you for
your patience.