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

There are 5 approving votes, 3 of which are binding:

* Lukasz Cwik

* Kenneth Knowles

* Ahmet Altay

There are no disapproving votes.

Thanks everyone!

On Tue, Sep 3, 2019 at 1:29 PM Lukasz Cwik <lc...@google.com> wrote:

> +1
>
> On Tue, Sep 3, 2019 at 1:22 PM Kenneth Knowles <k...@apache.org> wrote:
>
>> +1
>>
>> On Tue, Sep 3, 2019 at 11:00 AM Ahmet Altay <al...@google.com> wrote:
>>
>>> +1
>>>
>>> On Tue, Sep 3, 2019 at 10:52 AM Andrew Pilloud <apill...@google.com>
>>> wrote:
>>>
>>>> +1
>>>>
>>>> Inspected the jar it looked reasonable.
>>>>
>>>> Andrew
>>>>
>>>> On Tue, Sep 3, 2019 at 9:06 AM Rui Wang <ruw...@google.com> wrote:
>>>>
>>>>> Friendly ping.
>>>>>
>>>>>
>>>>> -Rui
>>>>>
>>>>> On Thu, Aug 29, 2019 at 9:50 AM Rui Wang <ruw...@google.com> wrote:
>>>>>
>>>>>> Thanks Kai and Andrew. Now prgapachebeam-1083 is publicly exposed.
>>>>>>
>>>>>> I also found a useful link[1] to explain staging repos in Apache Nexus
>>>>>>
>>>>>>
>>>>>> [1]:
>>>>>> https://help.sonatype.com/repomanager2/staging-releases/managing-staging-repositories#ManagingStagingRepositories-ClosinganOpenRepository
>>>>>>
>>>>>> -Rui
>>>>>>
>>>>>> On Wed, Aug 28, 2019 at 9:19 PM Andrew Pilloud <apill...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> You need to close the release for it to be published to the staging
>>>>>>> server. I can help if you still have questions.
>>>>>>>
>>>>>>> Andrew
>>>>>>>
>>>>>>> On Wed, Aug 28, 2019, 8:48 PM Rui Wang <ruw...@google.com> wrote:
>>>>>>>
>>>>>>>> I can see prgapachebeam-1083 is in open status in staging
>>>>>>>> repository. I am not sure why it is not public exposed. I probably need
>>>>>>>> some guidance on it.
>>>>>>>>
>>>>>>>>
>>>>>>>> -Rui
>>>>>>>>
>>>>>>>> On Wed, Aug 28, 2019 at 3:50 PM Kai Jiang <jiang...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Rui,
>>>>>>>>>
>>>>>>>>> For accessing artifacts [1] in Maven Central Repository, is this
>>>>>>>>> intent to be not public exposed?
>>>>>>>>>
>>>>>>>>> Best,
>>>>>>>>> Kai
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://repository.apache.org/content/repositories/orgapachebeam-1083/
>>>>>>>>>
>>>>>>>>> On Wed, Aug 28, 2019 at 11:57 AM Kai Jiang <jiang...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1 (non-binding)    Thanks Rui!
>>>>>>>>>>
>>>>>>>>>> On Tue, Aug 27, 2019 at 10:46 PM Rui Wang <ruw...@google.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Please review the release of the following artifacts that we
>>>>>>>>>>> vendor:
>>>>>>>>>>>
>>>>>>>>>>>  * beam-vendor-calcite-1_20_0
>>>>>>>>>>>
>>>>>>>>>>> Hi everyone,
>>>>>>>>>>>
>>>>>>>>>>> Please review and vote on the release candidate #1 for the
>>>>>>>>>>> org.apache.beam:beam-vendor-calcite-1_20_0:0.1, 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:
>>>>>>>>>>>
>>>>>>>>>>> * the official Apache source release to be deployed to
>>>>>>>>>>> dist.apache.org [1], which is signed with the key with
>>>>>>>>>>> fingerprint 0D7BE1A252DBCEE89F6491BBDFA64862B703F5C8 [2],
>>>>>>>>>>>
>>>>>>>>>>> * all artifacts to be deployed to the Maven Central Repository
>>>>>>>>>>> [3],
>>>>>>>>>>>
>>>>>>>>>>> * commit hash "664e25019fc1977e7041e4b834e8d9628b912473" [4],
>>>>>>>>>>>
>>>>>>>>>>> The vote will be open for at least 72 hours. It is adopted by
>>>>>>>>>>> majority approval, with at least 3 PMC affirmative votes.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Rui
>>>>>>>>>>>
>>>>>>>>>>> [1]
>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/beam/vendor/calcite/1_20_0
>>>>>>>>>>>
>>>>>>>>>>> [2] https://dist.apache.org/repos/dist/release/beam/KEYS
>>>>>>>>>>>
>>>>>>>>>>> [3]
>>>>>>>>>>> https://repository.apache.org/content/repositories/orgapachebeam-1083/
>>>>>>>>>>>
>>>>>>>>>>> [4]
>>>>>>>>>>> https://github.com/apache/beam/commit/664e25019fc1977e7041e4b834e8d9628b912473
>>>>>>>>>>>
>>>>>>>>>>>

Reply via email to