Hi all,

Following up on past discussions and
https://issues.apache.org/jira/browse/BEAM-1189 I have prepared a
spreadsheet so we can sign up for validation steps that must be done by a
human.

The spreadsheet for 2.2.0 is at
https://s.apache.org/beam-2.2.0-release-validation. Everyone can edit, so
it is easy to sign up or add new rows.

FYI the template is at https://s.apache.org/beam-release-validation. After
this release, I will update the rows in the template to match whatever we
have added to the validation for 2.2.0.

Kenn


On Thu, Nov 16, 2017 at 10:08 PM, Reuven Lax <re...@google.com.invalid>
wrote:

> Hi everyone,
>
> Please review and vote on the release candidate #4 for the version 2.2.0,
> as follows:
>   [ ] +1, Approve the release
>   [ ] -1, Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
>   * 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 B98B7708 [3],
>   * all artifacts to be deployed to the Maven Central Repository [4],
>   * source code tag "v2.2.0-RC4" [5],
>   * website pull request listing the release and publishing the API
> reference manual [6].
>   * Java artifacts were built with Maven 3.5.0 and OpenJDK/Oracle JDK
> 1.8.0_144.
>   * Python artifacts are deployed along with the source release to the
> dist.apache.org [2].
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> Thanks,
> Reuven
>
> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?p
> rojectId=12319527&version=12341044
> [2] https://dist.apache.org/repos/dist/dev/beam/2.2.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1025/
> [5] https://github.com/apache/beam/tree/v2.2.0-RC4
> <https://github.com/apache/beam/tree/v2.2.0-RC4>
> [6] https://github.com/apache/beam-site/pull/337
>

Reply via email to