Hi All,
We will cancel this vote and release a new RC.
Thanks everyone,
--
Yaniv Rodenski
Hi,
Sorry but it’s -1 binding as there compiled code in the source release and some
software is of an unknown license
I checked:
- incubating name
- signatures and hashes correct
- DISCLAIMER exists
- LICENSE is missing a number of things
- NOTICE has incorrect year
- a number of source files
Thanks Justin,
The keys ware invalidated and deleted the moment we have spotted them in
the repository.
However, I just took a deeper look and it seems that the sources released
are from our master branch and not the RC branch, hence the deleted keys so
I believe a new RC is needed.
Both our
Hi,
> However, this key is a private key added by mistake by one of our
> contributors and belonged to him (and since was decommissioned). In this
> situation, is this a blocking issue? If so, we will release a new RC and
> restart the voting.
IMO given the key is no longer valid I don't see
I went through the code, and found there are some java and scala codes.
I'm not sure if you publish the jars into nexus, but I guess the key may
used to sign the artifact jars .
As the private key is leaked, I had to vote -1 for this release.
Please take good care of the key when you do the
Hi Willem,
Thanks for that, this is really strange as the key was deleted from the
source a while back and is not there in the repository (I've just double
verified looking at the git repo). I will investigate why it does come out
in the source tar.gz file.
However, this key is a private key
Hi Yaniv,
I just checked the source tar, it has the ama-key and ama-key.pub.
I'm not sure what's ama key used to.
We normally don't ship any public key in the release kit, and should never
ship private key in the release kit,
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Tue, Jun 19,
I think this should leave to the team who contribute to this project, those
projects could share different purpose but also can work together...if the
architecture is flexible enough.
Jim Apple 于2018年6月19日周二 上午5:39写道：
> Let me respond specifically to a few of these as a way to, I hope,
> inspire
Incubating progress is something how to fix such issue, there's no need
such plan at this moment
Ryan Blue 于2018年6月19日周二 上午4:13写道：
> Okay, then let me rephrase: I would like to see a plan in the Palo proposal
> for a licensing scrub to be done before graduation.
>
> I'm still a little skeptical
+1 binding
Mohammad Asif Siddiqui 于2018年6月20日周三 上午12:40写道：
> Hello All IPMC Members,
>
> This vote is open from last 6 days, please help us to verify and vote for
> this release.
>
> Regards
> Asif
>
> On 2018/06/12 08:36:01, Mohammad Asif Siddiqui
> wrote:
> > Hello All,
> >
> > This is a call
+1 binding
Mohammad Asif Siddiqui 于2018年6月20日周三 上午12:39写道：
> Hello All IPMC Members,
>
> This vote is open from last 6 days, please help us to verify and vote for
> this release.
>
> Regards
> Asif
>
>
> On 2018/06/12 09:12:02, Mohammad Asif Siddiqui
> wrote:
> > Hello All,
> >
> > This is a
Hello All IPMC Members,
This vote is open from last 6 days, please help us to verify and vote for this
release.
Regards
Asif
On 2018/06/12 08:36:01, Mohammad Asif Siddiqui wrote:
> Hello All,
>
> This is a call for vote to release Apache ServiceComb Service-Center
>
Hello All IPMC Members,
This vote is open from last 6 days, please help us to verify and vote for this
release.
Regards
Asif
On 2018/06/12 09:12:02, Mohammad Asif Siddiqui wrote:
> Hello All,
>
> This is a call for vote to release Apache ServiceComb Saga (Incubating)
>
>
> I'm not sure if Palo is just a storage system but definitely we will
> separate query engine from Palo.
>
That's great news, and I think it will benefit users of Impala and Palo.
> Of cource, as you mentioned, "this could be a lot of work", so it will
> take a long time and we also hope
Hi Ryan,
Thank you for your response.
For #1, I admit we have not build open and inclusive community so far yet,
but we have realized the importance.
So one of our aims to proposal to enter incubrator is that to build a
well-cooperated community and worked with others in Apache way.
For #2, It
Hi Dave,
Thank you for your summary.
For #1, I got it, we will find a new name ASAP within several days.
For #2, I see, about license, we are rechecking all licenses of components in
Palo, and we have fixed most of those we found as I wrote in last email. Next,
we will continue to do this
Hi Jim,
Thank you for your response.
We have reflected upon your suggestion and we agree with you for the most
part.
We will try to find out or define a cleanly interface between Palo and
Impala and to determine which parts should keep in Palo and which parts
should as patches for Impala.
I'm
17 matches
Mail list logo
