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 <[email protected]> Sent: Tuesday, January 29, 2019 5:00 PM To: Felix Cheung Cc: Justin Mclean; [email protected]; [email protected] 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 <[email protected]> Sent: Tuesday, January 29, 2019 4:52 PM To: Subbu Subramaniam Cc: Justin Mclean; [email protected]; [email protected] 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 <[email protected]<mailto:[email protected]>> 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 <[email protected]<mailto:[email protected]>> Sent: Tuesday, January 29, 2019 3:09 PM To: Subbu Subramaniam Cc: [email protected]<mailto:[email protected]> 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
