I got it :D
Happy New Year!!
Lei Rui
On 1/2/2020 10:16，Kevin A. McGrail wrote：
Justin is correct. I was trying to be silly with the Happy New Year
note :-)
Happy New year and my apologies for the sarcasm via email.
Regards,
KAM
On 1/1/2020 8:55 PM, Lei Rui wrote:
Hi KAM,
I am a little
Justin is correct. I was trying to be silly with the Happy New Year
note :-)
Happy New year and my apologies for the sarcasm via email.
Regards,
KAM
On 1/1/2020 8:55 PM, Lei Rui wrote:
> Hi KAM,
>
>
> I am a little confused. Do you mean the NOTICE can't be changed to "Apache
> IoTDB
Hi,
I think he may of been joking, but it often hard to tell in email.
It currently 2020 now, what you release soon will be copyright 2020 no matter
what you put down as the year, but it’s nice if the year matches.
Thanks,
Justin
Hi KAM,
I am a little confused. Do you mean the NOTICE can't be changed to "Apache
IoTDB Copyright 2018-2020" until it is 2021?
Regards,
Lei Rui
On 1/2/2020 03:02，Kevin A. McGrail wrote：
I am going to vote -1 and insist we change back to 2019.
Happy New Year,
KAM
On Mon, Dec 30, 2019,
I am going to vote -1 and insist we change back to 2019.
Happy New Year,
KAM
On Mon, Dec 30, 2019, 20:58 Lei Rui wrote:
> Thank you all for the suggestions!
> I have changed the year to 2020 in the NOTICE file.
> Hopefully, the release vote of 0.9.1 will be initiated today.
>
>
> Regards,
>
Thank you all for the suggestions!
I have changed the year to 2020 in the NOTICE file.
Hopefully, the release vote of 0.9.1 will be initiated today.
Regards,
Lei Rui
On 12/28/2019 11:11，Xiangdong Huang wrote：
+1. Look forward to the new release version.
---
+1. Look forward to the new release version.
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
jincheng sun 于2019年12月28日周六 上午7:30写道：
> I think 2020 would be fine ：）
>
> Christofer Dutz 于2019年12月28日 周六00:45写道：
>
> > +1 From me too
> >
>
I think 2020 would be fine ：）
Christofer Dutz 于2019年12月28日 周六00:45写道：
> +1 From me too
>
> Chris
>
> Am 27.12.19, 17:40 schrieb "Kevin A. McGrail" :
>
> +1 to update in advance just make sure not to announce the release
> until
> 2020.
>
> On 12/27/2019 10:32 AM, Lei Rui wrote:
>
+1 From me too
Chris
Am 27.12.19, 17:40 schrieb "Kevin A. McGrail" :
+1 to update in advance just make sure not to announce the release until
2020.
On 12/27/2019 10:32 AM, Lei Rui wrote:
> Hi,
>
>
> I am the release manager of the upcoming 0.9.1 and I encounter
+1 to update in advance just make sure not to announce the release until
2020.
On 12/27/2019 10:32 AM, Lei Rui wrote:
> Hi,
>
>
> I am the release manager of the upcoming 0.9.1 and I encounter an interesting
> question:
>
>
> As you can see, Year 2020 is just around the corner and the upcoming
Hi,
I am the release manager of the upcoming 0.9.1 and I encounter an interesting
question:
As you can see, Year 2020 is just around the corner and the upcoming release
vote for 0.9.1
is likely to span from 2019 to 2020. So I don't know if I should change the
year in advance
to 2020, or
11 matches
Mail list logo
