Re: Pre-apache convenience releases
Hi, > We do have a healthy flow of discussion at http://apache-superset.slack.com > that anyone can join from our project page at > https://github.com/apache/incubator-superset. My impression is that this > has been a more effective forum for communication than the dev@ list. While it's fine for causal conversation it is not fine to have the majority of discussion on the project there: For instance: 1. Not everyone can or wants to sign up to slack 2. The conversions is not archived at the ASF 3. Real time messaging disadvantages for those not in the same time zone 4, Real time communication tend to be high bandwidth / low value unlike email when tends to have a higher information content When a question is answered on slack that answer is very quickly lost and hard to search for unlike if it was archived here. If you do a search the ASF mailing lists you see many discussions about this and what limits should be placed on Slack and similar technologies. While each project is different it might be good to see what other project are doing in this regard. > Understandably, we should have votes on the dev@ list, but it would be good > to know if we can also host discussions on Slack. You need more than just votes on dev list. > And correct, there are no project leads on ASF. Please do not take my > email signature out of context. Is was not out of context you posted to the dev list using it. If you know that to be the case why use it here? I've started a conversation about the project on the IPMC private list, I encourage your mentors to reply to that. Thanks, Justin
Re: Pre-apache convenience releases
Justin, We do have a healthy flow of discussion at http://apache-superset.slack.com that anyone can join from our project page at https://github.com/apache/incubator-superset. My impression is that this has been a more effective forum for communication than the dev@ list. Understandably, we should have votes on the dev@ list, but it would be good to know if we can also host discussions on Slack. And correct, there are no project leads on ASF. Please do not take my email signature out of context. Thanks, Jeff On Sat, Dec 1, 2018 at 1:55 PM Justin Mclean wrote: > Hi, > > > Justin - thanks for the reminder on bringing back discussion from the > > bi-weekly meetings back to the mailing list. It is sincerely > > unintentional. > > The best solution would be to not have them and move all discussion to the > mailing list, that way all of the community curl be involved especially > those in other time zones. > > > Product Lead > > There are no project leads at the ASF. > > Thanks, > Justin > > >
Re: Pre-apache convenience releases
Hi, Sorry for my double email there, I though the first one has not been sent, just treat them as a single email as their contents are similar. Thanks, Justin
Re: Pre-apache convenience releases
Hi, > Justin - thanks for the reminder on bringing back discussion from the > bi-weekly meetings back to the mailing list. It is sincerely > unintentional. The best solution would be to not have them and move all discussion to the mailing list, that way all of the community curl be involved especially those in other time zones. > Product Lead There are no project leads at the ASF. Thanks, Justin
Re: Pre-apache convenience releases
Hi, Projects at the ASF release source code. You make a release candidate that complies with ASF release policy, vote on it and release it on ASF infrastructure. You can optionally make a binary convenance release at the same time.That binary release must match what's in the source release. Please see ASF release policy, in particular [1] So in answer to you question you need to make a source releases and vote on that. This has been discussed before on this list but I can see that you continue to make releases outside of the ASF. I also note that this release has not been discussed on this list and there doesn't seems to be much else being discussed. Why is this and where are this discussions taking place? I also note that you have continued with the bi-weekly meetings but are not bringing back anything to this list, including decisions made in them, for discussion. How do you expect to grow your community outside the people employed to work on it if you continue in these behaviours? The above issues have been pointed out several times now. I like to see what the project is going to do to correct this in their next report which is due the 5th Dec. I'll also be starting a discussion in the IPMC on if this project should continue at the ASF or not. Thanks, Justin 1.http://www.apache.org/legal/release-policy.html#compiled-packages
Re: Introduction and offer to help with mentoring
+gene...@incubator.apache.org Could anyone help direct us as to how we can add Alan Gates as a mentor on our Superset Roster page? https://whimsy.apache.org/roster/ppmc/superset Thanks, Jeff On Fri, Oct 5, 2018 at 6:27 AM Maxime Beauchemin wrote: > Very glad to have you on board Alan! > > Let's revive the thread titled "Our first Apache release". I'd love more > mentor input on the topic. > > Max > > On Thu, Oct 4, 2018 at 10:47 PM Stephanie Rivera > > wrote: > > > Welcome Alan!!! Thanks for joining us > > > > Cheers, > > > > Stephanie > > > > > > *Stephanie Rivera* |* Sr. Director of Data Intelligence* > > > > 8181 Arista Place | Suite 300 | Broomfield, CO 80021 | Westminster, CO > > 80020 > > < > > > http://www.google.com/url?q=http%3A%2F%2Fwww.spotxchange.com%2F=D=1=AFrqEzdlZjMtAvYRCQByfN6D_6PjZhSbSw > > > > > > > < > > > https://www.google.com/url?q=https%3A%2F%2Fdl.dropbox.com%2Fs%2F5se5ucpqodjsq1h%2Flinkedin.png=D=1=AFrqEzdTHQrlDWywpW7VZVpwGJJdOBY-Wg > > > > > > > > > > > > > On Thu, Oct 4, 2018 at 7:58 PM Luke Han wrote: > > > > > That's great and happy to see new mentor join this community. > > > > > > Best Regards! > > > - > > > > > > Luke Han > > > > > > > > > On Wed, Oct 3, 2018 at 5:52 AM Alan Gates > wrote: > > > > > > > All, with Jim stepping down as mentor it looks like your community > > needs > > > > some additional mentors. I'm happy to help if you would like. > > > > > > > > Some background on me. I've been involved with various Apache big > data > > > > projects since 2007. I got started with Pig (when it was in the > > > > incubator), am currently active in the Hive community, and have > helped > > > > mentor many projects, including Flink, Ranger, and Bigtop. > > > > > > > > Alan. > > > > > > > > > > -- *Jeff Feng* Product Lead m: (949)-610-5108 twitter: @jtfeng
Re: Pre-apache convenience releases
Justin - thanks for the reminder on bringing back discussion from the bi-weekly meetings back to the mailing list. It is sincerely unintentional. I will start another thread and share those notes now. Best, Jeff On Sat, Dec 1, 2018 at 1:30 PM Justin Mclean wrote: > Hi, > > At the ASF projects release source code, a binary connivance release has > to match what is contained in that source release. [4][5] So you need to > make a source package that complies with ASF release policy [1][2][3] and > vote on that.Only then can you can then optionally release a binary package > based on that source release. (Most projects release both as once). > > I also note there has been zero discussion about this release on this > mailing list. Why is that? In fact there seems to be not much discussion > here at all? I also note that the biweekly(?) meetings are still occurring > but no information is being brought back to this list. > > Several months ago the podling was asked to correct the above issues. It > doesn't look like these issues are being addressed or being addressed q. I > expect the next report (due Dec 5th) will include steps this project will > take to correct this. I will also start a discussion at the IPMC to see if > a decision needs be taken on if this project should continue at the ASF or > not. > > Thanks, > Justin > > 1. http://www.apache.org/legal/release-policy.html > 2. https://www.apache.org/legal/resolved.html > 3. > https://incubator.apache.org/guides/releasemanagement.html#podling_constraints > 4. > http://www.apache.org/legal/release-policy.html#what-must-every-release-contain > 5. http://www.apache.org/legal/release-policy.html#compiled-packages > -- *Jeff Feng* Product Lead m: (949)-610-5108 twitter: @jtfeng
Re: Pre-apache convenience releases
Hi, At the ASF projects release source code, a binary connivance release has to match what is contained in that source release. [4][5] So you need to make a source package that complies with ASF release policy [1][2][3] and vote on that.Only then can you can then optionally release a binary package based on that source release. (Most projects release both as once). I also note there has been zero discussion about this release on this mailing list. Why is that? In fact there seems to be not much discussion here at all? I also note that the biweekly(?) meetings are still occurring but no information is being brought back to this list. Several months ago the podling was asked to correct the above issues. It doesn't look like these issues are being addressed or being addressed q. I expect the next report (due Dec 5th) will include steps this project will take to correct this. I will also start a discussion at the IPMC to see if a decision needs be taken on if this project should continue at the ASF or not. Thanks, Justin 1. http://www.apache.org/legal/release-policy.html 2. https://www.apache.org/legal/resolved.html 3. https://incubator.apache.org/guides/releasemanagement.html#podling_constraints 4. http://www.apache.org/legal/release-policy.html#what-must-every-release-contain 5. http://www.apache.org/legal/release-policy.html#compiled-packages
Re: Pre-apache convenience releases
cc-ing our mentors Ashutosh and Luke for visibility On Sat, Dec 1, 2018 at 12:41 PM Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > How should we go about the pre-Apache release process? We have `0.29.0rc5` > that would be ready for a vote. > > This would be a convenience release to PyPI.org. > > Max >
Pre-apache convenience releases
How should we go about the pre-Apache release process? We have `0.29.0rc5` that would be ready for a vote. This would be a convenience release to PyPI.org. Max
