+1

> On Feb 19, 2019, at 12:02 PM, Denis Shliakhov <[email protected]> wrote:
> 
> +1
> 
> On Tue, Feb 19, 2019 at 12:01 PM Oleksandr Isniuk
> <[email protected]> wrote:
> 
>> +1
>> -----Original Message-----
>> From: Oleksandr Chaparin <[email protected]>
>> Sent: Tuesday, February 19, 2019 11:13 AM
>> To: [email protected]
>> Subject: RE: [VOTE]: Release Apache DLab (incubating) 2.1
>> 
>> +1
>> 
>> -----Original Message-----
>> From: Dmytro Liaskovskyi <[email protected]>
>> Sent: Monday, February 18, 2019 8:44 PM
>> To: [email protected]
>> Subject: Re: [VOTE]: Release Apache DLab (incubating) 2.1
>> 
>> +1
>> 
>> On 2/18/19, 15:09, "Bohdan Hliva" <[email protected]> wrote:
>> 
>>    Hello DLab community,
>> 
>>    This is a call for the vote of Apache DLab (incubating) 2.1 release.
>> 
>>    Git tag for release:
>> 
>>      *   https://github.com/apache/incubator-dlab/tree/2.1
>> 
>>    Release notes:
>> 
>>      *
>> https://github.com/apache/incubator-dlab/blob/2.1/RELEASE_NOTES.md
>> 
>>    The artifacts (source, signature and checksum) corresponding to this
>> release candidate can be found here:
>> 
>>      *   https://dist.apache.org/repos/dist/dev/incubator/dlab/2.1/
>> 
>>    This has been signed with PGP key 5C3C66D1, corresponding to
>> [email protected]<mailto:[email protected]>.
>>    KEYS file is available here:
>> 
>>      *   https://dist.apache.org/repos/dist/dev/incubator/dlab/KEYS<
>> https://dist.apache.org/repos/dist/dev/incubator/dlab/KEYS<
>> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS>>
>> 
>>    Please vote accordingly:
>>    [ ] +1 approve
>>    [ ] +0 no option
>>    [ ] -1 disapprove with a reason
>> 
>>    Thanks,
>>    The Apache DLab (incubating) team
>> 
>> 
>> B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�
>> � [��X��ܚX�K  K[XZ[
>> �  ]�][��X��ܚX�P   X��\ X� K�ܙ�B��܈ Y  ] [ۘ[  ��[X[� �  K[XZ[
>> �  ]�Z [     X��\ X� K�ܙ�B
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to