Good point. How do I update that link? I think this step might be missing
from our release guide (or I simply can't find it).

Reuven

On Mon, Nov 20, 2017 at 4:24 PM, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:

> +1 (binding)
>
> Tested on Beam samples, it looks good.
>
> Checked the legal/license, content. OK for me.
>
> Just a side note: don't forget to update the latest link on
> dist.apache.org.
>
> Thanks
> Regards
> JB
>
>
> On 11/17/2017 07:08 AM, Reuven Lax 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/orgapache
>> beam-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
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Reply via email to