[ANNOUNCE] Release Apache DolphinScheduler (Incubating) 1.3.1

Hi all, We are glad to announce the release of Apache DolphinScheduler(incubating) 1.3.1. Once again I would like to express my thanks to your help. Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow scheduling system, dedicated to solving the complex dependencies in data

Re: [VOTE] Distribution guidelines for platforms

> So what would you suggest as an alternative? As I've been consistently suggesting in the discussion thread and in this thread, I hope that ASF could move forward together on the distribution guidelines, and the consensus should bind all projects, TLP and podlings alike. Taking the shortcut

Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.3.1 (ROUND2)

Hi, > The first minor issue of the following I didn't understand clearly, whether > the notice file means both the binary notice file and source notice file. I just looked at the source release. > Yes,I copied all of the mybatis NOTICE file and put it into our binary notice > file and source

Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.3.1 (ROUND2)

Thanks,I will remove the OGNL in the source notice next release. I checkd over the soure notice file. And I think the license information that you said and suggest to remove is that the following [1]. 1.The license information need to removed out from the source notice Licensed under the

Re: [VOTE] Distribution guidelines for platforms

> Put it this way without that guidance some podlings will come to graduation, > and it will not be granted as they are not complying with ASF policy. Or we > have the situation when the board points out to the Incubator that a podling > is not following ASF policy. Or podlings may leave the

Re: [ANNOUNCE] Release Apache DolphinScheduler (Incubating) 1.3.1

good news Best Regards --- DolphinScheduler(Incubator) PPMC Lidong Dai 代立冬 dailidon...@gmail.com --- Furkan KAMACI 于2020年7月13日周一 下午6:31写道： > Hi, > > Congrats for the release! > > Kind Regards, > Furkan KAMACI > > On Mon, Jul 13, 2020 at 1:27 PM leon bao wrote: > > >

Re: [VOTE] Distribution guidelines for platforms

Hi, How is providing guidance on ASF policy to podlings unfair if it makes their life easier? Again these guidelines add nothing that a TLP shouldn’t already be doing. They may do it in a slightly different way, and that’s OK and also allowed by these guidelines. Put it this way without that

[RESULT][VOTE] Release Apache DolphinScheduler (Incubating) 1.3.1 (ROUND2)

Hi All, Release vote for Release Apache DolphinScheduler (Incubating) 1.3.1(ROUND2) has PASSED and closed now. The results are as follows: [3] +1 Binded votes - Furkan KAMACI - Kevin Ratnasekera - Justin Mclean [ 0 ] +0 Binded Votes [ 0 ] -1 Binded Votes The vote is successful. Thanks for

Re: [DISCUSS] project proposal - Apache Sedona

Hello Dave, Thank you for the great question! We actually have tried our best to reach out to the existing code contributors to ask for their support. To be specific, we did the following two things: 1. We created a GitHub issue on GeoSpark repo to explain this donation in October 2019. Please

Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.3.1 (ROUND2)

Thanks for your suggest and guidence. In order to keep the notice file as brief and simple as possible in our next release, I have the following questions to verify and wish your response. The first minor issue of the following I didn't understand clearly,whether the notice file means both the

Re: [ANNOUNCE] Release Apache DolphinScheduler (Incubating) 1.3.1

Hi, Congrats for the release! Kind Regards, Furkan KAMACI On Mon, Jul 13, 2020 at 1:27 PM leon bao wrote: > Hi all, > > We are glad to announce the release of Apache DolphinScheduler(incubating) > 1.3.1. Once again I would like to express my thanks to your help. > > Dolphin Scheduler is a

Re: [VOTE] Distribution guidelines for platforms

Hi, > I think all of these situations can occur with or without the new incubator > policy. It possibles yes, but they would be less likely to occur. > his can only be more restrictive than the original ASF policies. These are not more restrictive than current policy. I really don’t

Re: [VOTE] Distribution guidelines for platforms

My reading of the wording is that there is now more wiggle room for podlings rather than more restrictions. Cheers, Paul. On Mon, Jul 13, 2020 at 5:51 PM Justin Mclean wrote: > Hi, > > > I think all of these situations can occur with or without the new > incubator policy. > > It possibles yes,

Re: [VOTE] Release Apache Daffodil (incubating) 2.7.0-rc2

HI, > Hoping we can get someone else to review soon. Your mentors should be voting on your releases as they are IPMC members. If they are not please remind them to do so. If your mentors are absent then please ask for someone to replace them. Thanks Justin

Re?? [ANNOUNCE] Release Apache DolphinScheduler (Incubating) 1.3.1

Hi, Congrats for the release! Best, Yichao Yang ---- ??: "dev"

Fw: [VOTE] Release Apache Daffodil (incubating) 2.7.0-rc2

We need one more +1 review to proceed. Hoping we can get someone else to review soon. We have a user community that requested that we do this point-release with a specific fix. This is gating their release of a system that uses Daffodil. Please review this latest incubator release of Daffodil.

Re: [VOTE] Release Apache Daffodil (incubating) 2.7.0-rc2

Mentors are volunteers. Daffodil has only two mentors. For a long time it was a single mentor. Anyone interested in mentoring Daffodil? The only issue preventing graduation is lack of diversity. Regards, Dave Sent from my iPhone > On Jul 13, 2020, at 7:25 AM, Justin Mclean wrote: > > HI,

Re: [RELEASENOTES?] Re: [VOTE] Release Apache Daffodil (incubating) 2.7.0-rc2

Hi Dave, they are not a requirement ... it's just that every project I'm on sort of has them and I think it's a good thing to have them. I didn't vote -1 or so ... I just added a comment as a minor issue (in my opinion) Chris Am 13.07.20, 16:53 schrieb "Dave Fisher" : > On Jul 10,

[RELEASENOTES?] Re: [VOTE] Release Apache Daffodil (incubating) 2.7.0-rc2

> On Jul 10, 2020, at 12:43 AM, Christofer Dutz > wrote: > > +1 (binding) > > I did find some minor issues though, please see below. > I would really suggest to start maintaining a RELEASE_NOTES file. I usually > have a look at this in order to see what to expect of the new release. > >

Re: [VOTE] Release Apache Daffodil (incubating) 2.7.0-rc2

Hi all, The vote to release Apache Daffodil (incubating) 2.7.0-rc2 is now closed. Thanks to those that took the time to review and vote. The release has passed with 3 +1 (binding) votes and no 0 or -1 votes. Binding: [List of +1 Voters] Christofer Dutz Justin Mclean Dave Fisher Vote threads:

Re: [VOTE] Release Apache Daffodil (incubating) 2.7.0-rc2

+1 (binding) NOTICE, LICENSE and DISCLAIMER are good. Checksums and signatures are good. Incubating in name. 3 of the 4 binary artifacts are equivalent aside from shell script in rpm. Did not unpack the msi so can’t vouch for that content. (I don’t have windows) sbt ratCheck is good. Compiles and

Re: [DISCUSS] project proposal - Apache Sedona

Thanks for your explanation. Thanks, Ming Wen, Apache APISIX(incubating) & Apache SkyWalking Twitter: _WenMing Jia Yu 于2020年7月14日周二 上午11:01写道： > Hello Ming Wen, > > Thanks for the question! > > Harry Zhu is the contributor of Sedona R binding. His code is a submodule > of the main repo >

Re: [DISCUSS] project proposal - Apache Sedona

Hi, Currently PiPy is not an ASF supported platform and you may have some difficulty in complying with ASF policies. Are you aware of the trademark, branding and other ASF policies that apply here? Also are you are aware that the ASF release process involve the PPMC and IPMC voting on release

Re: [DISCUSS] project proposal - Apache Sedona

Noted below. I will leave others to add anything I’ve missed. On Mon, Jul 13, 2020 at 8:15 PM Justin Mclean wrote: > Hi, > > Currently PiPy is not an ASF supported platform and you may have some > difficulty in complying with ASF policies. Are you aware of the trademark, > branding and other

[VOTE] Release Apache APISIX (Incubating) 1.4.1-RC1

Hello everyone, This is a call for the vote to release Apache APISIX (Incubating) version 1.4.1. The Apache APISIX community has voted on and approved a proposal to release Apache APISIX (Incubating) version 1.4.1. We now kindly request the Incubator IPMC members review and vote on this

Re: [DISCUSS] project proposal - Apache Sedona

Thank you Jia. Any other question on this? On Sun, Jul 12, 2020 at 8:06 PM Jia Yu wrote: > Hello Dave, > > Thank you for the great question! > > We actually have tried our best to reach out to the existing code > contributors to ask for their support. To be specific, we did the following > two

Re: [DISCUSS] project proposal - Apache Sedona

> The initial committers are contributors who made significant contributions to Apache Sedona based on the GitHub statistics: https://github.com/DataSystemsLab/GeoSpark/graphs/contributors hello, Jia Yu, I have a question. I saw that in the initial commiiters, Harry Zhu (7harryprince AT

Re: [DISCUSS] project proposal - Apache Sedona

Thank you, Justin and Felix. In addition to the comments from Felix, I am adding a few points: 1. We have noticed that the release process will go through voting, which may take some time. We have no problem with that. We believe that experiencing these is vital to Sedona and our community will

Re: [DISCUSS] project proposal - Apache Sedona

Hello Ming Wen, Thanks for the question! Harry Zhu is the contributor of Sedona R binding. His code is a submodule of the main repo https://github.com/DataSystemsLab/GeoSpark/tree/master/contrib, and thus was not counted towards the main statistics. The main repo of GeoSpark R is here

Re: [VOTE] Distribution guidelines for platforms

Hi, > Again, in my opinion, the act of interpretation of existing rules in a new > context is making new rules. Thus, all the rules in the guidelines are new > rules. If you see it that way , then every single project (both projects in the incubator and TLPs) makes new rules when they