date:20230212

Re: [VOTE] Release Apache Celeborn(Incubating) 0.2.0-incubating-rc4

2023-02-12 Thread Yu Li

Sorry guys, but I found a critical issue thus another -1 (binding)

* The source package contains a licenses-binary directory, which has
un-included dependency licenses (for source). Please check the packaging
script and confirm whether there is any error in it (the name of "licenses-
*binary*" indicates something wrong, which causes my attention)

Best Regards,
Yu


On Thu, 9 Feb 2023 at 18:43, angers zhu  wrote:

> +1 (no-binding)
>
> Checked:
>
> [1] ./build/make-distribution.sh -Pspark-3.1 (macOs Catalina 10.15.7)
> [2] RELEASE file are correct
> [3] jar soft link looks good
> [4] "incubating" in celeborn jar name
> [5] checksums are good
> [6] signatures are good.
>
> Kent Yao  于2023年2月8日周三 15:07写道：
>
> > +1 nonbinding
> >
> > - downloads ok
> > - All source files have license headers
> > - no binary files in the source release
> > - sig/checksums are ok
> > - notice/disclaimer/license files are good
> > - build from source successfully
> >
> > Kent Yao
> >
> > On 2023/02/08 02:40:34 Cheng Pan wrote:
> > >  +1 (no-binding)
> > >
> > > I checked
> > >
> > > - links are valid.
> > > - "incubating" is in the name.
> > > - LICENSE looks good.
> > > - NOTICE looks good.
> > > - DISCLAIMER exists.
> > >
> > > - signatures are good.
> > > ```
> > > gpg --verify apache-celeborn-0.2.0-incubating-source.tgz.asc
> > > gpg --verify apache-celeborn-0.2.0-incubating-bin.tgz.asc
> > > ```
> > >
> > > - checksums are good.
> > > ```
> > > sha512sum --check apache-celeborn-0.2.0-incubating-bin.tgz.sha512
> > > sha512sum --check apache-celeborn-0.2.0-incubating-source.tgz.sha512
> > > ```
> > >
> > > - build success from source code (openjdk-8, ubuntu 22.04 x86).
> > > ```
> > > build/make-distribution.sh --release
> > > ```
> > >
> > > Thanks,
> > > Cheng Pan
> > >
> > >
> > > On Feb 8, 2023 at 10:37:32, Ethan Feng  wrote:
> > >
> > > > Hello Incubator Community,
> > > >
> > > > This is a call for a vote to release Apache Celeborn(Incubating)
> > > > version 0.2.0-incubating-rc4
> > > >
> > > > The Apache Celeborn community has voted on and approved a proposal to
> > > > release
> > > > Apache Celeborn(Incubating) version 0.2.0-incubating-rc4
> > > >
> > > > We now kindly request the Incubator PMC members review and vote on
> this
> > > > incubator release.
> > > >
> > > > Celeborn community vote thread:
> > > > • https://lists.apache.org/thread/3qv3byyy1rqv7l9qsx02gbto1n9ymd1h
> > > >
> > > > Vote result thread:
> > > > • https://lists.apache.org/thread/k4jvqdd0dwk9dc7t6n80tgqv99fmwok7
> > > >
> > > > The release candidate:
> > > > •
> > > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.2.0-incubating-rc4
> > > >
> > > > Git tag for the release:
> > > > •
> > > >
> >
> https://github.com/apache/incubator-celeborn/releases/tag/v0.2.0-incubating-rc4
> > > >
> > > > Public keys file:
> > > > • https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS
> > > >
> > > > The change log is available in:
> > > > •
> > > >
> >
> https://github.com/apache/incubator-celeborn/compare/v0.1.4...v0.2.0-incubating-rc4
> > > >
> > > > The vote will be open for at least 72 hours or until the necessary
> > number
> > > > of votes are reached.
> > > >
> > > > Please vote accordingly:
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > More detailed checklist please refer:
> > > > •
> > > >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > > >
> > > > Steps to validate the release， Please refer to:
> > > > • https://www.apache.org/info/verification.html
> > > >
> > > > Thanks,
> > > > On behalf of Apache Celeborn(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 StreamPark(Incubating) 2.0.0-RC6

2023-02-12 Thread kezhenxu94

It depends, if you wrote the codes of `AssertUtils.scala` from scratch without 
referencing
the Spring's Assert class, you can definitely said it's your own work and your 
own IP,
but if you copied the content from Spring's, and converted it into Scala, even 
with some modifications,
I still consider it's originated from Spring project.

And the most important thing is that, you listed it in the LICENSE file
and admit that it's copied from Spring project.

If you don't agree it's copied from the Spring project,
you should remove it from the LICENSE file, but I don't think that's the case.

P.S. Sorry, I know it's me who raised this issue in the previous RC vote, if 
you think
that file is not copied from Spring project, you could clarify it
and I'd be happy to turn my vote into +1 when convinced.

> On Feb 13, 2023, at 15:28, Huajie Wang  wrote:
> 
> Thanks for your review and feedback, we will fix this issue, but I
> have a question:
> 
> As we all know, spring is developed in java language, while
> Streampark's AssertUtils.scala[1] is developed in scala. As you can
> see, the methods and logic in it are very simple. Even if the logic
> and method names in AssertUtils.scala are the same as in spring, it
> cannot be said that AssertUtils.scala is copied from spring's code. In
> other words, I implemented it in another language, like .net. Can you
> tell me that I copied the code? I don't know how this part is defined
> in ASF?
> 
> [1] 
> streampark-common/src/main/scala/org/apache/streampark/common/util/AssertUtils.scala
> 
> 
> Best,
> Huajie Wang
> 
> 
> 
> kezhenxu94  于2023年2月13日周一 14:48写道：
> 
>> Hi, -1 (binding), you cannot change the license header of a third-party's
>> file[1] as you mentioned in LICENSE it's from Spring team[2].
>> 
>> [1]
>> streampark-common/src/main/scala/org/apache/streampark/common/util/AssertUtils.scala
>> [2] https://github.com/spring-projects/spring-framework
>> 
>>> On Feb 10, 2023, at 17:44, Huajie Wang  wrote:
>>> 
>>> Hello Incubator Community:
>>> 
>>> This is a call for a vote to release Apache StreamPark(Incubating)
>>> version 2.0.0-RC6
>>> 
>>> The Apache StreamPark community has voted on and approved a proposal to
>>> release
>>> Apache StreamPark(Incubating) version 2.0.0-RC6
>>> 
>>> We now kindly request the Incubator PMC members review and vote on this
>>> incubator release.
>>> 
>>> Apache StreamPark, Make stream processing easier! easy-to-use streaming
>>> application development framework and operation platform.
>>> 
>>> 
>>> StreamPark community vote thread:
>>> https://lists.apache.org/thread/lvpc2hywbkdlvkpmjm0knchyk6vhvmnl
>>> 
>>> Vote result thread:
>>> https://lists.apache.org/thread/y77vc8c3d5x7wtslm99jydgwmp10ypxv
>>> 
>>> 
>>> The release candidate:
>>> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC6/
>>> 
>>> Git tag for the release:
>>> https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc6
>>> 
>>> Release notes:
>>> https://streampark.apache.org/download/release-note/2.0.0/
>>> 
>>> Maven artifacts are available in a staging repository at:
>>> 
>> https://repository.apache.org/content/repositories/orgapachestreampark-1009/
>>> 
>>> The artifacts signed with PGP key [5AE01B8E], corresponding to [
>>> benj...@apache.org], that can be found in keys file:
>>> https://downloads.apache.org/incubator/streampark/KEYS
>>> 
>>> 
>>> Last commit hash:
>>> •apache-streampark-2.0.0-incubating-src.tar.gz:
>>> 
>> 91083d97727e302997ae35e54e583340101d2e88968495b78fae16c32a0bd47dc0b87aa285f2a6279758906b811ca6665fb2b0120ebbb6d8d41a4da1263bca23
>>> 
>>> 
>>> • apache-streampark_2.11-2.0.0-incubating-bin.tar.gz:
>>> 
>> e055643a1657cd4f4dd1352d22bdafd9b3dd2cece5698f503e2a46bd8c1ad6d1a559e2c1041b528b65701f268ba0ae2aefc9072c9a1b0c783fc45c91ec2e88f9
>>> 
>>> 
>>> • apache-streampark_2.12-2.0.0-incubating-bin.tar.gz:
>>> 
>> 0fbccc5f3fec8c997fea61d60a399f69ab60abfa21e00a07d7bfce92773ef1a19780c3d639e8411b0ac8891f388ed62ff9b437bfec6c7bfcea3f5debbc98be88
>>> 
>>> In this vote we fixed RC4,RC5 vote process issue, and some licenses
>> issues
>>> mentioned in RC3 vote process:
>>> https://github.com/apache/incubator-streampark/pull/2277
>>> 
>>> 
>>> The vote will be open for at least 72 hours or until the necessary number
>>> of votes are reached.
>>> 
>>> Please vote accordingly:
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove with the reason
>>> 
>>> More detailed checklist please refer:
>>> •
>>> 
>> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>>> 
>>> Steps to validate the release， Please refer to:
>>> • https://www.apache.org/info/verification.html
>>> • https://streampark.apache.org/community/release/how-to-verify
>>> 
>>> 
>>> How to Build:
>>> 
>>> 1) clone source code:
 git clone -b v2.0.0-rc6 g...@github.com:apache/incubator-streampark.git
>>> 
>>> 2) build project:
 cd incubator-streampark && sh ./build.sh
>>> 
>>> 
>>> Thanks,
>>> 
>>> On behalf of Apache

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

2023-02-12 Thread Huajie Wang

Thanks for your review and feedback, we will fix this issue, but I
have a question:

As we all know, spring is developed in java language, while
Streampark's AssertUtils.scala[1] is developed in scala. As you can
see, the methods and logic in it are very simple. Even if the logic
and method names in AssertUtils.scala are the same as in spring, it
cannot be said that AssertUtils.scala is copied from spring's code. In
other words, I implemented it in another language, like .net. Can you
tell me that I copied the code? I don't know how this part is defined
in ASF?

[1] 
streampark-common/src/main/scala/org/apache/streampark/common/util/AssertUtils.scala


Best,
Huajie Wang



kezhenxu94  于2023年2月13日周一 14:48写道：

> Hi, -1 (binding), you cannot change the license header of a third-party's
> file[1] as you mentioned in LICENSE it's from Spring team[2].
>
> [1]
> streampark-common/src/main/scala/org/apache/streampark/common/util/AssertUtils.scala
> [2] https://github.com/spring-projects/spring-framework
>
> > On Feb 10, 2023, at 17:44, Huajie Wang  wrote:
> >
> > Hello Incubator Community:
> >
> > This is a call for a vote to release Apache StreamPark(Incubating)
> > version 2.0.0-RC6
> >
> > The Apache StreamPark community has voted on and approved a proposal to
> > release
> > Apache StreamPark(Incubating) version 2.0.0-RC6
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Apache StreamPark, Make stream processing easier! easy-to-use streaming
> > application development framework and operation platform.
> >
> >
> > StreamPark community vote thread:
> > https://lists.apache.org/thread/lvpc2hywbkdlvkpmjm0knchyk6vhvmnl
> >
> > Vote result thread:
> > https://lists.apache.org/thread/y77vc8c3d5x7wtslm99jydgwmp10ypxv
> >
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC6/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc6
> >
> > Release notes:
> > https://streampark.apache.org/download/release-note/2.0.0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> https://repository.apache.org/content/repositories/orgapachestreampark-1009/
> >
> > The artifacts signed with PGP key [5AE01B8E], corresponding to [
> > benj...@apache.org], that can be found in keys file:
> > https://downloads.apache.org/incubator/streampark/KEYS
> >
> >
> > Last commit hash:
> > •apache-streampark-2.0.0-incubating-src.tar.gz:
> >
> 91083d97727e302997ae35e54e583340101d2e88968495b78fae16c32a0bd47dc0b87aa285f2a6279758906b811ca6665fb2b0120ebbb6d8d41a4da1263bca23
> >
> >
> > • apache-streampark_2.11-2.0.0-incubating-bin.tar.gz:
> >
> e055643a1657cd4f4dd1352d22bdafd9b3dd2cece5698f503e2a46bd8c1ad6d1a559e2c1041b528b65701f268ba0ae2aefc9072c9a1b0c783fc45c91ec2e88f9
> >
> >
> > • apache-streampark_2.12-2.0.0-incubating-bin.tar.gz:
> >
> 0fbccc5f3fec8c997fea61d60a399f69ab60abfa21e00a07d7bfce92773ef1a19780c3d639e8411b0ac8891f388ed62ff9b437bfec6c7bfcea3f5debbc98be88
> >
> > In this vote we fixed RC4,RC5 vote process issue, and some licenses
> issues
> > mentioned in RC3 vote process:
> > https://github.com/apache/incubator-streampark/pull/2277
> >
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > More detailed checklist please refer:
> > •
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Steps to validate the release， Please refer to:
> > • https://www.apache.org/info/verification.html
> > • https://streampark.apache.org/community/release/how-to-verify
> >
> >
> > How to Build:
> >
> > 1) clone source code:
> >> git clone -b v2.0.0-rc6 g...@github.com:apache/incubator-streampark.git
> >
> > 2) build project:
> >> cd incubator-streampark && sh ./build.sh
> >
> >
> > Thanks,
> >
> > On behalf of Apache StreamPark(Incubating) community
> >
> >
> > Best,
> > Huajie Wang
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

2023-02-12 Thread Liang Chen

+1 (binding)

I checked : 
- [X] Download links are valid.
- [X] signatures and hashes are ok.
- [X] No binary files
- [X] LICENSE and NOTICE are ok
- [X] incubating in name, all source files have ASF headers.

Regards
Liang

On 2023/02/13 02:41:51 hulk wrote:
> +1 (non-binding)
> 
> I checked:
> [x] Download links are valid.
> [x] Checksums and signatures.
> [x] LICENSE/NOTICE files exist
> [x] No unexpected binary files
> [x] All source files have ASF headers
> [x] Can compile from source
> [x] All Tests Passed
> [x] Docker image with right version
> [x] Docker image contains license files
> [x] Docker image can work well
> 
> 
> 
> On Mon, 13 Feb 2023 at 10:30, Xiaoqiao He  wrote:
> >
> > +1 (binding).
> >
> > - Download links are valid.
> > - Checksums and signatures are valid.
> > - LICENSE, NOTICE and DISCLAIMER files exist.
> > - All source files have apache license declare if necessary.
> > - Compile from source passed.
> > - No compiled archives bundled in the source archive.
> > - Run successfully simple commands about put,get etc.
> >
> > Best Regards,
> > - He Xiaoqiao
> >
> >
> > On Sun, Feb 12, 2023 at 7:24 PM tison  wrote:
> >
> > > +1 (binding)
> > >
> > > Verified:
> > >
> > > - [X] Download links are valid.
> > > - [X] Checksums and PGP signatures are valid.
> > > - [X] Source code artifacts have correct names matching the current
> > > release.
> > > - [X] LICENSE, NOTICE and DISCLAIMER are correct for the repository.
> > > - [X] All files have license headers if necessary.
> > > - [X] No compiled archives bundled in the source archive.
> > > - [X] Building is OK with: ./x.py build --ninja --ghproxy
> > > - [X] Stage docker image runs and serves properly
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Chao Zhang  于2023年2月12日周日 18:33写道：
> > >
> > > > Hi,
> > > >
> > > > +1 (non-binding) from me. I have checked:
> > > >
> > > > 1. All the above links are correct;
> > > > 2. The signature and checksum are correct;
> > > > 3. LICENSE and NOTICE files exist;
> > > >
> > > > Best regards
> > > > Chao Zhang
> > > >
> > > > https://github.com/tokers
> > > >
> > > > On Sat, Feb 11, 2023 at 10:44 PM Myth  wrote:
> > > > >
> > > > > Hello Incubator PMC,
> > > > >
> > > > > The Apache Kvrocks community has voted and approved the release of
> > > Apache
> > > > > Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members
> > > review
> > > > > and vote for this release.
> > > > >
> > > > > This is  the second call for a vote. The first call for a vote, which
> > > is
> > > > > cancelled:
> > > > > *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt
> > > > > *
> > > > >
> > > > > Kvrocks is a distributed key value NoSQL database that uses RocksDB as
> > > > the
> > > > > storage engine and is compatible with Redis protocol. The current
> > > release
> > > > > provides many new features, many improvements and fixes many bugs.
> > > > >
> > > > > Kvrocks community vote thread:
> > > > > https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2
> > > > >
> > > > > Vote result thread:
> > > > > https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw
> > > > >
> > > > > The release candidate:
> > > > > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/
> > > > >
> > > > > This release has been signed with a PGP available here:
> > > > > https://downloads.apache.org/incubator/kvrocks/KEYS
> > > > >
> > > > > Git tag for the release:
> > > > > https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0
> > > > >
> > > > > Docker image:
> > > > >
> > > >
> > > https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807
> > > > >
> > > > > Build guide can be found at:
> > > > > https://github.com/apache/incubator-kvrocks#build
> > > > >
> > > > > The vote will be open for at least 72 hours or until the necessary
> > > number
> > > > > of votes is reached.
> > > > >
> > > > > Please vote accordingly:
> > > > > [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.3.0
> > > > > [ ] +0
> > > > > [ ] -1 Do not approve (please specify the reason)
> > > > >
> > > > > Thanks
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> 
> 
> 
> --
> Best Regards,
> - Hulk Lin
> 
> -
> 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 StreamPark(Incubating) 2.0.0-RC6

2023-02-12 Thread kezhenxu94

Hi, -1 (binding), you cannot change the license header of a third-party's 
file[1] as you mentioned in LICENSE it's from Spring team[2].

[1] 
streampark-common/src/main/scala/org/apache/streampark/common/util/AssertUtils.scala
[2] https://github.com/spring-projects/spring-framework

> On Feb 10, 2023, at 17:44, Huajie Wang  wrote:
> 
> Hello Incubator Community:
> 
> This is a call for a vote to release Apache StreamPark(Incubating)
> version 2.0.0-RC6
> 
> The Apache StreamPark community has voted on and approved a proposal to
> release
> Apache StreamPark(Incubating) version 2.0.0-RC6
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> Apache StreamPark, Make stream processing easier! easy-to-use streaming
> application development framework and operation platform.
> 
> 
> StreamPark community vote thread:
> https://lists.apache.org/thread/lvpc2hywbkdlvkpmjm0knchyk6vhvmnl
> 
> Vote result thread:
> https://lists.apache.org/thread/y77vc8c3d5x7wtslm99jydgwmp10ypxv
> 
> 
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC6/
> 
> Git tag for the release:
> https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc6
> 
> Release notes:
> https://streampark.apache.org/download/release-note/2.0.0/
> 
> Maven artifacts are available in a staging repository at:
> https://repository.apache.org/content/repositories/orgapachestreampark-1009/
> 
> The artifacts signed with PGP key [5AE01B8E], corresponding to [
> benj...@apache.org], that can be found in keys file:
> https://downloads.apache.org/incubator/streampark/KEYS
> 
> 
> Last commit hash:
> •apache-streampark-2.0.0-incubating-src.tar.gz:
> 91083d97727e302997ae35e54e583340101d2e88968495b78fae16c32a0bd47dc0b87aa285f2a6279758906b811ca6665fb2b0120ebbb6d8d41a4da1263bca23
> 
> 
> • apache-streampark_2.11-2.0.0-incubating-bin.tar.gz:
> e055643a1657cd4f4dd1352d22bdafd9b3dd2cece5698f503e2a46bd8c1ad6d1a559e2c1041b528b65701f268ba0ae2aefc9072c9a1b0c783fc45c91ec2e88f9
> 
> 
> • apache-streampark_2.12-2.0.0-incubating-bin.tar.gz:
> 0fbccc5f3fec8c997fea61d60a399f69ab60abfa21e00a07d7bfce92773ef1a19780c3d639e8411b0ac8891f388ed62ff9b437bfec6c7bfcea3f5debbc98be88
> 
> In this vote we fixed RC4,RC5 vote process issue, and some licenses issues
> mentioned in RC3 vote process:
> https://github.com/apache/incubator-streampark/pull/2277
> 
> 
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
> 
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> More detailed checklist please refer:
> •
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> 
> Steps to validate the release， Please refer to:
> • https://www.apache.org/info/verification.html
> • https://streampark.apache.org/community/release/how-to-verify
> 
> 
> How to Build:
> 
> 1) clone source code:
>> git clone -b v2.0.0-rc6 g...@github.com:apache/incubator-streampark.git
> 
> 2) build project:
>> cd incubator-streampark && sh ./build.sh
> 
> 
> Thanks,
> 
> On behalf of Apache StreamPark(Incubating) community
> 
> 
> Best,
> Huajie Wang


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread li gang

+1 (binding)
Good luck.

Eason Chen  于2023年2月10日周五 10:32写道：

> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
>
> Here is an overview of the Apache EventMesh(incubating) to help with the
> vote.
>
> *Community*
>
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
>
> *Project*
>
> ● Apache EventMesh(incubating) builds a fully serverless platform for
> distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
>
> *Brands, License, and Copyright*
>
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache EventMesh Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a fully serverless platform used to build distributed
> event-driven applications.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to a fully
> serverless platform used to build distributed event-driven applications;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache EventMesh
> Project:
>
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   
>  * Wenjun Ruan  
>  * XiaoShuang Li
>  * Xue Weiming  
>  * Yuwei Zhu
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eason

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

2023-02-12 Thread Huajie Wang

hi Kent Yao:

The current download page[1] is just a template, all links are empty links,
and there is no content about the release of version 2.0,

The previously failed RCs users will download and use. so deleted, I
don't konw if this will be the reason for block the release.


[1] https://streampark.apache.org/download/


Best,
Huajie Wang



Kent Yao  于2023年2月13日周一 11:46写道：

> Hi
>
> (-1, non-binding): There is a spoiler for 2.0.0 on your download page[1],
> you shall remove it as it's not been approved yet.
>
> The previously failed RCs, e.g. [2] have been deleted, which makes it
> difficult for others to
> track the history of the 2.0.0 voting progress.
>
>
> Kent Yao
>
> [1] https://streampark.apache.org/download/
> [2] https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc5
>
> On 2023/02/13 03:01:41 Qingrong wang wrote:
> > +1 (non-binding):
> > I checked:
> > 1. All download links are valid
> > 2.The source and distribution packages already exist
> > 3. Checksum and signature are OK
> > 4. LICENSE and NOTICE are exist and NOTICE  file year is ok
> > 5. Build successfully on ubuntu22.04
> >
> > Huajie Wang  于2023年2月10日周五 17:46写道：
> > >
> > > Hello Incubator Community:
> > >
> > > This is a call for a vote to release Apache StreamPark(Incubating)
> > > version 2.0.0-RC6
> > >
> > > The Apache StreamPark community has voted on and approved a proposal to
> > > release
> > > Apache StreamPark(Incubating) version 2.0.0-RC6
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > Apache StreamPark, Make stream processing easier! easy-to-use streaming
> > > application development framework and operation platform.
> > >
> > >
> > > StreamPark community vote thread:
> > > https://lists.apache.org/thread/lvpc2hywbkdlvkpmjm0knchyk6vhvmnl
> > >
> > > Vote result thread:
> > > https://lists.apache.org/thread/y77vc8c3d5x7wtslm99jydgwmp10ypxv
> > >
> > >
> > > The release candidate:
> > > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC6/
> > >
> > > Git tag for the release:
> > > https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc6
> > >
> > > Release notes:
> > > https://streampark.apache.org/download/release-note/2.0.0/
> > >
> > > Maven artifacts are available in a staging repository at:
> > >
> https://repository.apache.org/content/repositories/orgapachestreampark-1009/
> > >
> > > The artifacts signed with PGP key [5AE01B8E], corresponding to [
> > > benj...@apache.org], that can be found in keys file:
> > > https://downloads.apache.org/incubator/streampark/KEYS
> > >
> > >
> > > Last commit hash:
> > > •apache-streampark-2.0.0-incubating-src.tar.gz:
> > >
> 91083d97727e302997ae35e54e583340101d2e88968495b78fae16c32a0bd47dc0b87aa285f2a6279758906b811ca6665fb2b0120ebbb6d8d41a4da1263bca23
> > >
> > >
> > > • apache-streampark_2.11-2.0.0-incubating-bin.tar.gz:
> > >
> e055643a1657cd4f4dd1352d22bdafd9b3dd2cece5698f503e2a46bd8c1ad6d1a559e2c1041b528b65701f268ba0ae2aefc9072c9a1b0c783fc45c91ec2e88f9
> > >
> > >
> > > • apache-streampark_2.12-2.0.0-incubating-bin.tar.gz:
> > >
> 0fbccc5f3fec8c997fea61d60a399f69ab60abfa21e00a07d7bfce92773ef1a19780c3d639e8411b0ac8891f388ed62ff9b437bfec6c7bfcea3f5debbc98be88
> > >
> > > In this vote we fixed RC4,RC5 vote process issue, and some licenses
> issues
> > > mentioned in RC3 vote process:
> > > https://github.com/apache/incubator-streampark/pull/2277
> > >
> > >
> > > The vote will be open for at least 72 hours or until the necessary
> number
> > > of votes are reached.
> > >
> > > Please vote accordingly:
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > More detailed checklist please refer:
> > > •
> > >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > >
> > > Steps to validate the release， Please refer to:
> > > • https://www.apache.org/info/verification.html
> > > • https://streampark.apache.org/community/release/how-to-verify
> > >
> > >
> > > How to Build:
> > >
> > > 1) clone source code:
> > > > git clone -b v2.0.0-rc6 g...@github.com:
> apache/incubator-streampark.git
> > >
> > > 2) build project:
> > > > cd incubator-streampark && sh ./build.sh
> > >
> > >
> > > Thanks,
> > >
> > > On behalf of Apache StreamPark(Incubating) community
> > >
> > >
> > > Best,
> > > Huajie Wang
> >
> > -
> > 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] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread 尹强

+1 non-binding.
Good luck.

Xin Wang  于2023年2月13日周一 11:17写道：

> +1
>
> Jerry Tan  于2023年2月13日周一 10:48写道：
>
> > +1.
> > Good luck and best regards.
> >
> > On Mon, Feb 13, 2023 at 10:28 AM xiong mengfei 
> > wrote:
> >
> > > +1
> > >
> > > On Mon, Feb 13, 2023 at 10:22 AM sanchen  wrote:
> > >
> > > > +1
> > > >
> > > >
> > > > >
> > > > > On 2023/02/10 02:31:56 Eason Chen wrote:
> > > > > > Dear Apache Incubator Community and IPMC members,
> > > > > >
> > > > > > After having the graduation discussion in the EventMesh community
> > > [1],
> > > > > > we passed the vote within the EventMesh community [2] and the
> vote
> > > > > > result was published[3].
> > > > > > We then discussed the graduation for EventMesh in the Apache
> > > Incubator
> > > > > > Community [4], where no issues were raised and positive replies
> > were
> > > > > > received.
> > > > > >
> > > > > > I would like to start this voting thread to request graduating
> > Apache
> > > > > > EventMesh(incubating) from Apache Incubator as a Top Level
> Project.
> > > > > >
> > > > > > Please provide your vote accordingly:
> > > > > > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > > > > > Apache Incubator.
> > > > > > [ ] +0 No opinion.
> > > > > > [ ] -1 No, the EventMesh project is not ready to graduate,
> > because...
> > > > > >
> > > > > > Thank you for participating in the vote. This vote will stay open
> > for
> > > > > > at least 72 hours.
> > > > > >
> > > > > > Here is an overview of the Apache EventMesh(incubating) to help
> > with
> > > > the
> > > > > vote.
> > > > > >
> > > > > > *Community*
> > > > > >
> > > > > > ● 5 new PPMC members were added, bringing the total number of
> PPMC
> > > > > > members to 14 from at least 9 different organizations.
> > > > > > ● 20 new Committers were added, bringing the total number of
> > > > > > committers to 42 from at least 30 different organizations.
> > > > > > ● 220+ new contributors participate in the community. The number
> of
> > > > > > contributors is now 250+ and growing.
> > > > > > ● 20 Bi-weekly online meetings were held among the committers,
> > > > > > contributors, and users. The meeting minutes are recorded on the
> > > > > > mailing list[5] and cwiki [6].
> > > > > > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > > > > > ● We've confirmed the VP, PMC, and Committers in the preparation
> > > > > > discussion at private@eventmesh [7]. Eason
> > > > > > Chen(chenguangsh...@apache.org) was recommended as Vice
> President.
> > > > > >
> > > > > > *Project*
> > > > > >
> > > > > > ● Apache EventMesh(incubating) builds a fully serverless platform
> > for
> > > > > > distributed event-driven applications.
> > > > > > ● Project maturity model is detailed in [8].
> > > > > > ● EventMesh has been incubating [9] since 2021-02-18 for over 23
> > > > months.
> > > > > > ● EventMesh community released a total of 7 Apache releases [10]
> > by 6
> > > > > > different release managers from 5 different organizations.
> > > > > > ● 1300+ issues created, and 1100+ issues closed [11].
> > > > > > ● 1600+ pull requests created, and 1600+ pull requests closed
> [12],
> > > > > > 2500+ commits added.
> > > > > > ● The release cadence is about 3 months, with an average of 180+
> > > > > > issues and 230+ pull requests per release.
> > > > > > ● Please refer to the EventMesh project incubation status
> [13][14]
> > > for
> > > > > > more information.
> > > > > >
> > > > > > *Brands, License, and Copyright*
> > > > > >
> > > > > > ● We applied the brand [15], which has been reviewed and
> approved.
> > > > > > ● EventMesh community maintains project code on GitHub and all
> > > modules
> > > > > > code is under Apache 2.0 license. We have reviewed all the
> > > > > > dependencies and ensured they do not bring any license issues
> [16].
> > > > > > All the status files, license headers, and copyright are up to
> > date.
> > > > > > ● EventMesh official website [17] is compliant with Apache
> > Foundation
> > > > > > requirements[18].
> > > > > >
> > > > > > -
> > > > > > BEGINNING OF DRAFT RESOLUTION
> > > > > > -
> > > > > >
> > > > > > Establish the Apache EventMesh Project
> > > > > >
> > > > > > WHEREAS, the Board of Directors deems it to be in the best
> > interests
> > > of
> > > > > > the Foundation and consistent with the Foundation's purpose to
> > > > establish
> > > > > > a Project Management Committee charged with the creation and
> > > > maintenance
> > > > > > of open-source software, for distribution at no charge to the
> > public,
> > > > > > related to a fully serverless platform used to build distributed
> > > > > > event-driven applications.
> > > > > >
> > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee
> > > > > > (PMC), to be known as the "Apache EventMesh Project", be and
> hereby
> > > is
> > > > > >

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

2023-02-12 Thread 陈卓宇

+1 (non-binding):
I checked:
1. All download links are valid
2.The source and distribution packages already exist
3. Checksum and signature are OK
4. LICENSE and NOTICE are exist and NOTICE  file year is ok
5. Build successfully on ubuntu22.04

Kent Yao  于2023年2月13日周一 11:46写道：

> Hi
>
> (-1, non-binding): There is a spoiler for 2.0.0 on your download page[1],
> you shall remove it as it's not been approved yet.
>
> The previously failed RCs, e.g. [2] have been deleted, which makes it
> difficult for others to
> track the history of the 2.0.0 voting progress.
>
>
> Kent Yao
>
> [1] https://streampark.apache.org/download/
> [2] https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc5
>
> On 2023/02/13 03:01:41 Qingrong wang wrote:
> > +1 (non-binding):
> > I checked:
> > 1. All download links are valid
> > 2.The source and distribution packages already exist
> > 3. Checksum and signature are OK
> > 4. LICENSE and NOTICE are exist and NOTICE  file year is ok
> > 5. Build successfully on ubuntu22.04
> >
> > Huajie Wang  于2023年2月10日周五 17:46写道：
> > >
> > > Hello Incubator Community:
> > >
> > > This is a call for a vote to release Apache StreamPark(Incubating)
> > > version 2.0.0-RC6
> > >
> > > The Apache StreamPark community has voted on and approved a proposal to
> > > release
> > > Apache StreamPark(Incubating) version 2.0.0-RC6
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > Apache StreamPark, Make stream processing easier! easy-to-use streaming
> > > application development framework and operation platform.
> > >
> > >
> > > StreamPark community vote thread:
> > > https://lists.apache.org/thread/lvpc2hywbkdlvkpmjm0knchyk6vhvmnl
> > >
> > > Vote result thread:
> > > https://lists.apache.org/thread/y77vc8c3d5x7wtslm99jydgwmp10ypxv
> > >
> > >
> > > The release candidate:
> > > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC6/
> > >
> > > Git tag for the release:
> > > https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc6
> > >
> > > Release notes:
> > > https://streampark.apache.org/download/release-note/2.0.0/
> > >
> > > Maven artifacts are available in a staging repository at:
> > >
> https://repository.apache.org/content/repositories/orgapachestreampark-1009/
> > >
> > > The artifacts signed with PGP key [5AE01B8E], corresponding to [
> > > benj...@apache.org], that can be found in keys file:
> > > https://downloads.apache.org/incubator/streampark/KEYS
> > >
> > >
> > > Last commit hash:
> > > •apache-streampark-2.0.0-incubating-src.tar.gz:
> > >
> 91083d97727e302997ae35e54e583340101d2e88968495b78fae16c32a0bd47dc0b87aa285f2a6279758906b811ca6665fb2b0120ebbb6d8d41a4da1263bca23
> > >
> > >
> > > • apache-streampark_2.11-2.0.0-incubating-bin.tar.gz:
> > >
> e055643a1657cd4f4dd1352d22bdafd9b3dd2cece5698f503e2a46bd8c1ad6d1a559e2c1041b528b65701f268ba0ae2aefc9072c9a1b0c783fc45c91ec2e88f9
> > >
> > >
> > > • apache-streampark_2.12-2.0.0-incubating-bin.tar.gz:
> > >
> 0fbccc5f3fec8c997fea61d60a399f69ab60abfa21e00a07d7bfce92773ef1a19780c3d639e8411b0ac8891f388ed62ff9b437bfec6c7bfcea3f5debbc98be88
> > >
> > > In this vote we fixed RC4,RC5 vote process issue, and some licenses
> issues
> > > mentioned in RC3 vote process:
> > > https://github.com/apache/incubator-streampark/pull/2277
> > >
> > >
> > > The vote will be open for at least 72 hours or until the necessary
> number
> > > of votes are reached.
> > >
> > > Please vote accordingly:
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > More detailed checklist please refer:
> > > •
> > >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > >
> > > Steps to validate the release， Please refer to:
> > > • https://www.apache.org/info/verification.html
> > > • https://streampark.apache.org/community/release/how-to-verify
> > >
> > >
> > > How to Build:
> > >
> > > 1) clone source code:
> > > > git clone -b v2.0.0-rc6 g...@github.com:
> apache/incubator-streampark.git
> > >
> > > 2) build project:
> > > > cd incubator-streampark && sh ./build.sh
> > >
> > >
> > > Thanks,
> > >
> > > On behalf of Apache StreamPark(Incubating) community
> > >
> > >
> > > Best,
> > > Huajie Wang
> >
> > -
> > 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 StreamPark(Incubating) 2.0.0-RC6

2023-02-12 Thread Kent Yao

Hi

(-1, non-binding): There is a spoiler for 2.0.0 on your download page[1], you 
shall remove it as it's not been approved yet.

The previously failed RCs, e.g. [2] have been deleted, which makes it difficult 
for others to
track the history of the 2.0.0 voting progress.


Kent Yao

[1] https://streampark.apache.org/download/
[2] https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc5

On 2023/02/13 03:01:41 Qingrong wang wrote:
> +1 (non-binding):
> I checked:
> 1. All download links are valid
> 2.The source and distribution packages already exist
> 3. Checksum and signature are OK
> 4. LICENSE and NOTICE are exist and NOTICE  file year is ok
> 5. Build successfully on ubuntu22.04
> 
> Huajie Wang  于2023年2月10日周五 17:46写道：
> >
> > Hello Incubator Community:
> >
> > This is a call for a vote to release Apache StreamPark(Incubating)
> > version 2.0.0-RC6
> >
> > The Apache StreamPark community has voted on and approved a proposal to
> > release
> > Apache StreamPark(Incubating) version 2.0.0-RC6
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Apache StreamPark, Make stream processing easier! easy-to-use streaming
> > application development framework and operation platform.
> >
> >
> > StreamPark community vote thread:
> > https://lists.apache.org/thread/lvpc2hywbkdlvkpmjm0knchyk6vhvmnl
> >
> > Vote result thread:
> > https://lists.apache.org/thread/y77vc8c3d5x7wtslm99jydgwmp10ypxv
> >
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC6/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc6
> >
> > Release notes:
> > https://streampark.apache.org/download/release-note/2.0.0/
> >
> > Maven artifacts are available in a staging repository at:
> > https://repository.apache.org/content/repositories/orgapachestreampark-1009/
> >
> > The artifacts signed with PGP key [5AE01B8E], corresponding to [
> > benj...@apache.org], that can be found in keys file:
> > https://downloads.apache.org/incubator/streampark/KEYS
> >
> >
> > Last commit hash:
> > •apache-streampark-2.0.0-incubating-src.tar.gz:
> > 91083d97727e302997ae35e54e583340101d2e88968495b78fae16c32a0bd47dc0b87aa285f2a6279758906b811ca6665fb2b0120ebbb6d8d41a4da1263bca23
> >
> >
> > • apache-streampark_2.11-2.0.0-incubating-bin.tar.gz:
> > e055643a1657cd4f4dd1352d22bdafd9b3dd2cece5698f503e2a46bd8c1ad6d1a559e2c1041b528b65701f268ba0ae2aefc9072c9a1b0c783fc45c91ec2e88f9
> >
> >
> > • apache-streampark_2.12-2.0.0-incubating-bin.tar.gz:
> > 0fbccc5f3fec8c997fea61d60a399f69ab60abfa21e00a07d7bfce92773ef1a19780c3d639e8411b0ac8891f388ed62ff9b437bfec6c7bfcea3f5debbc98be88
> >
> > In this vote we fixed RC4,RC5 vote process issue, and some licenses issues
> > mentioned in RC3 vote process:
> > https://github.com/apache/incubator-streampark/pull/2277
> >
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > More detailed checklist please refer:
> > •
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Steps to validate the release， Please refer to:
> > • https://www.apache.org/info/verification.html
> > • https://streampark.apache.org/community/release/how-to-verify
> >
> >
> > How to Build:
> >
> > 1) clone source code:
> > > git clone -b v2.0.0-rc6 g...@github.com:apache/incubator-streampark.git
> >
> > 2) build project:
> > > cd incubator-streampark && sh ./build.sh
> >
> >
> > Thanks,
> >
> > On behalf of Apache StreamPark(Incubating) community
> >
> >
> > Best,
> > Huajie Wang
> 
> -
> 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] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread Xin Wang

+1

Jerry Tan  于2023年2月13日周一 10:48写道：

> +1.
> Good luck and best regards.
>
> On Mon, Feb 13, 2023 at 10:28 AM xiong mengfei 
> wrote:
>
> > +1
> >
> > On Mon, Feb 13, 2023 at 10:22 AM sanchen  wrote:
> >
> > > +1
> > >
> > >
> > > >
> > > > On 2023/02/10 02:31:56 Eason Chen wrote:
> > > > > Dear Apache Incubator Community and IPMC members,
> > > > >
> > > > > After having the graduation discussion in the EventMesh community
> > [1],
> > > > > we passed the vote within the EventMesh community [2] and the vote
> > > > > result was published[3].
> > > > > We then discussed the graduation for EventMesh in the Apache
> > Incubator
> > > > > Community [4], where no issues were raised and positive replies
> were
> > > > > received.
> > > > >
> > > > > I would like to start this voting thread to request graduating
> Apache
> > > > > EventMesh(incubating) from Apache Incubator as a Top Level Project.
> > > > >
> > > > > Please provide your vote accordingly:
> > > > > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > > > > Apache Incubator.
> > > > > [ ] +0 No opinion.
> > > > > [ ] -1 No, the EventMesh project is not ready to graduate,
> because...
> > > > >
> > > > > Thank you for participating in the vote. This vote will stay open
> for
> > > > > at least 72 hours.
> > > > >
> > > > > Here is an overview of the Apache EventMesh(incubating) to help
> with
> > > the
> > > > vote.
> > > > >
> > > > > *Community*
> > > > >
> > > > > ● 5 new PPMC members were added, bringing the total number of PPMC
> > > > > members to 14 from at least 9 different organizations.
> > > > > ● 20 new Committers were added, bringing the total number of
> > > > > committers to 42 from at least 30 different organizations.
> > > > > ● 220+ new contributors participate in the community. The number of
> > > > > contributors is now 250+ and growing.
> > > > > ● 20 Bi-weekly online meetings were held among the committers,
> > > > > contributors, and users. The meeting minutes are recorded on the
> > > > > mailing list[5] and cwiki [6].
> > > > > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > > > > ● We've confirmed the VP, PMC, and Committers in the preparation
> > > > > discussion at private@eventmesh [7]. Eason
> > > > > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> > > > >
> > > > > *Project*
> > > > >
> > > > > ● Apache EventMesh(incubating) builds a fully serverless platform
> for
> > > > > distributed event-driven applications.
> > > > > ● Project maturity model is detailed in [8].
> > > > > ● EventMesh has been incubating [9] since 2021-02-18 for over 23
> > > months.
> > > > > ● EventMesh community released a total of 7 Apache releases [10]
> by 6
> > > > > different release managers from 5 different organizations.
> > > > > ● 1300+ issues created, and 1100+ issues closed [11].
> > > > > ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > > > > 2500+ commits added.
> > > > > ● The release cadence is about 3 months, with an average of 180+
> > > > > issues and 230+ pull requests per release.
> > > > > ● Please refer to the EventMesh project incubation status [13][14]
> > for
> > > > > more information.
> > > > >
> > > > > *Brands, License, and Copyright*
> > > > >
> > > > > ● We applied the brand [15], which has been reviewed and approved.
> > > > > ● EventMesh community maintains project code on GitHub and all
> > modules
> > > > > code is under Apache 2.0 license. We have reviewed all the
> > > > > dependencies and ensured they do not bring any license issues [16].
> > > > > All the status files, license headers, and copyright are up to
> date.
> > > > > ● EventMesh official website [17] is compliant with Apache
> Foundation
> > > > > requirements[18].
> > > > >
> > > > > -
> > > > > BEGINNING OF DRAFT RESOLUTION
> > > > > -
> > > > >
> > > > > Establish the Apache EventMesh Project
> > > > >
> > > > > WHEREAS, the Board of Directors deems it to be in the best
> interests
> > of
> > > > > the Foundation and consistent with the Foundation's purpose to
> > > establish
> > > > > a Project Management Committee charged with the creation and
> > > maintenance
> > > > > of open-source software, for distribution at no charge to the
> public,
> > > > > related to a fully serverless platform used to build distributed
> > > > > event-driven applications.
> > > > >
> > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > > (PMC), to be known as the "Apache EventMesh Project", be and hereby
> > is
> > > > > established pursuant to Bylaws of the Foundation; and be it further
> > > > >
> > > > > RESOLVED, that the Apache EventMesh Project be and hereby is
> > > responsible
> > > > > for the creation and maintenance of software related to a fully
> > > > > serverless platform used to build distributed event-driven
> > > applications;
>

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

2023-02-12 Thread Qingrong wang

+1 (non-binding):
I checked:
1. All download links are valid
2.The source and distribution packages already exist
3. Checksum and signature are OK
4. LICENSE and NOTICE are exist and NOTICE  file year is ok
5. Build successfully on ubuntu22.04

Huajie Wang  于2023年2月10日周五 17:46写道：
>
> Hello Incubator Community:
>
> This is a call for a vote to release Apache StreamPark(Incubating)
> version 2.0.0-RC6
>
> The Apache StreamPark community has voted on and approved a proposal to
> release
> Apache StreamPark(Incubating) version 2.0.0-RC6
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache StreamPark, Make stream processing easier! easy-to-use streaming
> application development framework and operation platform.
>
>
> StreamPark community vote thread:
> https://lists.apache.org/thread/lvpc2hywbkdlvkpmjm0knchyk6vhvmnl
>
> Vote result thread:
> https://lists.apache.org/thread/y77vc8c3d5x7wtslm99jydgwmp10ypxv
>
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC6/
>
> Git tag for the release:
> https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc6
>
> Release notes:
> https://streampark.apache.org/download/release-note/2.0.0/
>
> Maven artifacts are available in a staging repository at:
> https://repository.apache.org/content/repositories/orgapachestreampark-1009/
>
> The artifacts signed with PGP key [5AE01B8E], corresponding to [
> benj...@apache.org], that can be found in keys file:
> https://downloads.apache.org/incubator/streampark/KEYS
>
>
> Last commit hash:
> •apache-streampark-2.0.0-incubating-src.tar.gz:
> 91083d97727e302997ae35e54e583340101d2e88968495b78fae16c32a0bd47dc0b87aa285f2a6279758906b811ca6665fb2b0120ebbb6d8d41a4da1263bca23
>
>
> • apache-streampark_2.11-2.0.0-incubating-bin.tar.gz:
> e055643a1657cd4f4dd1352d22bdafd9b3dd2cece5698f503e2a46bd8c1ad6d1a559e2c1041b528b65701f268ba0ae2aefc9072c9a1b0c783fc45c91ec2e88f9
>
>
> • apache-streampark_2.12-2.0.0-incubating-bin.tar.gz:
> 0fbccc5f3fec8c997fea61d60a399f69ab60abfa21e00a07d7bfce92773ef1a19780c3d639e8411b0ac8891f388ed62ff9b437bfec6c7bfcea3f5debbc98be88
>
> In this vote we fixed RC4,RC5 vote process issue, and some licenses issues
> mentioned in RC3 vote process:
> https://github.com/apache/incubator-streampark/pull/2277
>
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> More detailed checklist please refer:
> •
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Steps to validate the release， Please refer to:
> • https://www.apache.org/info/verification.html
> • https://streampark.apache.org/community/release/how-to-verify
>
>
> How to Build:
>
> 1) clone source code:
> > git clone -b v2.0.0-rc6 g...@github.com:apache/incubator-streampark.git
>
> 2) build project:
> > cd incubator-streampark && sh ./build.sh
>
>
> Thanks,
>
> On behalf of Apache StreamPark(Incubating) community
>
>
> Best,
> Huajie Wang

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread Jerry Tan

+1.
Good luck and best regards.

On Mon, Feb 13, 2023 at 10:28 AM xiong mengfei  wrote:

> +1
>
> On Mon, Feb 13, 2023 at 10:22 AM sanchen  wrote:
>
> > +1
> >
> >
> > >
> > > On 2023/02/10 02:31:56 Eason Chen wrote:
> > > > Dear Apache Incubator Community and IPMC members,
> > > >
> > > > After having the graduation discussion in the EventMesh community
> [1],
> > > > we passed the vote within the EventMesh community [2] and the vote
> > > > result was published[3].
> > > > We then discussed the graduation for EventMesh in the Apache
> Incubator
> > > > Community [4], where no issues were raised and positive replies were
> > > > received.
> > > >
> > > > I would like to start this voting thread to request graduating Apache
> > > > EventMesh(incubating) from Apache Incubator as a Top Level Project.
> > > >
> > > > Please provide your vote accordingly:
> > > > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > > > Apache Incubator.
> > > > [ ] +0 No opinion.
> > > > [ ] -1 No, the EventMesh project is not ready to graduate, because...
> > > >
> > > > Thank you for participating in the vote. This vote will stay open for
> > > > at least 72 hours.
> > > >
> > > > Here is an overview of the Apache EventMesh(incubating) to help with
> > the
> > > vote.
> > > >
> > > > *Community*
> > > >
> > > > ● 5 new PPMC members were added, bringing the total number of PPMC
> > > > members to 14 from at least 9 different organizations.
> > > > ● 20 new Committers were added, bringing the total number of
> > > > committers to 42 from at least 30 different organizations.
> > > > ● 220+ new contributors participate in the community. The number of
> > > > contributors is now 250+ and growing.
> > > > ● 20 Bi-weekly online meetings were held among the committers,
> > > > contributors, and users. The meeting minutes are recorded on the
> > > > mailing list[5] and cwiki [6].
> > > > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > > > ● We've confirmed the VP, PMC, and Committers in the preparation
> > > > discussion at private@eventmesh [7]. Eason
> > > > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> > > >
> > > > *Project*
> > > >
> > > > ● Apache EventMesh(incubating) builds a fully serverless platform for
> > > > distributed event-driven applications.
> > > > ● Project maturity model is detailed in [8].
> > > > ● EventMesh has been incubating [9] since 2021-02-18 for over 23
> > months.
> > > > ● EventMesh community released a total of 7 Apache releases [10] by 6
> > > > different release managers from 5 different organizations.
> > > > ● 1300+ issues created, and 1100+ issues closed [11].
> > > > ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > > > 2500+ commits added.
> > > > ● The release cadence is about 3 months, with an average of 180+
> > > > issues and 230+ pull requests per release.
> > > > ● Please refer to the EventMesh project incubation status [13][14]
> for
> > > > more information.
> > > >
> > > > *Brands, License, and Copyright*
> > > >
> > > > ● We applied the brand [15], which has been reviewed and approved.
> > > > ● EventMesh community maintains project code on GitHub and all
> modules
> > > > code is under Apache 2.0 license. We have reviewed all the
> > > > dependencies and ensured they do not bring any license issues [16].
> > > > All the status files, license headers, and copyright are up to date.
> > > > ● EventMesh official website [17] is compliant with Apache Foundation
> > > > requirements[18].
> > > >
> > > > -
> > > > BEGINNING OF DRAFT RESOLUTION
> > > > -
> > > >
> > > > Establish the Apache EventMesh Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best interests
> of
> > > > the Foundation and consistent with the Foundation's purpose to
> > establish
> > > > a Project Management Committee charged with the creation and
> > maintenance
> > > > of open-source software, for distribution at no charge to the public,
> > > > related to a fully serverless platform used to build distributed
> > > > event-driven applications.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > (PMC), to be known as the "Apache EventMesh Project", be and hereby
> is
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache EventMesh Project be and hereby is
> > responsible
> > > > for the creation and maintenance of software related to a fully
> > > > serverless platform used to build distributed event-driven
> > applications;
> > > > and be it further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache EventMesh" be
> and
> > > > hereby is created, the person holding such office to serve at the
> > > > direction of the Board of Directors as the chair of the Apache
> > EventMesh
> > > >

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

2023-02-12 Thread hulk

+1 (non-binding)

I checked:
[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
[x] No unexpected binary files
[x] All source files have ASF headers
[x] Can compile from source
[x] All Tests Passed
[x] Docker image with right version
[x] Docker image contains license files
[x] Docker image can work well



On Mon, 13 Feb 2023 at 10:30, Xiaoqiao He  wrote:
>
> +1 (binding).
>
> - Download links are valid.
> - Checksums and signatures are valid.
> - LICENSE, NOTICE and DISCLAIMER files exist.
> - All source files have apache license declare if necessary.
> - Compile from source passed.
> - No compiled archives bundled in the source archive.
> - Run successfully simple commands about put,get etc.
>
> Best Regards,
> - He Xiaoqiao
>
>
> On Sun, Feb 12, 2023 at 7:24 PM tison  wrote:
>
> > +1 (binding)
> >
> > Verified:
> >
> > - [X] Download links are valid.
> > - [X] Checksums and PGP signatures are valid.
> > - [X] Source code artifacts have correct names matching the current
> > release.
> > - [X] LICENSE, NOTICE and DISCLAIMER are correct for the repository.
> > - [X] All files have license headers if necessary.
> > - [X] No compiled archives bundled in the source archive.
> > - [X] Building is OK with: ./x.py build --ninja --ghproxy
> > - [X] Stage docker image runs and serves properly
> >
> > Best,
> > tison.
> >
> >
> > Chao Zhang  于2023年2月12日周日 18:33写道：
> >
> > > Hi,
> > >
> > > +1 (non-binding) from me. I have checked:
> > >
> > > 1. All the above links are correct;
> > > 2. The signature and checksum are correct;
> > > 3. LICENSE and NOTICE files exist;
> > >
> > > Best regards
> > > Chao Zhang
> > >
> > > https://github.com/tokers
> > >
> > > On Sat, Feb 11, 2023 at 10:44 PM Myth  wrote:
> > > >
> > > > Hello Incubator PMC,
> > > >
> > > > The Apache Kvrocks community has voted and approved the release of
> > Apache
> > > > Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members
> > review
> > > > and vote for this release.
> > > >
> > > > This is  the second call for a vote. The first call for a vote, which
> > is
> > > > cancelled:
> > > > *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt
> > > > *
> > > >
> > > > Kvrocks is a distributed key value NoSQL database that uses RocksDB as
> > > the
> > > > storage engine and is compatible with Redis protocol. The current
> > release
> > > > provides many new features, many improvements and fixes many bugs.
> > > >
> > > > Kvrocks community vote thread:
> > > > https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2
> > > >
> > > > Vote result thread:
> > > > https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw
> > > >
> > > > The release candidate:
> > > > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/
> > > >
> > > > This release has been signed with a PGP available here:
> > > > https://downloads.apache.org/incubator/kvrocks/KEYS
> > > >
> > > > Git tag for the release:
> > > > https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0
> > > >
> > > > Docker image:
> > > >
> > >
> > https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807
> > > >
> > > > Build guide can be found at:
> > > > https://github.com/apache/incubator-kvrocks#build
> > > >
> > > > The vote will be open for at least 72 hours or until the necessary
> > number
> > > > of votes is reached.
> > > >
> > > > Please vote accordingly:
> > > > [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.3.0
> > > > [ ] +0
> > > > [ ] -1 Do not approve (please specify the reason)
> > > >
> > > > Thanks
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >



--
Best Regards,
- Hulk Lin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

2023-02-12 Thread Xiaoqiao He

+1 (binding).

- Download links are valid.
- Checksums and signatures are valid.
- LICENSE, NOTICE and DISCLAIMER files exist.
- All source files have apache license declare if necessary.
- Compile from source passed.
- No compiled archives bundled in the source archive.
- Run successfully simple commands about put,get etc.

Best Regards,
- He Xiaoqiao


On Sun, Feb 12, 2023 at 7:24 PM tison  wrote:

> +1 (binding)
>
> Verified:
>
> - [X] Download links are valid.
> - [X] Checksums and PGP signatures are valid.
> - [X] Source code artifacts have correct names matching the current
> release.
> - [X] LICENSE, NOTICE and DISCLAIMER are correct for the repository.
> - [X] All files have license headers if necessary.
> - [X] No compiled archives bundled in the source archive.
> - [X] Building is OK with: ./x.py build --ninja --ghproxy
> - [X] Stage docker image runs and serves properly
>
> Best,
> tison.
>
>
> Chao Zhang  于2023年2月12日周日 18:33写道：
>
> > Hi,
> >
> > +1 (non-binding) from me. I have checked:
> >
> > 1. All the above links are correct;
> > 2. The signature and checksum are correct;
> > 3. LICENSE and NOTICE files exist;
> >
> > Best regards
> > Chao Zhang
> >
> > https://github.com/tokers
> >
> > On Sat, Feb 11, 2023 at 10:44 PM Myth  wrote:
> > >
> > > Hello Incubator PMC,
> > >
> > > The Apache Kvrocks community has voted and approved the release of
> Apache
> > > Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members
> review
> > > and vote for this release.
> > >
> > > This is  the second call for a vote. The first call for a vote, which
> is
> > > cancelled:
> > > *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt
> > > *
> > >
> > > Kvrocks is a distributed key value NoSQL database that uses RocksDB as
> > the
> > > storage engine and is compatible with Redis protocol. The current
> release
> > > provides many new features, many improvements and fixes many bugs.
> > >
> > > Kvrocks community vote thread:
> > > https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2
> > >
> > > Vote result thread:
> > > https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw
> > >
> > > The release candidate:
> > > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/
> > >
> > > This release has been signed with a PGP available here:
> > > https://downloads.apache.org/incubator/kvrocks/KEYS
> > >
> > > Git tag for the release:
> > > https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0
> > >
> > > Docker image:
> > >
> >
> https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807
> > >
> > > Build guide can be found at:
> > > https://github.com/apache/incubator-kvrocks#build
> > >
> > > The vote will be open for at least 72 hours or until the necessary
> number
> > > of votes is reached.
> > >
> > > Please vote accordingly:
> > > [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.3.0
> > > [ ] +0
> > > [ ] -1 Do not approve (please specify the reason)
> > >
> > > Thanks
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread xiong mengfei

+1

On Mon, Feb 13, 2023 at 10:22 AM sanchen  wrote:

> +1
>
>
> >
> > On 2023/02/10 02:31:56 Eason Chen wrote:
> > > Dear Apache Incubator Community and IPMC members,
> > >
> > > After having the graduation discussion in the EventMesh community [1],
> > > we passed the vote within the EventMesh community [2] and the vote
> > > result was published[3].
> > > We then discussed the graduation for EventMesh in the Apache Incubator
> > > Community [4], where no issues were raised and positive replies were
> > > received.
> > >
> > > I would like to start this voting thread to request graduating Apache
> > > EventMesh(incubating) from Apache Incubator as a Top Level Project.
> > >
> > > Please provide your vote accordingly:
> > > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > > Apache Incubator.
> > > [ ] +0 No opinion.
> > > [ ] -1 No, the EventMesh project is not ready to graduate, because...
> > >
> > > Thank you for participating in the vote. This vote will stay open for
> > > at least 72 hours.
> > >
> > > Here is an overview of the Apache EventMesh(incubating) to help with
> the
> > vote.
> > >
> > > *Community*
> > >
> > > ● 5 new PPMC members were added, bringing the total number of PPMC
> > > members to 14 from at least 9 different organizations.
> > > ● 20 new Committers were added, bringing the total number of
> > > committers to 42 from at least 30 different organizations.
> > > ● 220+ new contributors participate in the community. The number of
> > > contributors is now 250+ and growing.
> > > ● 20 Bi-weekly online meetings were held among the committers,
> > > contributors, and users. The meeting minutes are recorded on the
> > > mailing list[5] and cwiki [6].
> > > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > > ● We've confirmed the VP, PMC, and Committers in the preparation
> > > discussion at private@eventmesh [7]. Eason
> > > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> > >
> > > *Project*
> > >
> > > ● Apache EventMesh(incubating) builds a fully serverless platform for
> > > distributed event-driven applications.
> > > ● Project maturity model is detailed in [8].
> > > ● EventMesh has been incubating [9] since 2021-02-18 for over 23
> months.
> > > ● EventMesh community released a total of 7 Apache releases [10] by 6
> > > different release managers from 5 different organizations.
> > > ● 1300+ issues created, and 1100+ issues closed [11].
> > > ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > > 2500+ commits added.
> > > ● The release cadence is about 3 months, with an average of 180+
> > > issues and 230+ pull requests per release.
> > > ● Please refer to the EventMesh project incubation status [13][14] for
> > > more information.
> > >
> > > *Brands, License, and Copyright*
> > >
> > > ● We applied the brand [15], which has been reviewed and approved.
> > > ● EventMesh community maintains project code on GitHub and all modules
> > > code is under Apache 2.0 license. We have reviewed all the
> > > dependencies and ensured they do not bring any license issues [16].
> > > All the status files, license headers, and copyright are up to date.
> > > ● EventMesh official website [17] is compliant with Apache Foundation
> > > requirements[18].
> > >
> > > -
> > > BEGINNING OF DRAFT RESOLUTION
> > > -
> > >
> > > Establish the Apache EventMesh Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > the Foundation and consistent with the Foundation's purpose to
> establish
> > > a Project Management Committee charged with the creation and
> maintenance
> > > of open-source software, for distribution at no charge to the public,
> > > related to a fully serverless platform used to build distributed
> > > event-driven applications.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache EventMesh Project be and hereby is
> responsible
> > > for the creation and maintenance of software related to a fully
> > > serverless platform used to build distributed event-driven
> applications;
> > > and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> > > hereby is created, the person holding such office to serve at the
> > > direction of the Board of Directors as the chair of the Apache
> EventMesh
> > > Project, and to have primary responsibility for management of the
> > > projects within the scope of responsibility of the Apache EventMesh
> > > Project; and be it further
> > >
> > > RESOLVED, that the persons listed immediately below be and hereby are
> > > appointed to serve as the initial members of the Apache

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread bingyan

+1

Eason Chen  于2023年2月10日周五 10:32写道：

> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
>
> Here is an overview of the Apache EventMesh(incubating) to help with the
> vote.
>
> *Community*
>
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
>
> *Project*
>
> ● Apache EventMesh(incubating) builds a fully serverless platform for
> distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
>
> *Brands, License, and Copyright*
>
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache EventMesh Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a fully serverless platform used to build distributed
> event-driven applications.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to a fully
> serverless platform used to build distributed event-driven applications;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache EventMesh
> Project:
>
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   
>  * Wenjun Ruan  
>  * XiaoShuang Li
>  * Xue Weiming  
>  * Yuwei Zhu
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eason Chen be appointed to

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread sanchen

+1


>
> On 2023/02/10 02:31:56 Eason Chen wrote:
> > Dear Apache Incubator Community and IPMC members,
> >
> > After having the graduation discussion in the EventMesh community [1],
> > we passed the vote within the EventMesh community [2] and the vote
> > result was published[3].
> > We then discussed the graduation for EventMesh in the Apache Incubator
> > Community [4], where no issues were raised and positive replies were
> > received.
> >
> > I would like to start this voting thread to request graduating Apache
> > EventMesh(incubating) from Apache Incubator as a Top Level Project.
> >
> > Please provide your vote accordingly:
> > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > Apache Incubator.
> > [ ] +0 No opinion.
> > [ ] -1 No, the EventMesh project is not ready to graduate, because...
> >
> > Thank you for participating in the vote. This vote will stay open for
> > at least 72 hours.
> >
> > Here is an overview of the Apache EventMesh(incubating) to help with the
> vote.
> >
> > *Community*
> >
> > ● 5 new PPMC members were added, bringing the total number of PPMC
> > members to 14 from at least 9 different organizations.
> > ● 20 new Committers were added, bringing the total number of
> > committers to 42 from at least 30 different organizations.
> > ● 220+ new contributors participate in the community. The number of
> > contributors is now 250+ and growing.
> > ● 20 Bi-weekly online meetings were held among the committers,
> > contributors, and users. The meeting minutes are recorded on the
> > mailing list[5] and cwiki [6].
> > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > ● We've confirmed the VP, PMC, and Committers in the preparation
> > discussion at private@eventmesh [7]. Eason
> > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> >
> > *Project*
> >
> > ● Apache EventMesh(incubating) builds a fully serverless platform for
> > distributed event-driven applications.
> > ● Project maturity model is detailed in [8].
> > ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> > ● EventMesh community released a total of 7 Apache releases [10] by 6
> > different release managers from 5 different organizations.
> > ● 1300+ issues created, and 1100+ issues closed [11].
> > ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > 2500+ commits added.
> > ● The release cadence is about 3 months, with an average of 180+
> > issues and 230+ pull requests per release.
> > ● Please refer to the EventMesh project incubation status [13][14] for
> > more information.
> >
> > *Brands, License, and Copyright*
> >
> > ● We applied the brand [15], which has been reviewed and approved.
> > ● EventMesh community maintains project code on GitHub and all modules
> > code is under Apache 2.0 license. We have reviewed all the
> > dependencies and ensured they do not bring any license issues [16].
> > All the status files, license headers, and copyright are up to date.
> > ● EventMesh official website [17] is compliant with Apache Foundation
> > requirements[18].
> >
> > -
> > BEGINNING OF DRAFT RESOLUTION
> > -
> >
> > Establish the Apache EventMesh Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to a fully serverless platform used to build distributed
> > event-driven applications.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> > for the creation and maintenance of software related to a fully
> > serverless platform used to build distributed event-driven applications;
> > and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache EventMesh
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache EventMesh
> > Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache EventMesh
> > Project:
> >
> >  * Alex Luo 
> >  * Du Heng  
> >  * Eason Chen   
> >  * Francois Papon   
> >  * Jean-Baptiste Onofré 
> >  * Junping Du   
> >  * Justin Mclean
> >  * ShannonDing  
> >  * Von

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread Huimin Li

+1


On 2023/02/10 02:31:56 Eason Chen wrote:
> Dear Apache Incubator Community and IPMC members,
> 
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
> 
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
> 
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
> 
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
> 
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
> 
> *Community*
> 
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
> 
> *Project*
> 
> ● Apache EventMesh(incubating) builds a fully serverless platform for
> distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
> 
> *Brands, License, and Copyright*
> 
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
> 
> -
> BEGINNING OF DRAFT RESOLUTION
> -
> 
> Establish the Apache EventMesh Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a fully serverless platform used to build distributed
> event-driven applications.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to a fully
> serverless platform used to build distributed event-driven applications;
> and be it further
> 
> RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache EventMesh
> Project:
> 
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   
>  * Wenjun Ruan  
>  * XiaoShuang Li
>  * Xue Weiming  
>  * Yuwei Zhu
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread Huajie Wang

+1, congratulations.



Best,
Huajie Wang



wenjun  于2023年2月13日周一 10:04写道：

> +1 (non-binding)
>
> Great to join EventMesh community.
>
>
>
> On Mon, Feb 13, 2023 at 9:59 AM ShannonDing  wrote:
>
> > +1
> >
> > At 2023-02-10 10:31:56, "Eason Chen"  wrote:
> > >Dear Apache Incubator Community and IPMC members,
> > >
> > >After having the graduation discussion in the EventMesh community [1],
> > >we passed the vote within the EventMesh community [2] and the vote
> > >result was published[3].
> > >We then discussed the graduation for EventMesh in the Apache Incubator
> > >Community [4], where no issues were raised and positive replies were
> > >received.
> > >
> > >I would like to start this voting thread to request graduating Apache
> > >EventMesh(incubating) from Apache Incubator as a Top Level Project.
> > >
> > >Please provide your vote accordingly:
> > >[ ] +1 Yes, I support the EventMesh project to graduate from the
> > >Apache Incubator.
> > >[ ] +0 No opinion.
> > >[ ] -1 No, the EventMesh project is not ready to graduate, because...
> > >
> > >Thank you for participating in the vote. This vote will stay open for
> > >at least 72 hours.
> > >
> > >Here is an overview of the Apache EventMesh(incubating) to help with the
> > vote.
> > >
> > >*Community*
> > >
> > >● 5 new PPMC members were added, bringing the total number of PPMC
> > >members to 14 from at least 9 different organizations.
> > >● 20 new Committers were added, bringing the total number of
> > >committers to 42 from at least 30 different organizations.
> > >● 220+ new contributors participate in the community. The number of
> > >contributors is now 250+ and growing.
> > >● 20 Bi-weekly online meetings were held among the committers,
> > >contributors, and users. The meeting minutes are recorded on the
> > >mailing list[5] and cwiki [6].
> > >● The dev@eventmesh mailing list currently has 117 subscribers.
> > >● We've confirmed the VP, PMC, and Committers in the preparation
> > >discussion at private@eventmesh [7]. Eason
> > >Chen(chenguangsh...@apache.org) was recommended as Vice President.
> > >
> > >*Project*
> > >
> > >● Apache EventMesh(incubating) builds a fully serverless platform for
> > >distributed event-driven applications.
> > >● Project maturity model is detailed in [8].
> > >● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> > >● EventMesh community released a total of 7 Apache releases [10] by 6
> > >different release managers from 5 different organizations.
> > >● 1300+ issues created, and 1100+ issues closed [11].
> > >● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > >2500+ commits added.
> > >● The release cadence is about 3 months, with an average of 180+
> > >issues and 230+ pull requests per release.
> > >● Please refer to the EventMesh project incubation status [13][14] for
> > >more information.
> > >
> > >*Brands, License, and Copyright*
> > >
> > >● We applied the brand [15], which has been reviewed and approved.
> > >● EventMesh community maintains project code on GitHub and all modules
> > >code is under Apache 2.0 license. We have reviewed all the
> > >dependencies and ensured they do not bring any license issues [16].
> > >All the status files, license headers, and copyright are up to date.
> > >● EventMesh official website [17] is compliant with Apache Foundation
> > >requirements[18].
> > >
> > >-
> > >BEGINNING OF DRAFT RESOLUTION
> > >-
> > >
> > >Establish the Apache EventMesh Project
> > >
> > >WHEREAS, the Board of Directors deems it to be in the best interests of
> > >the Foundation and consistent with the Foundation's purpose to establish
> > >a Project Management Committee charged with the creation and maintenance
> > >of open-source software, for distribution at no charge to the public,
> > >related to a fully serverless platform used to build distributed
> > >event-driven applications.
> > >
> > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > >(PMC), to be known as the "Apache EventMesh Project", be and hereby is
> > >established pursuant to Bylaws of the Foundation; and be it further
> > >
> > >RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> > >for the creation and maintenance of software related to a fully
> > >serverless platform used to build distributed event-driven applications;
> > >and be it further
> > >
> > >RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> > >hereby is created, the person holding such office to serve at the
> > >direction of the Board of Directors as the chair of the Apache EventMesh
> > >Project, and to have primary responsibility for management of the
> > >projects within the scope of responsibility of the Apache EventMesh
> > >Project; and be it further
> > >
> > >RESOLVED, that the persons listed immediately below be and hereby are
> >

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread Zhang Yonglun

+1 (non-binding)

--

Zhang Yonglun
Apache ShenYu & ShardingSphere

Eason Chen  于2023年2月10日周五 10:32写道：
>
> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
>
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
>
> *Community*
>
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
>
> *Project*
>
> ● Apache EventMesh(incubating) builds a fully serverless platform for
> distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
>
> *Brands, License, and Copyright*
>
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache EventMesh Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a fully serverless platform used to build distributed
> event-driven applications.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to a fully
> serverless platform used to build distributed event-driven applications;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache EventMesh
> Project:
>
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   
>  * Wenjun Ruan  
>  * XiaoShuang Li
>  * Xue Weiming  
>  * Yuwei Zhu
>
> NOW,

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread wenjun

+1 (non-binding)

Great to join EventMesh community.



On Mon, Feb 13, 2023 at 9:59 AM ShannonDing  wrote:

> +1
>
> At 2023-02-10 10:31:56, "Eason Chen"  wrote:
> >Dear Apache Incubator Community and IPMC members,
> >
> >After having the graduation discussion in the EventMesh community [1],
> >we passed the vote within the EventMesh community [2] and the vote
> >result was published[3].
> >We then discussed the graduation for EventMesh in the Apache Incubator
> >Community [4], where no issues were raised and positive replies were
> >received.
> >
> >I would like to start this voting thread to request graduating Apache
> >EventMesh(incubating) from Apache Incubator as a Top Level Project.
> >
> >Please provide your vote accordingly:
> >[ ] +1 Yes, I support the EventMesh project to graduate from the
> >Apache Incubator.
> >[ ] +0 No opinion.
> >[ ] -1 No, the EventMesh project is not ready to graduate, because...
> >
> >Thank you for participating in the vote. This vote will stay open for
> >at least 72 hours.
> >
> >Here is an overview of the Apache EventMesh(incubating) to help with the
> vote.
> >
> >*Community*
> >
> >● 5 new PPMC members were added, bringing the total number of PPMC
> >members to 14 from at least 9 different organizations.
> >● 20 new Committers were added, bringing the total number of
> >committers to 42 from at least 30 different organizations.
> >● 220+ new contributors participate in the community. The number of
> >contributors is now 250+ and growing.
> >● 20 Bi-weekly online meetings were held among the committers,
> >contributors, and users. The meeting minutes are recorded on the
> >mailing list[5] and cwiki [6].
> >● The dev@eventmesh mailing list currently has 117 subscribers.
> >● We've confirmed the VP, PMC, and Committers in the preparation
> >discussion at private@eventmesh [7]. Eason
> >Chen(chenguangsh...@apache.org) was recommended as Vice President.
> >
> >*Project*
> >
> >● Apache EventMesh(incubating) builds a fully serverless platform for
> >distributed event-driven applications.
> >● Project maturity model is detailed in [8].
> >● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> >● EventMesh community released a total of 7 Apache releases [10] by 6
> >different release managers from 5 different organizations.
> >● 1300+ issues created, and 1100+ issues closed [11].
> >● 1600+ pull requests created, and 1600+ pull requests closed [12],
> >2500+ commits added.
> >● The release cadence is about 3 months, with an average of 180+
> >issues and 230+ pull requests per release.
> >● Please refer to the EventMesh project incubation status [13][14] for
> >more information.
> >
> >*Brands, License, and Copyright*
> >
> >● We applied the brand [15], which has been reviewed and approved.
> >● EventMesh community maintains project code on GitHub and all modules
> >code is under Apache 2.0 license. We have reviewed all the
> >dependencies and ensured they do not bring any license issues [16].
> >All the status files, license headers, and copyright are up to date.
> >● EventMesh official website [17] is compliant with Apache Foundation
> >requirements[18].
> >
> >-
> >BEGINNING OF DRAFT RESOLUTION
> >-
> >
> >Establish the Apache EventMesh Project
> >
> >WHEREAS, the Board of Directors deems it to be in the best interests of
> >the Foundation and consistent with the Foundation's purpose to establish
> >a Project Management Committee charged with the creation and maintenance
> >of open-source software, for distribution at no charge to the public,
> >related to a fully serverless platform used to build distributed
> >event-driven applications.
> >
> >NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >(PMC), to be known as the "Apache EventMesh Project", be and hereby is
> >established pursuant to Bylaws of the Foundation; and be it further
> >
> >RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> >for the creation and maintenance of software related to a fully
> >serverless platform used to build distributed event-driven applications;
> >and be it further
> >
> >RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> >hereby is created, the person holding such office to serve at the
> >direction of the Board of Directors as the chair of the Apache EventMesh
> >Project, and to have primary responsibility for management of the
> >projects within the scope of responsibility of the Apache EventMesh
> >Project; and be it further
> >
> >RESOLVED, that the persons listed immediately below be and hereby are
> >appointed to serve as the initial members of the Apache EventMesh
> >Project:
> >
> > * Alex Luo 
> > * Du Heng  
> > * Eason Chen   
> > * Francois Papon   
> > * Jean-Baptiste Onofré 
> > * Junping Du   
> > * Justin Mclean
> > * ShannonDing

Re:[VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread ShannonDing

+1

At 2023-02-10 10:31:56, "Eason Chen"  wrote:
>Dear Apache Incubator Community and IPMC members,
>
>After having the graduation discussion in the EventMesh community [1],
>we passed the vote within the EventMesh community [2] and the vote
>result was published[3].
>We then discussed the graduation for EventMesh in the Apache Incubator
>Community [4], where no issues were raised and positive replies were
>received.
>
>I would like to start this voting thread to request graduating Apache
>EventMesh(incubating) from Apache Incubator as a Top Level Project.
>
>Please provide your vote accordingly:
>[ ] +1 Yes, I support the EventMesh project to graduate from the
>Apache Incubator.
>[ ] +0 No opinion.
>[ ] -1 No, the EventMesh project is not ready to graduate, because...
>
>Thank you for participating in the vote. This vote will stay open for
>at least 72 hours.
>
>Here is an overview of the Apache EventMesh(incubating) to help with the vote.
>
>*Community*
>
>● 5 new PPMC members were added, bringing the total number of PPMC
>members to 14 from at least 9 different organizations.
>● 20 new Committers were added, bringing the total number of
>committers to 42 from at least 30 different organizations.
>● 220+ new contributors participate in the community. The number of
>contributors is now 250+ and growing.
>● 20 Bi-weekly online meetings were held among the committers,
>contributors, and users. The meeting minutes are recorded on the
>mailing list[5] and cwiki [6].
>● The dev@eventmesh mailing list currently has 117 subscribers.
>● We've confirmed the VP, PMC, and Committers in the preparation
>discussion at private@eventmesh [7]. Eason
>Chen(chenguangsh...@apache.org) was recommended as Vice President.
>
>*Project*
>
>● Apache EventMesh(incubating) builds a fully serverless platform for
>distributed event-driven applications.
>● Project maturity model is detailed in [8].
>● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
>● EventMesh community released a total of 7 Apache releases [10] by 6
>different release managers from 5 different organizations.
>● 1300+ issues created, and 1100+ issues closed [11].
>● 1600+ pull requests created, and 1600+ pull requests closed [12],
>2500+ commits added.
>● The release cadence is about 3 months, with an average of 180+
>issues and 230+ pull requests per release.
>● Please refer to the EventMesh project incubation status [13][14] for
>more information.
>
>*Brands, License, and Copyright*
>
>● We applied the brand [15], which has been reviewed and approved.
>● EventMesh community maintains project code on GitHub and all modules
>code is under Apache 2.0 license. We have reviewed all the
>dependencies and ensured they do not bring any license issues [16].
>All the status files, license headers, and copyright are up to date.
>● EventMesh official website [17] is compliant with Apache Foundation
>requirements[18].
>
>-
>BEGINNING OF DRAFT RESOLUTION
>-
>
>Establish the Apache EventMesh Project
>
>WHEREAS, the Board of Directors deems it to be in the best interests of
>the Foundation and consistent with the Foundation's purpose to establish
>a Project Management Committee charged with the creation and maintenance
>of open-source software, for distribution at no charge to the public,
>related to a fully serverless platform used to build distributed
>event-driven applications.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>(PMC), to be known as the "Apache EventMesh Project", be and hereby is
>established pursuant to Bylaws of the Foundation; and be it further
>
>RESOLVED, that the Apache EventMesh Project be and hereby is responsible
>for the creation and maintenance of software related to a fully
>serverless platform used to build distributed event-driven applications;
>and be it further
>
>RESOLVED, that the office of "Vice President, Apache EventMesh" be and
>hereby is created, the person holding such office to serve at the
>direction of the Board of Directors as the chair of the Apache EventMesh
>Project, and to have primary responsibility for management of the
>projects within the scope of responsibility of the Apache EventMesh
>Project; and be it further
>
>RESOLVED, that the persons listed immediately below be and hereby are
>appointed to serve as the initial members of the Apache EventMesh
>Project:
>
> * Alex Luo 
> * Du Heng  
> * Eason Chen   
> * Francois Papon   
> * Jean-Baptiste Onofré 
> * Junping Du   
> * Justin Mclean
> * ShannonDing  
> * Von Gosling  
> * Weiqiang Liang   
> * Wenjun Ruan  
> * XiaoShuang Li
> * Xue Weiming  
> * Yuwei Zhu
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eason Chen be appointed to
>the office of Vice President, Apache EventMesh, to serve in accordance
>with and

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread Xiaoyang Liu

+1

On 2023/02/10 02:31:56 Eason Chen wrote:
> Dear Apache Incubator Community and IPMC members,
> 
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
> 
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
> 
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
> 
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
> 
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
> 
> *Community*
> 
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
> 
> *Project*
> 
> ● Apache EventMesh(incubating) builds a fully serverless platform for
> distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
> 
> *Brands, License, and Copyright*
> 
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
> 
> -
> BEGINNING OF DRAFT RESOLUTION
> -
> 
> Establish the Apache EventMesh Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a fully serverless platform used to build distributed
> event-driven applications.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to a fully
> serverless platform used to build distributed event-driven applications;
> and be it further
> 
> RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache EventMesh
> Project:
> 
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   
>  * Wenjun Ruan  
>  * XiaoShuang Li
>  * Xue Weiming  
>  * Yuwei Zhu
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread heng du

+1

Willem Jiang  于2023年2月13日周一 08:47写道：

> +1 （binding）
> It's great to see EventMesh in good shape for graduation.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Feb 10, 2023 at 10:32 AM Eason Chen 
> wrote:
> >
> > Dear Apache Incubator Community and IPMC members,
> >
> > After having the graduation discussion in the EventMesh community [1],
> > we passed the vote within the EventMesh community [2] and the vote
> > result was published[3].
> > We then discussed the graduation for EventMesh in the Apache Incubator
> > Community [4], where no issues were raised and positive replies were
> > received.
> >
> > I would like to start this voting thread to request graduating Apache
> > EventMesh(incubating) from Apache Incubator as a Top Level Project.
> >
> > Please provide your vote accordingly:
> > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > Apache Incubator.
> > [ ] +0 No opinion.
> > [ ] -1 No, the EventMesh project is not ready to graduate, because...
> >
> > Thank you for participating in the vote. This vote will stay open for
> > at least 72 hours.
> >
> > Here is an overview of the Apache EventMesh(incubating) to help with the
> vote.
> >
> > *Community*
> >
> > ● 5 new PPMC members were added, bringing the total number of PPMC
> > members to 14 from at least 9 different organizations.
> > ● 20 new Committers were added, bringing the total number of
> > committers to 42 from at least 30 different organizations.
> > ● 220+ new contributors participate in the community. The number of
> > contributors is now 250+ and growing.
> > ● 20 Bi-weekly online meetings were held among the committers,
> > contributors, and users. The meeting minutes are recorded on the
> > mailing list[5] and cwiki [6].
> > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > ● We've confirmed the VP, PMC, and Committers in the preparation
> > discussion at private@eventmesh [7]. Eason
> > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> >
> > *Project*
> >
> > ● Apache EventMesh(incubating) builds a fully serverless platform for
> > distributed event-driven applications.
> > ● Project maturity model is detailed in [8].
> > ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> > ● EventMesh community released a total of 7 Apache releases [10] by 6
> > different release managers from 5 different organizations.
> > ● 1300+ issues created, and 1100+ issues closed [11].
> > ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > 2500+ commits added.
> > ● The release cadence is about 3 months, with an average of 180+
> > issues and 230+ pull requests per release.
> > ● Please refer to the EventMesh project incubation status [13][14] for
> > more information.
> >
> > *Brands, License, and Copyright*
> >
> > ● We applied the brand [15], which has been reviewed and approved.
> > ● EventMesh community maintains project code on GitHub and all modules
> > code is under Apache 2.0 license. We have reviewed all the
> > dependencies and ensured they do not bring any license issues [16].
> > All the status files, license headers, and copyright are up to date.
> > ● EventMesh official website [17] is compliant with Apache Foundation
> > requirements[18].
> >
> > -
> > BEGINNING OF DRAFT RESOLUTION
> > -
> >
> > Establish the Apache EventMesh Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to a fully serverless platform used to build distributed
> > event-driven applications.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> > for the creation and maintenance of software related to a fully
> > serverless platform used to build distributed event-driven applications;
> > and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache EventMesh
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache EventMesh
> > Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache EventMesh
> > Project:
> >
> >  * Alex Luo 
> >  * Du Heng  
>

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

2023-02-12 Thread Willem Jiang

+1 （binding）
It's great to see EventMesh in good shape for graduation.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Feb 10, 2023 at 10:32 AM Eason Chen  wrote:
>
> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
>
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
>
> *Community*
>
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
>
> *Project*
>
> ● Apache EventMesh(incubating) builds a fully serverless platform for
> distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
>
> *Brands, License, and Copyright*
>
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache EventMesh Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a fully serverless platform used to build distributed
> event-driven applications.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to a fully
> serverless platform used to build distributed event-driven applications;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache EventMesh
> Project:
>
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>  * Francois Papon   
>  * Jean-Baptiste Onofré 
>  * Junping Du   
>  * Justin Mclean
>  * ShannonDing  
>  * Von Gosling  
>  * Weiqiang Liang   
>  * Wenjun Ruan  
>  * XiaoShuang Li

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

2023-02-12 Thread tison

+1 (binding)

Verified:

- [X] Download links are valid.
- [X] Checksums and PGP signatures are valid.
- [X] Source code artifacts have correct names matching the current release.
- [X] LICENSE, NOTICE and DISCLAIMER are correct for the repository.
- [X] All files have license headers if necessary.
- [X] No compiled archives bundled in the source archive.
- [X] Building is OK with: ./x.py build --ninja --ghproxy
- [X] Stage docker image runs and serves properly

Best,
tison.


Chao Zhang  于2023年2月12日周日 18:33写道：

> Hi,
>
> +1 (non-binding) from me. I have checked:
>
> 1. All the above links are correct;
> 2. The signature and checksum are correct;
> 3. LICENSE and NOTICE files exist;
>
> Best regards
> Chao Zhang
>
> https://github.com/tokers
>
> On Sat, Feb 11, 2023 at 10:44 PM Myth  wrote:
> >
> > Hello Incubator PMC,
> >
> > The Apache Kvrocks community has voted and approved the release of Apache
> > Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members review
> > and vote for this release.
> >
> > This is  the second call for a vote. The first call for a vote, which is
> > cancelled:
> > *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt
> > *
> >
> > Kvrocks is a distributed key value NoSQL database that uses RocksDB as
> the
> > storage engine and is compatible with Redis protocol. The current release
> > provides many new features, many improvements and fixes many bugs.
> >
> > Kvrocks community vote thread:
> > https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2
> >
> > Vote result thread:
> > https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/
> >
> > This release has been signed with a PGP available here:
> > https://downloads.apache.org/incubator/kvrocks/KEYS
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0
> >
> > Docker image:
> >
> https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807
> >
> > Build guide can be found at:
> > https://github.com/apache/incubator-kvrocks#build
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes is reached.
> >
> > Please vote accordingly:
> > [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.3.0
> > [ ] +0
> > [ ] -1 Do not approve (please specify the reason)
> >
> > Thanks
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

2023-02-12 Thread Chao Zhang

Hi,

+1 (non-binding) from me. I have checked:

1. All the above links are correct;
2. The signature and checksum are correct;
3. LICENSE and NOTICE files exist;

Best regards
Chao Zhang

https://github.com/tokers

On Sat, Feb 11, 2023 at 10:44 PM Myth  wrote:
>
> Hello Incubator PMC,
>
> The Apache Kvrocks community has voted and approved the release of Apache
> Kvrocks(incubating) 2.3.0. We now kindly request the IPMC members review
> and vote for this release.
>
> This is  the second call for a vote. The first call for a vote, which is
> cancelled:
> *https://lists.apache.org/thread/pbfmd81pfqrzjvqzb194o6dxlynt5gwt
> *
>
> Kvrocks is a distributed key value NoSQL database that uses RocksDB as the
> storage engine and is compatible with Redis protocol. The current release
> provides many new features, many improvements and fixes many bugs.
>
> Kvrocks community vote thread:
> https://lists.apache.org/thread/o4rl21ckhmo5d594xvksl4l8djf0ctm2
>
> Vote result thread:
> https://lists.apache.org/thread/o335chgmyfrplcvys3lobtdwdk29kmjw
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.3.0/
>
> This release has been signed with a PGP available here:
> https://downloads.apache.org/incubator/kvrocks/KEYS
>
> Git tag for the release:
> https://github.com/apache/incubator-kvrocks/releases/tag/v2.3.0
>
> Docker image:
> https://hub.docker.com/layers/caipengbo/kvrocks/2.3.0/images/sha256-78f1d29e632e94fc438d71174285e1034418fb06eb8b623a93bc0a15451b6807
>
> Build guide can be found at:
> https://github.com/apache/incubator-kvrocks#build
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.3.0
> [ ] +0
> [ ] -1 Do not approve (please specify the reason)
>
> Thanks

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Celeborn(Incubating) 0.2.0-incubating-rc4

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Release Apache StreamPark(Incubating) 2.0.0-RC6

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re:[VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

Re: [VOTE] Release Apache Kvrocks(incubating) 2.3.0(NEW VOTE)

28 matches

Site Navigation

Mail list logo

Footer information