Re: Is Livy podling still active?
We are using Livy in our production, is there any alternative for Livy ?? On Mon, 9 May 2022 at 3:44 AM, John D. Ament wrote: > Hi all > > Based on the discussions, it seems like we should start a formal retirement > vote. I will plan to start it within the next couple of days unless > someone else does. > > John > > On Tue, Apr 5, 2022 at 9:38 AM sebb wrote: > > > On Tue, 5 Apr 2022 at 13:27, Jean-Baptiste Onofré > wrote: > > > > > > Hi, > > > > > > AFAIR, a report has been submitted since. Report on cwiki doesn't mean > > > it's the last send, we should check in the incubator board report. > > > > > > It's true that Livy is a "stable" project and kind of "mature" > > > podling. IMHO, it should have graduated to TLP. > > > > Huh? > > That would require an active PMC, for which there is little evidence. > > > > > As said, I tried to restart podling activity, but I didn't get a lot > > > of updates: most people are Livy users but they don't seem to want to > > > become contributors. > > > > Nor does anyone seem to want to deal with issues. > > > > > Regards > > > JB > > > > > > On Tue, Apr 5, 2022 at 8:56 AM Javi Roman > wrote: > > > > > > > > Hi community! > > > > > > > > I see that the project is losing interest from the community, however > > it is > > > > a project widely used by companies (I know personally). It is a pity > > that > > > > the project may die. > > > > > > > > In my opinion one of the first actions to take is to recreate the > > reports > > > > correctly (Podling reports). I have seen that the last one sent was > in > > > > August last year [1]. > > > > > > > > Personally I would like to get involved in this project and help in > > > > restarting it. If you like, I could be in charge of the next report, > if > > > > there is no inconvenience. > > > > > > > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/August2021 > > > > > > > > > > > > On Mon, Apr 4, 2022 at 9:44 AM Jean-Baptiste Onofré > > > wrote: > > > > > > > > > Hi, > > > > > > > > > > You are right, I tried to bring Livy podling back to active. We had > > > > > few PRs/contributions and I also worked on reload4j switch and so > on. > > > > > > > > > > If the activity around the code is low, there are few. > Unfortunately, > > > > > the mailing list is pretty quiet. > > > > > > > > > > Regards > > > > > JB > > > > > > > > > > On Sun, Apr 3, 2022 at 11:46 PM Luciano Resende < > > luckbr1...@gmail.com> > > > > > wrote: > > > > > > > > > > > > There seem to have been a couple of initiatives to reboot the > > podling and > > > > > > make it healthy again but without much success. > > > > > > > > > > > > What are other mentors' thoughts? > > > > > > > > > > > > On Sun, Apr 3, 2022 at 12:59 PM sebb wrote: > > > > > > > > > > > > > There doesn't seem to be any recent activity on the mailing > > lists, and > > > > > > > no recent commits. > > > > > > > > > > > > > > Sebb > > > > > > > > > > > > > > > > - > > > > > > > To unsubscribe, e-mail: > general-unsubscr...@incubator.apache.org > > > > > > > For additional commands, e-mail: > > general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Luciano Resende > > > > > > http://twitter.com/lresende1975 > > > > > > http://lresende.blogspot.com/ > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- --Brahma Reddy Battula
Re: [VOTE] Release Apache EventMesh(Incubating) 1.5.0-rc0
Hi Justin, Thanks for your check, vote, and suggestion, the build error may due to an incompatible version of gradle, the gradle version may need to be higher than 7. And I will add the build step to README soon, and modify the download way in EventMesh doc to use ASF release rather than github. Thanks, Wenjun On Wed, Jun 29, 2022 at 1:31 PM Justin Mclean wrote: > > Hi, > > +1 (binding) if it can be built from the source release. > > I checked: > - incubating in name > - signatures and hashes are fine > - disclaimer exists (WIP) > - LICENSE and NOTICE seem fine > - no unexpected binary files > - ASF files have ASF headers > - Was unable to compile from source > > Can someone confirm you can build this from the source release? I’m getting > an error in the gradle build file, but it may just be my setup. > > Error is: > Could not compile build file > '/Users/justinmclean/ApacheEventMesh/apache-eventmesh-1.5.0-incubating-src/build.gradle'. > > startup failed: > build file > '/Users/justinmclean/ApacheEventMesh/apache-eventmesh-1.5.0-incubating-src/build.gradle': > 116: unexpected token: ) @ line 116, column 105. > dist/lib").list()).orElseGet(() -> new S > > It would also be nice to include instructions on how to build in the README. > On the page here [1] it states "Download and extract the source code of the > latest release from GitHub releases.”. Please do not recommend this, please > recommend instead that people use the offical ASF releases. > > Kind Regards, > Justin > > 1. > https://github.com/apache/incubator-eventmesh/blob/master/docs/en/installation/01-runtime.md > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Is Livy podling still active?
Apache Kyuubi (Incubating)[1] is an option, it's a distributed and multi-tenant gateway to provide serverless SQL on lakehouses. [1] https://kyuubi.apache.org/ Thanks, Cheng Pan On Wed, Jun 29, 2022 at 5:21 PM Brahma Reddy Battula wrote: > > We are using Livy in our production, is there any alternative for Livy ?? > > On Mon, 9 May 2022 at 3:44 AM, John D. Ament wrote: > > > Hi all > > > > Based on the discussions, it seems like we should start a formal retirement > > vote. I will plan to start it within the next couple of days unless > > someone else does. > > > > John > > > > On Tue, Apr 5, 2022 at 9:38 AM sebb wrote: > > > > > On Tue, 5 Apr 2022 at 13:27, Jean-Baptiste Onofré > > wrote: > > > > > > > > Hi, > > > > > > > > AFAIR, a report has been submitted since. Report on cwiki doesn't mean > > > > it's the last send, we should check in the incubator board report. > > > > > > > > It's true that Livy is a "stable" project and kind of "mature" > > > > podling. IMHO, it should have graduated to TLP. > > > > > > Huh? > > > That would require an active PMC, for which there is little evidence. > > > > > > > As said, I tried to restart podling activity, but I didn't get a lot > > > > of updates: most people are Livy users but they don't seem to want to > > > > become contributors. > > > > > > Nor does anyone seem to want to deal with issues. > > > > > > > Regards > > > > JB > > > > > > > > On Tue, Apr 5, 2022 at 8:56 AM Javi Roman > > wrote: > > > > > > > > > > Hi community! > > > > > > > > > > I see that the project is losing interest from the community, however > > > it is > > > > > a project widely used by companies (I know personally). It is a pity > > > that > > > > > the project may die. > > > > > > > > > > In my opinion one of the first actions to take is to recreate the > > > reports > > > > > correctly (Podling reports). I have seen that the last one sent was > > in > > > > > August last year [1]. > > > > > > > > > > Personally I would like to get involved in this project and help in > > > > > restarting it. If you like, I could be in charge of the next report, > > if > > > > > there is no inconvenience. > > > > > > > > > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/August2021 > > > > > > > > > > > > > > > On Mon, Apr 4, 2022 at 9:44 AM Jean-Baptiste Onofré > > > > > wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > You are right, I tried to bring Livy podling back to active. We had > > > > > > few PRs/contributions and I also worked on reload4j switch and so > > on. > > > > > > > > > > > > If the activity around the code is low, there are few. > > Unfortunately, > > > > > > the mailing list is pretty quiet. > > > > > > > > > > > > Regards > > > > > > JB > > > > > > > > > > > > On Sun, Apr 3, 2022 at 11:46 PM Luciano Resende < > > > luckbr1...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > There seem to have been a couple of initiatives to reboot the > > > podling and > > > > > > > make it healthy again but without much success. > > > > > > > > > > > > > > What are other mentors' thoughts? > > > > > > > > > > > > > > On Sun, Apr 3, 2022 at 12:59 PM sebb wrote: > > > > > > > > > > > > > > > There doesn't seem to be any recent activity on the mailing > > > lists, and > > > > > > > > no recent commits. > > > > > > > > > > > > > > > > Sebb > > > > > > > > > > > > > > > > > > > - > > > > > > > > To unsubscribe, e-mail: > > general-unsubscr...@incubator.apache.org > > > > > > > > For additional commands, e-mail: > > > general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Luciano Resende > > > > > > > http://twitter.com/lresende1975 > > > > > > > http://lresende.blogspot.com/ > > > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > -- > > > > --Brahma Reddy Battula - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Queuing solution for merging patches
Hi, There're several solutions around GitHub ecosystem to queuing patches passed reviews and waiting for merged, especially in case to avoid semantic conflict; e.g., Mergify or Bors-NG. After enabled branch must be up-to-date with main branch, it introduces an issue that multiple patches can race each other and cause unnecessary CI tasks rerun - two patches can be verified simultaneously, after one merged, the other should rerun, which generally cause O(n^2) task instance while with queuing only O(n) is required. Given that there're existing solutions, I'd like to ask what the best practice for Apache projects host developments on GitHub on this topic. Or what support does INFRA provide for the certain case. Best, tison.
Re: Queuing solution for merging patches
Hi Tison I think there is no hard requirement from infra or Apache perspective. The PMC could decide what they like, and ask Infra team to set them up. tison 于2022年6月29日 周三19:25写道： > Hi, > > There're several solutions around GitHub ecosystem to queuing patches > passed reviews and waiting for merged, especially in case to avoid semantic > conflict; e.g., Mergify or Bors-NG. > > After enabled branch must be up-to-date with main branch, it introduces an > issue that multiple patches can race each other and cause unnecessary CI > tasks rerun - two patches can be verified simultaneously, after one merged, > the other should rerun, which generally cause O(n^2) task instance while > with queuing only O(n) is required. > > Given that there're existing solutions, I'd like to ask what the best > practice for Apache projects host developments on GitHub on this topic. Or > what support does INFRA provide for the certain case. > > Best, > tison. > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: Short process intro for exec's?
>> What does "releases are a sacred ritual" mean? That there's a fixed process that must be followed? >Basically yes, the PPMC and IPMC check and vote on releases as described here [1]. Thanks.
Re: Queuing solution for merging patches
Hi Sheng, Yes. I do _not_ ask INFRA to support it, but to see if there is existing practice. Best, tison. Sheng Wu 于2022年6月29日周三 19:33写道： > Hi Tison > > I think there is no hard requirement from infra or Apache perspective. The > PMC could decide what they like, and ask Infra team to set them up. > > tison 于2022年6月29日 周三19:25写道： > > > Hi, > > > > There're several solutions around GitHub ecosystem to queuing patches > > passed reviews and waiting for merged, especially in case to avoid > semantic > > conflict; e.g., Mergify or Bors-NG. > > > > After enabled branch must be up-to-date with main branch, it introduces > an > > issue that multiple patches can race each other and cause unnecessary CI > > tasks rerun - two patches can be verified simultaneously, after one > merged, > > the other should rerun, which generally cause O(n^2) task instance while > > with queuing only O(n) is required. > > > > Given that there're existing solutions, I'd like to ask what the best > > practice for Apache projects host developments on GitHub on this topic. > Or > > what support does INFRA provide for the certain case. > > > > Best, > > tison. > > > -- > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 >
Re: Queuing solution for merging patches
Hi Tison, I asked a couple of months ago [1] if Infra could enable Github's Merge Queue Functionality [2]. That was rejected unfortunately. I'm also curious if others think of a solution that would be compliant with the ASF rules. Best regards, Martijn [1] https://issues.apache.org/jira/browse/INFRA-22804 [2] https://github.blog/changelog/2021-10-27-pull-request-merge-queue-limited-beta/ Op wo 29 jun. 2022 om 13:53 schreef Sheng Wu : > Hi > > I think the key is you set up to date for main branch, which makes CI has > to rerun. > > tison 于2022年6月29日 周三19:39写道： > >> Hi Sheng, >> >> Yes. I do _not_ ask INFRA to support it, but to see if there is existing >> practice. >> >> Best, >> tison. >> >> >> Sheng Wu 于2022年6月29日周三 19:33写道： >> >> > Hi Tison >> > >> > I think there is no hard requirement from infra or Apache perspective. >> The >> > PMC could decide what they like, and ask Infra team to set them up. >> > >> > tison 于2022年6月29日 周三19:25写道： >> > >> > > Hi, >> > > >> > > There're several solutions around GitHub ecosystem to queuing patches >> > > passed reviews and waiting for merged, especially in case to avoid >> > semantic >> > > conflict; e.g., Mergify or Bors-NG. >> > > >> > > After enabled branch must be up-to-date with main branch, it >> introduces >> > an >> > > issue that multiple patches can race each other and cause unnecessary >> CI >> > > tasks rerun - two patches can be verified simultaneously, after one >> > merged, >> > > the other should rerun, which generally cause O(n^2) task instance >> while >> > > with queuing only O(n) is required. >> > > >> > > Given that there're existing solutions, I'd like to ask what the best >> > > practice for Apache projects host developments on GitHub on this >> topic. >> > Or >> > > what support does INFRA provide for the certain case. >> > > >> > > Best, >> > > tison. >> > > >> > -- >> > Sheng Wu 吴晟 >> > >> > Apache SkyWalking >> > Apache Incubator >> > Apache ShardingSphere, ECharts, DolphinScheduler podlings >> > Zipkin >> > Twitter, wusheng1108 >> > >> > -- > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 >
Re: Queuing solution for merging patches
Hi I think the key is you set up to date for main branch, which makes CI has to rerun. tison 于2022年6月29日 周三19:39写道： > Hi Sheng, > > Yes. I do _not_ ask INFRA to support it, but to see if there is existing > practice. > > Best, > tison. > > > Sheng Wu 于2022年6月29日周三 19:33写道： > > > Hi Tison > > > > I think there is no hard requirement from infra or Apache perspective. > The > > PMC could decide what they like, and ask Infra team to set them up. > > > > tison 于2022年6月29日 周三19:25写道： > > > > > Hi, > > > > > > There're several solutions around GitHub ecosystem to queuing patches > > > passed reviews and waiting for merged, especially in case to avoid > > semantic > > > conflict; e.g., Mergify or Bors-NG. > > > > > > After enabled branch must be up-to-date with main branch, it introduces > > an > > > issue that multiple patches can race each other and cause unnecessary > CI > > > tasks rerun - two patches can be verified simultaneously, after one > > merged, > > > the other should rerun, which generally cause O(n^2) task instance > while > > > with queuing only O(n) is required. > > > > > > Given that there're existing solutions, I'd like to ask what the best > > > practice for Apache projects host developments on GitHub on this topic. > > Or > > > what support does INFRA provide for the certain case. > > > > > > Best, > > > tison. > > > > > -- > > Sheng Wu 吴晟 > > > > Apache SkyWalking > > Apache Incubator > > Apache ShardingSphere, ECharts, DolphinScheduler podlings > > Zipkin > > Twitter, wusheng1108 > > > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
Re: [VOTE] Release Apache Linkis(Incubating) 1.1.2-RC2
The RC2 version mainly resolve the problems about some web JS file license in RC1[1]. About gpg key,I have tried to modify the description about "test key for apache" for the gpg key but it didn't work 1. https://lists.apache.org/thread/91y4wncdrct8m34mozz3246hv29w4hyl On 2022/06/29 15:16:28 seayi wrote: > Hello Incubator Community, > > The Apache Linkis community has voted and approved the release of Apache > Linkis(incubating) 1.1.2-RC2. We now kindly request IPMC members and the > incubator community to help review and vote for this release. > > Apache Linkis builds a computation middleware layer to decouple the upper > applications and the underlying data engines, provides standardized > interfaces (REST, JDBC, WebSocket etc.) to easily connect to various > underlying engines (Spark, Presto, Flink, etc.), while enables cross engine > context sharing, unified job& engine governance and orchestration. > > Linkis community vote thread: > • https://lists.apache.org/thread/llcy6fbbh2z2yjt21gmo0bz5htjkwobt > > Vote result thread: > • https://lists.apache.org/thread/t9y1o82x47905l84jzg26l8rzrvm9bwo > > The release candidate: > • https://dist.apache.org/repos/dist/dev/incubator/linkis/1.1.2-RC2/ > > Git tag for the release: > • > https://github.com/apache/incubator-linkis/releases/tag/release-1.1.2-rc2 > > Release notes: > • https://linkis.apache.org/docs/1.1.2/release-notes-1.1.2 > > The artifacts signed with PGP key [seayi], corresponding to [ > se...@apache.org], that can be found in keys file: > • https://downloads.apache.org/incubator/linkis/KEYS > > The vote will be open for at least 72 hours or until necessary number > of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > More detail checklist please refer: > • > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > Steps to validate the release，Please refer to: > • https://linkis.apache.org/community/how-to-verify > > Thanks, > On behalf of Apache Linkis(Incubating) community > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Linkis(Incubating) 1.1.2-RC2
Hello Incubator Community, The Apache Linkis community has voted and approved the release of Apache Linkis(incubating) 1.1.2-RC2. We now kindly request IPMC members and the incubator community to help review and vote for this release. Apache Linkis builds a computation middleware layer to decouple the upper applications and the underlying data engines, provides standardized interfaces (REST, JDBC, WebSocket etc.) to easily connect to various underlying engines (Spark, Presto, Flink, etc.), while enables cross engine context sharing, unified job& engine governance and orchestration. Linkis community vote thread: • https://lists.apache.org/thread/llcy6fbbh2z2yjt21gmo0bz5htjkwobt Vote result thread: • https://lists.apache.org/thread/t9y1o82x47905l84jzg26l8rzrvm9bwo The release candidate: • https://dist.apache.org/repos/dist/dev/incubator/linkis/1.1.2-RC2/ Git tag for the release: • https://github.com/apache/incubator-linkis/releases/tag/release-1.1.2-rc2 Release notes: • https://linkis.apache.org/docs/1.1.2/release-notes-1.1.2 The artifacts signed with PGP key [seayi], corresponding to [ se...@apache.org], that can be found in keys file: • https://downloads.apache.org/incubator/linkis/KEYS The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason More detail checklist please refer: • https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist Steps to validate the release，Please refer to: • https://linkis.apache.org/community/how-to-verify Thanks, On behalf of Apache Linkis(Incubating) community
Re: [VOTE] Release Apache EventMesh(Incubating) 1.5.0-rc0
Hi Paul, Thanks for your check and vote. Welcome to submit PR. The copyright notice has been incorrect modified by this commit, I will fix this. Yes, we need to add a step to remove the wrapper-related file in our build file. Thanks, Wenjun On Wed, Jun 29, 2022 at 10:57 PM Paul King wrote: > > Yes, the build file is using (just a little) Groovy 3 syntax (new in > Gradle 7). You could revert to older style syntax but it would > probably be better to have a bootstrap step that downloaded the gradle > wrapper and then use the wrapper in all of your instructions. The > Groovy build has such a setup. Let me know if you need a PR (for the > English instructions anyway). You could then use older Gradle versions > to bootstrap and then gradlew from then on. It would be considered > better practice in terms of reproducible builds. > > I noticed also that you seem to have "gradlew.bat" in your source zip. > Is that an oversight? I couldn't see where you removed other gradle > wrapper-related artifacts in your build file - though there doesn't > seem to be any others which is usual practice currently. > > Also, it seems this commit splattered over the copyright notice lines > from the gradle supplied gradlew/gradlew.bat files in the main source > repo: > https://github.com/apache/incubator-eventmesh/commit/032bb0d8b09 > I didn't check if any other files are splattered in the same way in > other commits but it might be worthwhile to do a bit of an audit. > > +1 (binding) but only because of the WIP disclaimer (because of the > issue mentioned above) > > I checked: > - incubating in name > - signatures and hashes okay > - disclaimer exists (WIP) > - LICENSE and NOTICE seem okay > - no unexpected binary files (but I suspect gradlew.bat is an oversight) > - headers seem okay apart from gradlew.bat which shouldn't be there I suspect. > > > Cheers, Paul. > > > On Wed, Jun 29, 2022 at 7:35 PM wenjun wrote: > > > > Hi Justin, > > > > Thanks for your check, vote, and suggestion, the build error may due > > to an incompatible version of gradle, the gradle version may need to > > be higher than 7. > > > > And I will add the build step to README soon, and modify the download > > way in EventMesh doc to use ASF release rather than github. > > > > > > Thanks, > > Wenjun > > > > On Wed, Jun 29, 2022 at 1:31 PM Justin Mclean > > wrote: > > > > > > Hi, > > > > > > +1 (binding) if it can be built from the source release. > > > > > > I checked: > > > - incubating in name > > > - signatures and hashes are fine > > > - disclaimer exists (WIP) > > > - LICENSE and NOTICE seem fine > > > - no unexpected binary files > > > - ASF files have ASF headers > > > - Was unable to compile from source > > > > > > Can someone confirm you can build this from the source release? I’m > > > getting an error in the gradle build file, but it may just be my setup. > > > > > > Error is: > > > Could not compile build file > > > '/Users/justinmclean/ApacheEventMesh/apache-eventmesh-1.5.0-incubating-src/build.gradle'. > > > > startup failed: > > > build file > > > '/Users/justinmclean/ApacheEventMesh/apache-eventmesh-1.5.0-incubating-src/build.gradle': > > > 116: unexpected token: ) @ line 116, column 105. > > > dist/lib").list()).orElseGet(() -> new S > > > > > > It would also be nice to include instructions on how to build in the > > > README. On the page here [1] it states "Download and extract the source > > > code of the latest release from GitHub releases.”. Please do not > > > recommend this, please recommend instead that people use the offical ASF > > > releases. > > > > > > Kind Regards, > > > Justin > > > > > > 1. > > > https://github.com/apache/incubator-eventmesh/blob/master/docs/en/installation/01-runtime.md > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache EventMesh(Incubating) 1.5.0-rc0
Yes, the build file is using (just a little) Groovy 3 syntax (new in Gradle 7). You could revert to older style syntax but it would probably be better to have a bootstrap step that downloaded the gradle wrapper and then use the wrapper in all of your instructions. The Groovy build has such a setup. Let me know if you need a PR (for the English instructions anyway). You could then use older Gradle versions to bootstrap and then gradlew from then on. It would be considered better practice in terms of reproducible builds. I noticed also that you seem to have "gradlew.bat" in your source zip. Is that an oversight? I couldn't see where you removed other gradle wrapper-related artifacts in your build file - though there doesn't seem to be any others which is usual practice currently. Also, it seems this commit splattered over the copyright notice lines from the gradle supplied gradlew/gradlew.bat files in the main source repo: https://github.com/apache/incubator-eventmesh/commit/032bb0d8b09 I didn't check if any other files are splattered in the same way in other commits but it might be worthwhile to do a bit of an audit. +1 (binding) but only because of the WIP disclaimer (because of the issue mentioned above) I checked: - incubating in name - signatures and hashes okay - disclaimer exists (WIP) - LICENSE and NOTICE seem okay - no unexpected binary files (but I suspect gradlew.bat is an oversight) - headers seem okay apart from gradlew.bat which shouldn't be there I suspect. Cheers, Paul. On Wed, Jun 29, 2022 at 7:35 PM wenjun wrote: > > Hi Justin, > > Thanks for your check, vote, and suggestion, the build error may due > to an incompatible version of gradle, the gradle version may need to > be higher than 7. > > And I will add the build step to README soon, and modify the download > way in EventMesh doc to use ASF release rather than github. > > > Thanks, > Wenjun > > On Wed, Jun 29, 2022 at 1:31 PM Justin Mclean > wrote: > > > > Hi, > > > > +1 (binding) if it can be built from the source release. > > > > I checked: > > - incubating in name > > - signatures and hashes are fine > > - disclaimer exists (WIP) > > - LICENSE and NOTICE seem fine > > - no unexpected binary files > > - ASF files have ASF headers > > - Was unable to compile from source > > > > Can someone confirm you can build this from the source release? I’m getting > > an error in the gradle build file, but it may just be my setup. > > > > Error is: > > Could not compile build file > > '/Users/justinmclean/ApacheEventMesh/apache-eventmesh-1.5.0-incubating-src/build.gradle'. > > > startup failed: > > build file > > '/Users/justinmclean/ApacheEventMesh/apache-eventmesh-1.5.0-incubating-src/build.gradle': > > 116: unexpected token: ) @ line 116, column 105. > > dist/lib").list()).orElseGet(() -> new S > > > > It would also be nice to include instructions on how to build in the > > README. On the page here [1] it states "Download and extract the source > > code of the latest release from GitHub releases.”. Please do not recommend > > this, please recommend instead that people use the offical ASF releases. > > > > Kind Regards, > > Justin > > > > 1. > > https://github.com/apache/incubator-eventmesh/blob/master/docs/en/installation/01-runtime.md > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Linkis(Incubating) 1.1.2-RC2
Hi, +1 (binding) I checked: - incubating in name - signatures and hashes are fine - LICENSE and NOTICE are fine - No unexpected binary files - ASF headers where needed - Can compile from source In the readme it sates: "Please go to the [Linkis Releases Page](https://github.com/apache/incubator- /releases) to download a compiled distribution or a source code package of Linkis.” Please do not point users to guthub as a primary way to obtain releases, please point them to the ASF official release area. It also a good idea to tell people how they can verify releases. It would also be best if the full instructions on how to compile were included in the README. Instructions at a URL may change over time and may not work for previous versions of the software. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[Branding Issue] Shenyu is still decleared as a project of dromara community
Hi Shenyu and incubator Shenyu is going to graduate in next month, I accidentally have a chance to review its original org, Dromara, due to some reviews for SkyWalking PR. There are two things concerning me. 1. Dromara website[1] still declare Shenyu(even with Apache prefix) on its project page. I think this is wrong and confusing end-users. As this project has been donated for a long time, why it is still hosted there? 2. Hutool project[2], another project hosted in dromara community, its website declares very clearly Shenyu is a project of Dromara community. 3. Sa-token project[3], Dromara community project. It posts Shenyu's logo as well without Apache prefix, and it links the project to gitee[4], which is mostly an official mirror of Shenyu. Could Shenyu's PMC take care of this? make sure that, Dromara is not a big open-source community, and several people in Shenyu PMC team actually leads this community as far as I know. 1. From Dromara community perspective, it would keep declaring things like this. Shenyu has been donated to the foundation. 2. All links, especially those you could control in the Dromara community's project, should go to the Apache website, or Apache's GitHub repository very clearly. For members of the PMC team, I hope Shenyu's PMC could take more responsibilities to protect the ASF and project branding. This should not be hard to find, as you are working inside Dromara community. Unless you didn't know this is a branding, this would concern me more, as you are going to graduate a TLP. [1] https://dromara.org/projects/ [2] https://www.hutool.cn/ [3] https://sa-token.dev33.cn/ [4] https://gitee.com/Apache-ShenYu/incubator-shenyu Sheng Wu 吴晟 Twitter, wusheng1108 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache EventMesh(Incubating) 1.5.0-rc0
Hi, > Thanks for your check, vote, and suggestion, the build error may due > to an incompatible version of gradle, the gradle version may need to > be higher than 7. Yes that is the case I have 6.8.1 installed. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Branding Issue] Shenyu is still decleared as a project of dromara community
Hi Sheng, Thank you very much for the reminder, I will notify dromara, hutool, sa-token and clean up the links about Apache ShenYu. Sheng Wu 于2022年6月30日周四 08:38写道： > > Hi Shenyu and incubator > > Shenyu is going to graduate in next month, I accidentally have a > chance to review its original org, Dromara, due to some reviews for > SkyWalking PR. > > There are two things concerning me. > 1. Dromara website[1] still declare Shenyu(even with Apache prefix) on > its project page. I think this is wrong and confusing end-users. As > this project has been donated for a long time, why it is still hosted > there? > 2. Hutool project[2], another project hosted in dromara community, its > website declares very clearly Shenyu is a project of Dromara > community. > 3. Sa-token project[3], Dromara community project. It posts Shenyu's > logo as well without Apache prefix, and it links the project to > gitee[4], which is mostly an official mirror of Shenyu. > > Could Shenyu's PMC take care of this? make sure that, Dromara is not a > big open-source community, and several people in Shenyu PMC team > actually leads this community as far as I know. > 1. From Dromara community perspective, it would keep declaring things > like this. Shenyu has been donated to the foundation. > 2. All links, especially those you could control in the Dromara > community's project, should go to the Apache website, or Apache's > GitHub repository very clearly. > > For members of the PMC team, I hope Shenyu's PMC could take more > responsibilities to protect the ASF and project branding. This should > not be hard to find, as you are working inside Dromara community. > Unless you didn't know this is a branding, this would concern me more, > as you are going to graduate a TLP. > > > [1] https://dromara.org/projects/ > [2] https://www.hutool.cn/ > [3] https://sa-token.dev33.cn/ > [4] https://gitee.com/Apache-ShenYu/incubator-shenyu > > Sheng Wu 吴晟 > Twitter, wusheng1108 -- -- Best wishes! Yu Xiao Apache ShenYu (Incubating) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Branding Issue] Shenyu is still decleared as a project of dromara community
Hi, ShenYu PPMCs have good communication with the dromara community. Dromara Community Team clean up about Apache ShenYu links in dromara website[1]. Hutool Team clean up about Apache ShenYu links in hutool website[2]. Sa-Token Team clean up about Apache ShenYu links in sa-Token website[3]. Finally, ShenYu PPMCs checked all the official websites of the projects under the dromara community, no other links found for Apache ShenYu（Or have been cleaned). [1] https://dromara.org/projects/ [2] https://www.hutool.cn/ [3] https://sa-token.dev33.cn/ -- Best wishes! Yu Xiao Apache ShenYu (Incubating) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
