gt;> From: kishore g
>> Sent: Friday, February 8, 2019 3:34 PM
>> To: dev@pinot.apache.org
>> Subject: Re: [MENTORS] Unapproved releases
>>
>> Thanks Justin. I will take a look at it. Olivier, we might need your
>> expertise here.
>>
>> On Fri, Feb 8, 2019
ink this happens automatically by GitHub when a git tag is pushed?
>
>
>
> From: kishore g
> Sent: Friday, February 8, 2019 3:34 PM
> To: dev@pinot.apache.org
> Subject: Re: [MENTORS] Unapproved releases
>
> Thanks Justin. I will take a look at i
I think this happens automatically by GitHub when a git tag is pushed?
From: kishore g
Sent: Friday, February 8, 2019 3:34 PM
To: dev@pinot.apache.org
Subject: Re: [MENTORS] Unapproved releases
Thanks Justin. I will take a look at it. Olivier, we might need
Thanks Justin. I will take a look at it. Olivier, we might need your
expertise here.
On Fri, Feb 8, 2019 at 2:24 PM Justin Mclean wrote:
> Hi,
>
> Sorry to bother you again, but It seems this is not sinking in. I can see
> you have just marked a release candidate as a release here. [1] Mentors
> *Sent:* Wednesday, January 30, 2019 9:55:50 AM
>
> *To:* dev@pinot.apache.org
> *Cc:* kisho...@apache.org; Felix Cheung; Subbu Subramaniam
> *Subject:* Re: Unapproved releases
>
> We will be deleting all old releases/tags using the "git push --delete
> origin &qu
Subramaniam
Subject: Re: Unapproved releases
We will be deleting all old releases/tags using the "git push --delete origin
". Will do this around noon for the tags that show up in the output of
"git tag".
Will update this thread once done.
From:
29, 2019 5:20:36 PM
To: dev@pinot.apache.org
Cc: kisho...@apache.org; Felix Cheung; Subbu Subramaniam
Subject: Re: Unapproved releases
Hi,
> Would it be possible to get an exception only for the latest one until we
> make our first release (expected end of this quarter)?
IMO you
Hi,
> Would it be possible to get an exception only for the latest one until we
> make our first release (expected end of this quarter)?
IMO you would need to ask VP legal for permission. My guess (but I could be
wrong) is that they would say no and just suggest that you just make an
official
...@apache.org
Subject: Re: Unapproved releases
Hi Felix,
Thanks for quick response.
The one from Dec was made for a specific user, so we need to check with them
(at least) before removing. I will start that process right away. It was made
for them to do some performance measurements on Pinot
--
> *From:* Felix Cheung
> *Sent:* Tuesday, January 29, 2019 4:52 PM
> *To:* Subbu Subramaniam
> *Cc:* Justin Mclean; dev@pinot.apache.org; kisho...@apache.org
> *Subject:* Re: Unapproved releases
>
> Hi Subbu
>
> How are these releases made and what are
stopping checkin to the trunk.
-Subbu
From: Felix Cheung
Sent: Tuesday, January 29, 2019 4:52 PM
To: Subbu Subramaniam
Cc: Justin Mclean; dev@pinot.apache.org; kisho...@apache.org
Subject: Re: Unapproved releases
Hi Subbu
How are these releases made and what
nuary 29, 2019 3:09 PM
> *To:* Subbu Subramaniam
> *Cc:* dev@pinot.apache.org
> *Subject:* Re: Unapproved releases
>
> Hi,
>
> Is it sufficient if we write that the snapshots in the links are
> unofficial snapshots of Pinot, and that we are working on a formal apach
if there are users that are using these images.
thanks,
-Subbu
From: Justin Mclean
Sent: Tuesday, January 29, 2019 3:09 PM
To: Subbu Subramaniam
Cc: dev@pinot.apache.org
Subject: Re: Unapproved releases
Hi,
Is it sufficient if we write that the snapshots
Hi,
> Is it sufficient if we write that the snapshots in the links are unofficial
> snapshots of Pinot, and that we are working on a formal apache release?
No you are no allowed to make unofficial releases that are public in this way.
IMO they need to be removed.
It would be best to discuss
From: Justin Mclean
Sent: Tuesday, January 29, 2019 1:48 PM
To: dev@pinot.apache.org
Subject: Unapproved releases
Hi,
I'm a little concerned about the releases you have publicly available on GitHub
[1] as per [2] you must not point outsiders to any unapproved releases. Can you
include
Hi,
I'm a little concerned about the releases you have publicly available on GitHub
[1] as per [2] you must not point outsiders to any unapproved releases. Can you
include in your incubator report (due shortly) how you will address this issue.
Thanks,
Justin
P.S Please CC me on any replies
16 matches
Mail list logo
