You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pinot.apache.org by Justin Mclean <jm...@apache.org> on 2019/01/29 21:48:09 UTC
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 in your incubator report (due shortly) how you will address this issue.
Thanks,
Justin
P.S Please CC me on any replies as I'm not subscribed to this list
1. https://github.com/apache/incubator-pinot/releases
2. http://www.apache.org/legal/release-policy.html#publication
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
For additional commands, e-mail: dev-help@pinot.apache.org
Re: [MENTORS] Unapproved releases
Posted by Seunghyun Lee <sn...@apache.org>.
I removed those from github release page.
Best,
Seunghyun
On Fri, Feb 8, 2019 at 5:05 PM Seunghyun Lee <sn...@apache.org> wrote:
> Sorry for this. I was trying out the maven-release plugin (first time to
> use this plugin) and this got automatically created. I will probably go
> with an option of doing it manually.
>
> I will clean up these.
>
> Best,
> Seunghyun
>
> On Fri, Feb 8, 2019 at 4:56 PM Felix Cheung <fe...@hotmail.com>
> wrote:
>
>> I think this happens automatically by GitHub when a git tag is pushed?
>>
>>
>> ________________________________
>> From: kishore g <g....@gmail.com>
>> 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 at 2:24 PM Justin Mclean <jm...@apache.org> 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
>> can
>> > you please deal with this.
>> >
>> > Thanks,
>> > Justin
>> >
>> > 1. https://github.com/apache/incubator-pinot/releases
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
>> > For additional commands, e-mail: dev-help@pinot.apache.org
>> >
>> >
>>
>
Re: [MENTORS] Unapproved releases
Posted by Seunghyun Lee <sn...@apache.org>.
Sorry for this. I was trying out the maven-release plugin (first time to
use this plugin) and this got automatically created. I will probably go
with an option of doing it manually.
I will clean up these.
Best,
Seunghyun
On Fri, Feb 8, 2019 at 4:56 PM Felix Cheung <fe...@hotmail.com>
wrote:
> I think this happens automatically by GitHub when a git tag is pushed?
>
>
> ________________________________
> From: kishore g <g....@gmail.com>
> 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 at 2:24 PM Justin Mclean <jm...@apache.org> 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
> can
> > you please deal with this.
> >
> > Thanks,
> > Justin
> >
> > 1. https://github.com/apache/incubator-pinot/releases
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
> > For additional commands, e-mail: dev-help@pinot.apache.org
> >
> >
>
Re: [MENTORS] Unapproved releases
Posted by Felix Cheung <fe...@hotmail.com>.
I think this happens automatically by GitHub when a git tag is pushed?
________________________________
From: kishore g <g....@gmail.com>
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 at 2:24 PM Justin Mclean <jm...@apache.org> 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 can
> you please deal with this.
>
> Thanks,
> Justin
>
> 1. https://github.com/apache/incubator-pinot/releases
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
> For additional commands, e-mail: dev-help@pinot.apache.org
>
>
Re: [MENTORS] Unapproved releases
Posted by kishore g <g....@gmail.com>.
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 <jm...@apache.org> 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 can
> you please deal with this.
>
> Thanks,
> Justin
>
> 1. https://github.com/apache/incubator-pinot/releases
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
> For additional commands, e-mail: dev-help@pinot.apache.org
>
>
[MENTORS] Unapproved releases
Posted by Justin Mclean <jm...@apache.org>.
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 can you please deal with this.
Thanks,
Justin
1. https://github.com/apache/incubator-pinot/releases
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
For additional commands, e-mail: dev-help@pinot.apache.org
Re: Unapproved releases
Posted by Justin Mclean <jm...@apache.org>.
Hi,
Thanks for dealing with this quickly.
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
For additional commands, e-mail: dev-help@pinot.apache.org
Re: Unapproved releases
Posted by Felix Cheung <fe...@apache.org>.
Thanks for the prompt action!
On Wed, Jan 30, 2019 at 2:03 PM Sunitha Beeram <sb...@linkedin.com> wrote:
> The releases/tags have been cleanedup.
> https://github.com/apache/incubator-pinot/releases is now empty.
>
> Thanks
> Sunitha
> ------------------------------
> *From:* Sunitha Beeram <sb...@linkedin.com>
> *Sent:* Wednesday, January 30, 2019 9:55:50 AM
>
> *To:* dev@pinot.apache.org
> *Cc:* kishoreg@apache.org; Felix Cheung; Subbu Subramaniam
> *Subject:* Re: Unapproved releases
>
> We will be deleting all old releases/tags using the "git push --delete
> origin <tag>". Will do this around noon for the tags that show up in the
> output of "git tag".
>
>
> Will update this thread once done.
>
> ________________________________
> From: Justin Mclean <jm...@apache.org>
> Sent: Tuesday, January 29, 2019 5:20:36 PM
> To: dev@pinot.apache.org
> Cc: kishoreg@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 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 release.
>
> I do know of a couple of projects that have been allowed to make
> unofficial releases shortly after entering incubation, but they asked
> before making the release and it was clearly marked so to not cause any
> confusion with official releases.
>
> ASF release policy is quite clear:
> "Projects MUST direct outsiders towards official releases rather than raw
> source repositories, nightly builds, snapshots, release candidates, or any
> other similar packages."
>
> Thanks,
> Justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
> For additional commands, e-mail: dev-help@pinot.apache.org
>
>
Re: Unapproved releases
Posted by Sunitha Beeram <sb...@linkedin.com>.
The releases/tags have been cleanedup. https://github.com/apache/incubator-pinot/releases is now empty.
Thanks
Sunitha
________________________________
From: Sunitha Beeram <sb...@linkedin.com>
Sent: Wednesday, January 30, 2019 9:55:50 AM
To: dev@pinot.apache.org
Cc: kishoreg@apache.org; Felix Cheung; Subbu Subramaniam
Subject: Re: Unapproved releases
We will be deleting all old releases/tags using the "git push --delete origin <tag>". Will do this around noon for the tags that show up in the output of "git tag".
Will update this thread once done.
________________________________
From: Justin Mclean <jm...@apache.org>
Sent: Tuesday, January 29, 2019 5:20:36 PM
To: dev@pinot.apache.org
Cc: kishoreg@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 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 release.
I do know of a couple of projects that have been allowed to make unofficial releases shortly after entering incubation, but they asked before making the release and it was clearly marked so to not cause any confusion with official releases.
ASF release policy is quite clear:
"Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages."
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
For additional commands, e-mail: dev-help@pinot.apache.org
Re: Unapproved releases
Posted by Sunitha Beeram <sb...@linkedin.com>.
We will be deleting all old releases/tags using the "git push --delete origin <tag>". Will do this around noon for the tags that show up in the output of "git tag".
Will update this thread once done.
________________________________
From: Justin Mclean <jm...@apache.org>
Sent: Tuesday, January 29, 2019 5:20:36 PM
To: dev@pinot.apache.org
Cc: kishoreg@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 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 release.
I do know of a couple of projects that have been allowed to make unofficial releases shortly after entering incubation, but they asked before making the release and it was clearly marked so to not cause any confusion with official releases.
ASF release policy is quite clear:
"Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages."
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
For additional commands, e-mail: dev-help@pinot.apache.org
Re: Unapproved releases
Posted by Justin Mclean <jm...@apache.org>.
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 release.
I do know of a couple of projects that have been allowed to make unofficial releases shortly after entering incubation, but they asked before making the release and it was clearly marked so to not cause any confusion with official releases.
ASF release policy is quite clear:
"Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages."
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
For additional commands, e-mail: dev-help@pinot.apache.org
Re: Unapproved releases
Posted by Subbu Subramaniam <ss...@linkedin.com>.
I also noticed that the only way to delete releases from this page (that I could find) was to click on edit, remove the zip file, which then takes me to a page that has a delete button, and I click on delete.
I noticed that there are probably 100+ releases in that page.
Is there a quicker way to delete these?
I confirm that we can drop these releases, so if you can do a mass delete at your end that will be awesome.
-Subbu
________________________________
From: Subbu Subramaniam <ss...@linkedin.com>
Sent: Tuesday, January 29, 2019 5:00 PM
To: Felix Cheung
Cc: Justin Mclean; dev@pinot.apache.org; kishoreg@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. The previous one was too old, and did not have most new features we added.
We can certainly remove the older versions from that page. Would it be possible to get an exception only for the latest one until we make our first release (expected end of this quarter)?
Yes, we do plan to go to branch-based releases, much easier to manage without stopping checkin to the trunk.
-Subbu
________________________________
From: Felix Cheung <fe...@apache.org>
Sent: Tuesday, January 29, 2019 4:52 PM
To: Subbu Subramaniam
Cc: Justin Mclean; dev@pinot.apache.org; kishoreg@apache.org
Subject: Re: Unapproved releases
Hi Subbu
How are these releases made and what are they useful for?
Generally, it’s not good to have unofficial unvoted releases, and having these visible links on GitHub can be confusing. To me the biggest concern is github doesn’t give you a way to note these are unofficial and unsupported releases. But even if there is a place to write note it can still be confusing as this is the same place other non-ASF projects have releases.
Can I suggest to remove these for now?
I think you can mitigate this with tag or commit id for now. Hopefully the community can build from source from this point in time references.
Also it might be a good move to version branching structure. This is commonly done in other projects and it gives an easy access to point in time reference, and in the future release and maintanence.
(I see there is also one release from Dec 2018 - that’s after entering incubation AFAIK)
On Tue, Jan 29, 2019 at 4:30 PM Subbu Subramaniam <ss...@linkedin.com>> wrote:
Hi Felix/Kishore,
Justin has pointed out that we (Pinot) have snapshot releases that are not through the apache web site, and in his opinion these need to be removed.
He has suggested that we discuss with our mentors and put out an appropriate note in this month's podling report.
IIRC these releases were present before we incubated into apache. We would like to keep them there until we get the first release out via apache.
We are working hard to get the first release out this quarter.
Do you suggest that we take them out, or let them be until the end of the quarter. We don't know if there are users that are using these images.
thanks,
-Subbu
________________________________
From: Justin Mclean <jm...@apache.org>>
Sent: Tuesday, January 29, 2019 3:09 PM
To: Subbu Subramaniam
Cc: dev@pinot.apache.org<ma...@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 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 this with your mentors and see what they have to say.
Thanks,
Justin
Re: Unapproved releases
Posted by Felix Cheung <fe...@apache.org>.
IMO the last one is after incubation which is the biggest problem here.
Other releases were from 2017.
Is there a way this user can make do with commit tag, and build from source?
Also, I’d also encourage discussions or requests with this user to be on
dev@ - as the community can benefit from that conversation and it
performance work as well. And perhaps we could get to an acceptable
alternative there.
On Tue, Jan 29, 2019 at 5:00 PM Subbu Subramaniam <ss...@linkedin.com>
wrote:
> 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. The
> previous one was too old, and did not have most new features we added.
>
> We can certainly remove the older versions from that page. Would it be
> possible to get an exception only for the latest one until we make our
> first release (expected end of this quarter)?
>
> Yes, we do plan to go to branch-based releases, much easier to manage
> without stopping checkin to the trunk.
>
> -Subbu
> ------------------------------
> *From:* Felix Cheung <fe...@apache.org>
> *Sent:* Tuesday, January 29, 2019 4:52 PM
> *To:* Subbu Subramaniam
> *Cc:* Justin Mclean; dev@pinot.apache.org; kishoreg@apache.org
> *Subject:* Re: Unapproved releases
>
> Hi Subbu
>
> How are these releases made and what are they useful for?
>
> Generally, it’s not good to have unofficial unvoted releases, and having
> these visible links on GitHub can be confusing. To me the biggest concern
> is github doesn’t give you a way to note these are unofficial and
> unsupported releases. But even if there is a place to write note it can
> still be confusing as this is the same place other non-ASF projects have
> releases.
>
> Can I suggest to remove these for now?
>
> I think you can mitigate this with tag or commit id for now. Hopefully the
> community can build from source from this point in time references.
>
> Also it might be a good move to version branching structure. This is
> commonly done in other projects and it gives an easy access to point in
> time reference, and in the future release and maintanence.
>
> (I see there is also one release from Dec 2018 - that’s after entering
> incubation AFAIK)
>
>
>
> On Tue, Jan 29, 2019 at 4:30 PM Subbu Subramaniam <
> ssubramaniam@linkedin.com> wrote:
>
> Hi Felix/Kishore,
>
> Justin has pointed out that we (Pinot) have snapshot releases that are not
> through the apache web site, and in his opinion these need to be removed.
> He has suggested that we discuss with our mentors and put out an
> appropriate note in this month's podling report.
>
> IIRC these releases were present before we incubated into apache. We
> would like to keep them there until we get the first release out via apache.
> We are working hard to get the first release out this quarter.
>
> Do you suggest that we take them out, or let them be until the end of the
> quarter. We don't know if there are users that are using these images.
>
> thanks,
>
> -Subbu
> ------------------------------
> *From:* Justin Mclean <jm...@apache.org>
> *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 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 this with your mentors and see what they have
> to say.
>
> Thanks,
> Justin
>
>
Re: Unapproved releases
Posted by Subbu Subramaniam <ss...@linkedin.com>.
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. The previous one was too old, and did not have most new features we added.
We can certainly remove the older versions from that page. Would it be possible to get an exception only for the latest one until we make our first release (expected end of this quarter)?
Yes, we do plan to go to branch-based releases, much easier to manage without stopping checkin to the trunk.
-Subbu
________________________________
From: Felix Cheung <fe...@apache.org>
Sent: Tuesday, January 29, 2019 4:52 PM
To: Subbu Subramaniam
Cc: Justin Mclean; dev@pinot.apache.org; kishoreg@apache.org
Subject: Re: Unapproved releases
Hi Subbu
How are these releases made and what are they useful for?
Generally, it’s not good to have unofficial unvoted releases, and having these visible links on GitHub can be confusing. To me the biggest concern is github doesn’t give you a way to note these are unofficial and unsupported releases. But even if there is a place to write note it can still be confusing as this is the same place other non-ASF projects have releases.
Can I suggest to remove these for now?
I think you can mitigate this with tag or commit id for now. Hopefully the community can build from source from this point in time references.
Also it might be a good move to version branching structure. This is commonly done in other projects and it gives an easy access to point in time reference, and in the future release and maintanence.
(I see there is also one release from Dec 2018 - that’s after entering incubation AFAIK)
On Tue, Jan 29, 2019 at 4:30 PM Subbu Subramaniam <ss...@linkedin.com>> wrote:
Hi Felix/Kishore,
Justin has pointed out that we (Pinot) have snapshot releases that are not through the apache web site, and in his opinion these need to be removed.
He has suggested that we discuss with our mentors and put out an appropriate note in this month's podling report.
IIRC these releases were present before we incubated into apache. We would like to keep them there until we get the first release out via apache.
We are working hard to get the first release out this quarter.
Do you suggest that we take them out, or let them be until the end of the quarter. We don't know if there are users that are using these images.
thanks,
-Subbu
________________________________
From: Justin Mclean <jm...@apache.org>>
Sent: Tuesday, January 29, 2019 3:09 PM
To: Subbu Subramaniam
Cc: dev@pinot.apache.org<ma...@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 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 this with your mentors and see what they have to say.
Thanks,
Justin
Re: Unapproved releases
Posted by Felix Cheung <fe...@apache.org>.
Hi Subbu
How are these releases made and what are they useful for?
Generally, it’s not good to have unofficial unvoted releases, and having
these visible links on GitHub can be confusing. To me the biggest concern
is github doesn’t give you a way to note these are unofficial and
unsupported releases. But even if there is a place to write note it can
still be confusing as this is the same place other non-ASF projects have
releases.
Can I suggest to remove these for now?
I think you can mitigate this with tag or commit id for now. Hopefully the
community can build from source from this point in time references.
Also it might be a good move to version branching structure. This is
commonly done in other projects and it gives an easy access to point in
time reference, and in the future release and maintanence.
(I see there is also one release from Dec 2018 - that’s after entering
incubation AFAIK)
On Tue, Jan 29, 2019 at 4:30 PM Subbu Subramaniam <ss...@linkedin.com>
wrote:
> Hi Felix/Kishore,
>
> Justin has pointed out that we (Pinot) have snapshot releases that are not
> through the apache web site, and in his opinion these need to be removed.
> He has suggested that we discuss with our mentors and put out an
> appropriate note in this month's podling report.
>
> IIRC these releases were present before we incubated into apache. We
> would like to keep them there until we get the first release out via apache.
> We are working hard to get the first release out this quarter.
>
> Do you suggest that we take them out, or let them be until the end of the
> quarter. We don't know if there are users that are using these images.
>
> thanks,
>
> -Subbu
> ------------------------------
> *From:* Justin Mclean <jm...@apache.org>
> *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 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 this with your mentors and see what they have
> to say.
>
> Thanks,
> Justin
>
Re: Unapproved releases
Posted by Subbu Subramaniam <ss...@linkedin.com>.
Hi Felix/Kishore,
Justin has pointed out that we (Pinot) have snapshot releases that are not through the apache web site, and in his opinion these need to be removed.
He has suggested that we discuss with our mentors and put out an appropriate note in this month's podling report.
IIRC these releases were present before we incubated into apache. We would like to keep them there until we get the first release out via apache.
We are working hard to get the first release out this quarter.
Do you suggest that we take them out, or let them be until the end of the quarter. We don't know if there are users that are using these images.
thanks,
-Subbu
________________________________
From: Justin Mclean <jm...@apache.org>
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 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 this with your mentors and see what they have to say.
Thanks,
Justin
Re: Unapproved releases
Posted by Justin Mclean <jm...@apache.org>.
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 this with your mentors and see what they have to say.
Thanks,
Justin
Re: Unapproved releases
Posted by Subbu Subramaniam <ss...@linkedin.com>.
Hi Justin,
Sure, we can include something in the report.
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? (the latter part is there in the report anyway)
thanks
-Subbu
________________________________
From: Justin Mclean <jm...@apache.org>
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 in your incubator report (due shortly) how you will address this issue.
Thanks,
Justin
P.S Please CC me on any replies as I'm not subscribed to this list
1. https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-pinot%2Freleases&data=02%7C01%7Cssubramaniam%40linkedin.com%7C87694dae28654488ff5a08d6863379a2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636843952976181801&sdata=CVcATUIfOputFdbBASr2Trgq40fTLSurX40SsvWpK1g%3D&reserved=0
2. https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Flegal%2Frelease-policy.html%23publication&data=02%7C01%7Cssubramaniam%40linkedin.com%7C87694dae28654488ff5a08d6863379a2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636843952976181801&sdata=lIjOPfxfBe%2F%2BVJh5bNy4NPklmUzDNDgNTC7OK5BrD%2FQ%3D&reserved=0
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org
For additional commands, e-mail: dev-help@pinot.apache.org