Re: [VOTE] Release Apache EventMesh (incubating) 1.3.0 rc0
+1 (non-binding) from me, I have checked the following items: - Incubating in name - LICENSE and NOTICE are fine - DISCLAIMER-WIP exists - All links are valid - The PGP key file has the correct download link - Checksums and PGP signatures are valid. Xun Liu 于2021年12月25日周六 14:03写道： > Hi Folks, > > +1 (binding) from me, > > I have checked the following items: > - Incubating in name > - LICENSE and NOTICE are fine > - DISCLAIMER-WIP exists > - All links are valid > - No unexpected binary files > - All ASF files have ASF headers > - The PGP key file has the correct download link > - Checksums and PGP signatures are valid. > > In addition, > it seems that the EventMesh website[1] of our project is missing 2 links > [2][3]. > It would be even better if it could be made up next time. :-) > > [1]https://eventmesh.apache.org/ > [2]https://www.apache.org/security/ > [3]https://www.apache.org/events/ > > Best regards, > Xun Liu > > On Thu, Dec 23, 2021 at 4:45 PM mikexue wrote: > > > Hello Incubator Community, > > > > This is a call for a vote to release Apache EventMesh(Incubating) > > version 1.3.0 rc0 > > > > The Apache EventMesh community has voted on and approved a proposal to > > release Apache EventMesh(Incubating) version 1.3.0 rc0 > > > > We now kindly request the Incubator PMC members review and vote on > > this incubator release. > > > > EventMesh community vote thread: > > • https://lists.apache.org/thread/wolw8dvoxw1z53jc7cj52fj5vn8lt1m0 > > > > Vote result thread: > > • https://lists.apache.org/thread/xkkq19onk7lrrlboqybjsvxhgtdvn11c > > > > The release candidate: > > • > > https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.3.0-rc0/ > > > > Git tag for the release: > > • https://github.com/apache/incubator-eventmesh/tree/v1.3.0-rc0 > > > > Release notes: > > • https://eventmesh.apache.org/events/release-notes/v1.3.0 > > > > The artifacts signed with PGP key > > F84A0041D70B37AF9C7BF0B339F429D7579C25F5, corresponding to > > mike...@apache.org, that can be found in keys file: > > • https://downloads.apache.org/incubator/eventmesh/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 > > > > Thanks, > > On behalf of Apache EventMesh(Incubating) community > > > > - > > 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.3.0 rc0
Hi Folks, +1 (binding) from me, I have checked the following items: - Incubating in name - LICENSE and NOTICE are fine - DISCLAIMER-WIP exists - All links are valid - No unexpected binary files - All ASF files have ASF headers - The PGP key file has the correct download link - Checksums and PGP signatures are valid. In addition, it seems that the EventMesh website[1] of our project is missing 2 links [2][3]. It would be even better if it could be made up next time. :-) [1]https://eventmesh.apache.org/ [2]https://www.apache.org/security/ [3]https://www.apache.org/events/ Best regards, Xun Liu On Thu, Dec 23, 2021 at 4:45 PM mikexue wrote: > Hello Incubator Community, > > This is a call for a vote to release Apache EventMesh(Incubating) > version 1.3.0 rc0 > > The Apache EventMesh community has voted on and approved a proposal to > release Apache EventMesh(Incubating) version 1.3.0 rc0 > > We now kindly request the Incubator PMC members review and vote on > this incubator release. > > EventMesh community vote thread: > • https://lists.apache.org/thread/wolw8dvoxw1z53jc7cj52fj5vn8lt1m0 > > Vote result thread: > • https://lists.apache.org/thread/xkkq19onk7lrrlboqybjsvxhgtdvn11c > > The release candidate: > • > https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.3.0-rc0/ > > Git tag for the release: > • https://github.com/apache/incubator-eventmesh/tree/v1.3.0-rc0 > > Release notes: > • https://eventmesh.apache.org/events/release-notes/v1.3.0 > > The artifacts signed with PGP key > F84A0041D70B37AF9C7BF0B339F429D7579C25F5, corresponding to > mike...@apache.org, that can be found in keys file: > • https://downloads.apache.org/incubator/eventmesh/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 > > Thanks, > On behalf of Apache EventMesh(Incubating) community > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [MENTORS] Podling reporting timeline - reports due January 05
hi， justin Thank you for your enthusiastic reminder. The apache shenyu project has been received. Justin Mclean 于2021年12月24日周五 14:30写道： > > Hi, > > Reporting timeline is as follows: > Wed January 05 Podling reports due by end of day > Sun January 09 Shepherd reviews due by end of day > Sun January 09 Summary due by end of day > Tue January 11 Mentor signoff due by end of day > Wed January 12 Report submitted to Board > Wed January 19 Board meeting > > Expected to report are: > Annotator > BlueMarlin > DataLab > EventMesh > Flagon > Inlong > Liminal > Livy > Milagro > MXnet > Nuttx > Pagespeed > Pegasus > Pony Mail > Sdap > Shenyu > Teaclave > Toree > Training > Yunikorn > > The report is in the usual place [1], however I’m currently to fill in the > report text due to a confluence issue. Hopefully this will be fixe din a day > or two. > > Kind Regards, > Justin > > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/January2022 > - > 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: [Mentors] podling report text
I added the content. Let me know if it correct or needs further updates. Wilfred > On 24 Dec 2021, at 17:29, Justin Mclean wrote: > > Hi, > > i seem to be unable to post this into confluence, if someone could add this > it would be appreciated. > > > ## Annotator > > Annotator provides annotation enabling code for browsers, servers, and > humans. > > Annotator has been incubating since 2016-08-30. > > ### Three most important unfinished issues to address before graduating: > > 1. > 2. > 3. > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > > ### How has the community developed since the last report? > > > ### How has the project developed since the last report? > > > ### How would you assess the podling's maturity? > Please feel free to add your own commentary. > > - [ ] Initial setup > - [ ] Working towards first release > - [ ] Community building > - [ ] Nearing graduation > - [ ] Other: > > ### Date of last release: > > -XX-XX > > ### When were the last committers or PPMC members elected? > > > ### Have your mentors been helpful and responsive? > Are things falling through the cracks? If so, please list any > open issues that need to be addressed. > > ### Is the PPMC managing the podling's brand / trademarks? > Are 3rd parties respecting and correctly using the podlings > name and brand? If not what actions has the PPMC taken to > correct this? Has the VP, Brand approved the project name? > > ### Signed-off-by: > > - [ ] (annotator) Nick Kew > Comments: > - [ ] (annotator) Tommaso Teofili > Comments: > - [ ] (annotator) Benjamin Young > Comments: > > ### IPMC/Shepherd notes: > > > > > ## BlueMarlin > > BlueMarlin will develop a web service to add intelligence functionality to a > plain ad system. > > BlueMarlin has been incubating since 2020-06-09. > > ### Three most important unfinished issues to address before graduating: > > 1. > 2. > 3. > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > > ### How has the community developed since the last report? > > > ### How has the project developed since the last report? > > > ### How would you assess the podling's maturity? > Please feel free to add your own commentary. > > - [ ] Initial setup > - [ ] Working towards first release > - [ ] Community building > - [ ] Nearing graduation > - [ ] Other: > > ### Date of last release: > > -XX-XX > > ### When were the last committers or PPMC members elected? > > > ### Have your mentors been helpful and responsive? > Are things falling through the cracks? If so, please list any > open issues that need to be addressed. > > ### Is the PPMC managing the podling's brand / trademarks? > Are 3rd parties respecting and correctly using the podlings > name and brand? If not what actions has the PPMC taken to > correct this? Has the VP, Brand approved the project name? > > ### Signed-off-by: > > - [ ] (bluemarlin) Craig Russell > Comments: > - [ ] (bluemarlin) Jean-Baptiste Onofré > Comments: > - [ ] (bluemarlin) Von Gosling > Comments: > - [ ] (bluemarlin) Junping Du > Comments: > - [ ] (bluemarlin) Uma Maheswara Rao G > Comments: > > ### IPMC/Shepherd notes: > > > > > ## DataLab > > DataLab is a platform for creating self-service, exploratory data science > environments in the cloud using best-of-breed data science tools. > > DataLab has been incubating since 2018-08-20. > > ### Three most important unfinished issues to address before graduating: > > 1. > 2. > 3. > > ### Are there any issues that the IPMC or ASF Board need to be aware of? > > > ### How has the community developed since the last report? > > > ### How has the project developed since the last report? > > > ### How would you assess the podling's maturity? > Please feel free to add your own commentary. > > - [ ] Initial setup > - [ ] Working towards first release > - [ ] Community building > - [ ] Nearing graduation > - [ ] Other: > > ### Date of last release: > > -XX-XX > > ### When were the last committers or PPMC members elected? > > > ### Have your mentors been helpful and responsive? > Are things falling through the cracks? If so, please list any > open issues that need to be addressed. > > ### Is the PPMC managing the podling's brand / trademarks? > Are 3rd parties respecting and correctly using the podlings > name and brand? If not what actions has the PPMC taken to > correct this? Has the VP, Brand approved the project name? > > ### Signed-off-by: > > - [ ] (datalab) P. Taylor Goetz > Comments: > - [ ] (datalab) Henry Saputra > Comments: > - [ ] (datalab) Konstantin I Boudnik > Comments: > - [ ] (datalab) Furkan Kamaci > Comments: > > ### IPMC/Shepherd notes: > > > > > ## EventMesh > > EventMes
