72 hours have passed. I am happy to announce that we are migrating the Jenkins
to the GitHub Actions.

The vote has passed with 6 +1 votes, 0 +0 votes and 0 -1 votes.

The 5 +1 votes include 3 binding votes and 3 non-binding votes.

The 3 binding votes are:

- Enrico Olivelli
- Jia Zhai
- Sijie Guo

The 3 non-binding votes are:

- Alessandras Luccaroni
- Yong Zhang
- Guangning E

FYI, the PR about migrate the Github Action has been merged, you can trigger the
Github Action by rebasing the code.

Thanks,
Yong

> On Jan 22, 2020, at 9:15 PM, Guangning E <eguangn...@gmail.com> wrote:
> 
> Great, +1 (non-binding)
> 
> Thanks,
> Guangning
> 
> Enrico Olivelli <eolive...@gmail.com> 于2020年1月22日周三 下午4:51写道:
> 
>> +1 binding
>> 
>> Already approved the PR
>> https://github.com/apache/bookkeeper/pull/2246
>> 
>> Thank you
>> Enrico
>> 
>> Il giorno mar 21 gen 2020 alle ore 04:53 Sijie Guo <guosi...@gmail.com> ha
>> scritto:
>> 
>>> +1 binding
>>> 
>>> On Mon, Jan 20, 2020 at 6:50 PM Jia Zhai <zhaiji...@gmail.com> wrote:
>>> 
>>>> +1
>>>> 
>>>> Best Regards.
>>>> 
>>>> 
>>>> Jia Zhai
>>>> 
>>>> Beijing, China
>>>> 
>>>> Mobile: +86 15810491983
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Sat, Jan 18, 2020 at 12:48 AM Alessandro Luccaroni - Diennea <
>>>> alessandro.luccar...@diennea.com> wrote:
>>>> 
>>>>> +1 (non-binding)
>>>>> 
>>>>> Alessandro
>>>>> 
>>>>>> -----Messaggio originale-----
>>>>>> Da: Yong Zhang <zhangyong1025...@gmail.com>
>>>>>> Inviato: venerdì 17 gennaio 2020 15:21
>>>>>> A: dev@bookkeeper.apache.org
>>>>>> Oggetto: [VOTE] Migrate the Jenkins CI to Github Actions
>>>>>> 
>>>>>> Hi, BookKeepers
>>>>>> 
>>>>>> Since the Jenkins CI is not anymore working when a new pull request
>>>>>> created. This is a vote to migrate the Jenkins to Github Actions.
>>>>>> 
>>>>>> Please vote with your opinions. The vote will be open for at least
>> 72
>>>>> hours.
>>>>>> 
>>>>>> Thanks,
>>>>>> Yong
>>>>> 
>>>>> ________________________________
>>>>> 
>>>>> CONFIDENTIALITY & PRIVACY NOTICE
>>>>> This e-mail (including any attachments) is strictly confidential and
>>> may
>>>>> also contain privileged information. If you are not the intended
>>>> recipient
>>>>> you are not authorised to read, print, save, process or disclose this
>>>>> message. If you have received this message by mistake, please inform
>>> the
>>>>> sender immediately and destroy this e-mail, its attachments and any
>>>> copies.
>>>>> Any use, distribution, reproduction or disclosure by any person other
>>>> than
>>>>> the intended recipient is strictly prohibited and the person
>>> responsible
>>>>> may incur in penalties.
>>>>> The use of this e-mail is only for professional purposes; there is no
>>>>> guarantee that the correspondence towards this e-mail will be read
>> only
>>>> by
>>>>> the recipient, because, under certain circumstances, there may be a
>>> need
>>>> to
>>>>> access this email by third subjects belonging to the Company.
>>>>> 
>>>> 
>>> 
>> 

Reply via email to