Re: [DISCUSS] Incubating Proposal of Seata
Hi, I have been following the Seata project for years and have witnessed the project's growth. I am glad to see Seata joining the apache community, and happy to be mentor of the seata project to help seata going through the incubation process. I have a question about the initial comitters. Looking at the developer page[1], not all the seata comitters are listed in the initial comitters. Could you elaborate more about this? [1] https://seata.io/en/docs/developers/developers_dev The On Wed, Oct 11, 2023 at 2:37 PM Sheng Wu wrote: > > Hi Incubator > > I would like to propose a new project to the ASF incubator - Seata. > > Seata[1] is an open-source distributed transaction solution that > delivers high-performance and easy-to-use distributed transaction > services under a microservices architecture. > This project is owned by Alibaba and Ant Group. They have agreed to > sign the SGAs and CCLAs for the donation. > > Here is their proposal, > https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal > > I would be the Champion of the project. I am going to mentor and help > the project go through the incubator with Justin Mclean(justin at > classsoftware dot com), Huxing Zhang(huxing at apache dot org), and > Heng Du(duhengforever at apache dot org). > > So far, the project has a large user group and diverse dev team, it is > healthy and moving forward. > Within the ASF requirements, the MySQL dependency is the major issue > we need to resolve after being accepted due to GPL limitations. The > project community has supported to use other databases such as > PostgreSQL, they just need to remove the MySQL driver from the binary > and keep it optional. > > We are open to hearing the feedback from the incubator. > > [1] https://seata.io/en/ > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Best Regards！ Huxing - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache OpenDAL(incubating) 0.41.0-rc.1 - Incubator Vote Round 1
Carry my non-binding +1 vote from OpenDAL community. On Thu, Oct 12, 2023, at 15:30, Suyan wrote: > Hello Incubator PMC, > > The Apache OpenDAL community has voted and approved the release of Apache > OpenDAL(incubating) 0.41.0-rc.1. We would like to request the IPMC members > to review and vote for this release. > > OpenDAL is a data access layer that allows users to easily and efficiently > retrieve data from various storage services in a unified way. > > OpenDAL community vote thread: > > https://lists.apache.org/thread/zwr6m8qpgj82r7wkxmnovb6yv19hl7ng > > Vote result thread: > > https://lists.apache.org/thread/lm5t2f6v31lp8bmltoppqsxowxvos89x > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.41.0-rc.1/ > > This release has been signed with a PGP available here: > > https://downloads.apache.org/incubator/opendal/KEYS > > Git tag for the release: > > https://github.com/apache/incubator-opendal/releases/tag/v0.41.0-rc.1/ > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapacheopendal-1015/ > > Please download, verify, and test. > > The VOTE will be open for at least 72 hours and until the necessary > number of votes are reached. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > To learn more about Apache OpenDAL(incubating), please see > https://opendal.apache.org/ > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and signatures. > [ ] LICENSE/NOTICE files exist > [ ] No unexpected binary files > [ ] All source files have ASF headers > [ ] Can compile from source > > More detailed checklist please refer to: > https://github.com/apache/incubator-opendal/tree/main/scripts > > To compile from the source, please refer to: > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md > > Here is a Python script in release to help you verify the release candidate: > > ./scripts/verify.py > > Thanks > > Sincerely, > Suyan > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org -- Xuanwo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Release Apache Baremaps 0.7.2-rc3 (incubating)
Yes; unfortunately, the concept of binding votes is one that you need to know. If and when Baremaps has graduated as a top-level project, the votes of Baremaps PMC members will be binding, but for the sake of inclusion and quality you will want as many votes as possible from other community members (including non-PMC committers). Julian > On Oct 12, 2023, at 03:05, Bertil Chapuis wrote: > > Thanks a lot for the clarification, we will eventually get familiar with the > process > >> On 11 Oct 2023, at 21:02, Julian Hyde wrote: >> >> Note that 3 of those +1s (me, Calvin, JB) are binding because they are >> Incubator PMC members, 2 are not (Bertil, Leonard). >> >> 3 binding +1s is sufficient for the vote to pass. >> >> Congratulations! >> >> Julian >> >>> On Tue, Oct 10, 2023 at 12:49 AM Bertil Chapuis wrote: >>> >>> Hello Everyone, >>> >>> The vote for Apache Baremaps 0.7.2-rc3 (incubating) is now closed. The >>> results are summarised below. Thank you all for taking the time to provide >>> valuable feedbacks for this release, we are getting very close from being >>> fully compliant with the guidelines. >>> >>> Binding Votes: >>> >>> +1 votes [5]: >>> - Leonard Cseres >>> - Julian Hyde >>> - Jean-Baptiste Onofré >>> - Calvin Kirs >>> - Bertil Chapuis >>> >>> 0 votes [0]: >>> None >>> >>> -1 votes [0]: >>> None >>> >>> Best regards, >>> >>> Bertil >>> >>> >>> On 7 Oct 2023, at 07:08, Calvin Kirs wrote: +1 （binding） I checked: - incubating in name - signatures and hashes are fine - disclaimer-wip exists - license and notice files look good - file have correct ASF headers if necessary On Thu, Oct 5, 2023 at 7:19 PM Jean-Baptiste Onofré wrote: > > +1 (binding) > > I checked: > - signatures and hashes ok > - asf headers > - license, notice and disclaimer are there > - no binary found in source distribution > > Thanks > Regards > JB > > Le mar. 3 oct. 2023 à 00:10, Bertil Chapuis a écrit : > >> Hello Everyone, >> >> This is a call for a vote to release Apache Baremaps 0.7.2 (incubating), >> release candidate 3. Apache Baremaps is a toolkit and a set of >> infrastructure components for creating, publishing, and operating online >> maps. >> >> We would like to thanks everyone who has vetted the previous release >> candidates and who has contributed to the project. This release candidate >> fixes the issues identified in the previous vote thread: >> https://lists.apache.org/thread/vzvl8rl5h5k9vj3j2xhbkn92zvn4db2f >> >> We now would like to request the Incubator PMC members to review and vote >> on this new release candidate. >> >> You can read the release notes here: >> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.2-rc3 >> >> The commit to be voted upon: >> https://github.com/apache/incubator-baremaps/tree/v0.7.2-rc3 >> >> Its hash is 823b55507eec425776d996b64b489c8235f6bb37. >> >> Its tag is v0.7.2-rc3. >> >> The artifacts to be voted on are located here: >> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.2-rc3/ >> >> The hashes of the artifacts are as follows: >> 658ed9f9d7836c774095bd6079a39c92b366da38d733a04f2334ca39e55d41001ea997c826f9024bae51034ee6861d153ef1948defff8ebf02ce18b79d52319b >> ./apache-baremaps-0.7.2-incubating-src.tar.gz >> 778a4c2e657b5f632f9abe547d68978da40f162bdddc6dc342586b40952b0c72a0c4f6976cc47f720134c7e547af58f1efa39ddb2441e7f57c7a35fee68a1915 >> ./apache-baremaps-0.7.2-incubating-bin.tar.gz >> >> Release artifacts are signed with the following key: >> http://people.apache.org/keys/committer/bchapuis.asc >> https://downloads.apache.org/incubator/baremaps/KEYS >> >> The README file for the src distribution contains instructions for >> building and testing the release. >> >> Please vote on releasing this package as Apache Baremaps 0.7.2. >> >> The vote is open for the next 72 hours and passes if a majority of at >> least three +1 PMC votes are cast. >> >> [ ] +1 Release this package as Apache Baremaps 0.7.2 >> [ ] 0 I don't feel strongly about it, but I'm okay with the release >> [ ] -1 Do not release this package because... >> >> Best, >> >> Bertil >> -- Best wishes！ CalvinKirs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org >> For additional commands, e-mail: dev-h...@baremaps.apache.org >> >
Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.1-incubating-rc3
+1 (binding) I checked - Files have the word incubating in their name. - Checksums and signatures are valid. - DISCLAIMER,LICENSE and NOTICE files exist. - No Unexpected Binary Files in source release. - The LICENSE file looks good to me. Cheng Pan 于2023年10月7日周六 13:29写道： > Hi IPMC, > > This is a call for a vote to release Apache Celeborn (Incubating) > 0.3.1-incubating-rc3 > > The Apache Celeborn community has voted on and approved a proposal to > release Apache Celeborn (Incubating) version 0.3.1-incubating-rc3. > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > dev@celeborn vote thread: > https://lists.apache.org/thread/wt69x5h3jxrmozkjgh2v544sgpdqhnvq > > dev@celeborn vote result thread: > https://lists.apache.org/thread/p6m2ko6lok8wkbbswt1n2qhwm0rh4xf4 > > The git tag to be voted upon: > > https://github.com/apache/incubator-celeborn/releases/tag/v0.3.1-incubating-rc3 > > The git commit hash: > 861788810642ef19769b097b82bee70b92e0ace0 > > The source and binary artifacts can be found at: > > https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.1-incubating-rc3 > > The staging repo: > https://repository.apache.org/content/repositories/orgapacheceleborn-1040 > > Fingerprint of the PGP key release artifacts are signed with: > 8FC8075E1FDC303276C676EE8001952629BCC75D > > My public key to verify signatures can be found in: > https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS > > 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 (and the reason) > > Checklist for release: > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > Steps to validate the release: > https://www.apache.org/info/verification.html > > Instructions for making binary artifacts from source: > build/make-distribution.sh --release > > Thanks, > Cheng Pan > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- -- Best Regards Gang Li 李岗 lgcar...@apache.org
Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.1-incubating-rc3
+1 (nonbinding), I have checked: [✓] The checksums and signatures are validated [✓] The LICENSE and NOTICE are fine [✓] DISCLAIMER is present [✓] No binary files in the source release [✓] incubating in the name [✓] Built from source with make-distribution.sh Kent Yao On 2023/10/12 10:22:46 "张铎(Duo Zhang)" wrote: > +1 binding > > Checked sigs and sums: Matched > LICENSE and NOTICE: OK > DISCLAIMER: In place > Built from source: > ‘./build/make-distribution.sh --release -Pflink-1.17’, successfully > generated the tarball > Run UTs: > './build/mvn test -Pflink-1.17', passed > > Thanks. > > Willem Jiang 于2023年10月12日周四 15:32写道： > > > > +1 binding. > > > > - incubating in the release kit name > > - The checksums and signatures are validated. > > - The LICENSE and NOTICE files look good to me. > > - There is a DISCLAIMER in the release kits > > - No binary files in the source release kits > > - I can build the source with the command > > ./build/make-distribution.sh --release > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > > > > > On Sat, Oct 7, 2023 at 1:29 PM Cheng Pan wrote: > > > > > > Hi IPMC, > > > > > > This is a call for a vote to release Apache Celeborn (Incubating) > > > 0.3.1-incubating-rc3 > > > > > > The Apache Celeborn community has voted on and approved a proposal to > > > release Apache Celeborn (Incubating) version 0.3.1-incubating-rc3. > > > We now kindly request the Incubator PMC members review and vote on this > > > incubator release. > > > > > > dev@celeborn vote thread: > > > https://lists.apache.org/thread/wt69x5h3jxrmozkjgh2v544sgpdqhnvq > > > > > > dev@celeborn vote result thread: > > > https://lists.apache.org/thread/p6m2ko6lok8wkbbswt1n2qhwm0rh4xf4 > > > > > > The git tag to be voted upon: > > > https://github.com/apache/incubator-celeborn/releases/tag/v0.3.1-incubating-rc3 > > > > > > The git commit hash: > > > 861788810642ef19769b097b82bee70b92e0ace0 > > > > > > The source and binary artifacts can be found at: > > > https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.1-incubating-rc3 > > > > > > The staging repo: > > > https://repository.apache.org/content/repositories/orgapacheceleborn-1040 > > > > > > Fingerprint of the PGP key release artifacts are signed with: > > > 8FC8075E1FDC303276C676EE8001952629BCC75D > > > > > > My public key to verify signatures can be found in: > > > https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS > > > > > > 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 (and the reason) > > > > > > Checklist for release: > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > > > Steps to validate the release: > > > https://www.apache.org/info/verification.html > > > > > > Instructions for making binary artifacts from source: > > > build/make-distribution.sh --release > > > > > > Thanks, > > > Cheng Pan > > > > > > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Pekko(incubating) gRPC 1.0.1-RC1
Carrying over +1 vote from https://lists.apache.org/thread/s53trdc7prq3406jx64wo1rq4nbbkv63 On Thu, Oct 12, 2023 at 6:15 AM PJ Fanning wrote: > Hello Incubator Community, > > This is a call for a vote to release Apache Pekko(incubating) > gRPC version 1.0.1-RC1. > > The discussion thread: > https://lists.apache.org/thread/tlmk742qvm0tlfmk3o24cch41mtpwnx7 > > The Pekko PPMC vote result: > https://lists.apache.org/thread/jsntxyy7wo5om0tqlp7rxzmz8oodt8pt > > The Pekko PPMC vote thread: > https://lists.apache.org/thread/ly3q9kfsovtnk6l5m8y8s8kgfs739g9x > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/pekko/GRPC-1.0.1-RC1/ > > This release has been signed with a *recently updated* PGP key, available > here: > > https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS > > Release Notes: > > https://pekko.apache.org/docs/pekko-grpc/current/release-notes/index.html > > Git branch for the release: > > https://github.com/apache/incubator-pekko-grpc/tree/v1.0.1-RC1 > Git commit ID: 53f91e8efb0416831483c34ad9ee9c211d8d > > Please download, verify, and test. > > We have also staged jars in the Apache Nexus Repository. These were > built with the same code > as appears in this Source Release Candidate. We would appreciate if > users could test with these too. > If anyone finds any serious problems with these jars, please also > notify us on this thread. > > https://repository.apache.org/content/groups/staging/org/apache/pekko/ > > In sbt, you can add this resolver. > > resolvers += "Apache Pekko Staging" at > "https://repository.apache.org/content/groups/staging; > > > The vote will be left open for at least 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > To learn more about Apache Pekko, please see https://pekko.apache.org/ > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and signatures. > [ ] LICENSE/NOTICE files exist > [ ] No unexpected binary files > [ ] Source files have ASF headers > [ ] Can compile from source > > To compile from the source, please refer to: > > > https://github.com/apache/incubator-pekko-grpc/blob/main/README.md#building-from-source > > Some notes about verifying downloads can be found at: > > https://pekko.apache.org/download.html#verifying-downloads > > > Here is my +1 (binding). > Matthew de Detrich has already voted +1 (binding) on the initial Pekko > team vote. > > Thanks, > > PJ Fanning > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Matthew de Detrich *Aiven Deutschland GmbH* Immanuelkirchstraße 26, 10405 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen *m:* +491603708037 *w:* aiven.io *e:* matthew.dedetr...@aiven.io
Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.1-incubating-rc3
+1 binding Checked sigs and sums: Matched LICENSE and NOTICE: OK DISCLAIMER: In place Built from source: ‘./build/make-distribution.sh --release -Pflink-1.17’, successfully generated the tarball Run UTs: './build/mvn test -Pflink-1.17', passed Thanks. Willem Jiang 于2023年10月12日周四 15:32写道： > > +1 binding. > > - incubating in the release kit name > - The checksums and signatures are validated. > - The LICENSE and NOTICE files look good to me. > - There is a DISCLAIMER in the release kits > - No binary files in the source release kits > - I can build the source with the command > ./build/make-distribution.sh --release > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > > > On Sat, Oct 7, 2023 at 1:29 PM Cheng Pan wrote: > > > > Hi IPMC, > > > > This is a call for a vote to release Apache Celeborn (Incubating) > > 0.3.1-incubating-rc3 > > > > The Apache Celeborn community has voted on and approved a proposal to > > release Apache Celeborn (Incubating) version 0.3.1-incubating-rc3. > > We now kindly request the Incubator PMC members review and vote on this > > incubator release. > > > > dev@celeborn vote thread: > > https://lists.apache.org/thread/wt69x5h3jxrmozkjgh2v544sgpdqhnvq > > > > dev@celeborn vote result thread: > > https://lists.apache.org/thread/p6m2ko6lok8wkbbswt1n2qhwm0rh4xf4 > > > > The git tag to be voted upon: > > https://github.com/apache/incubator-celeborn/releases/tag/v0.3.1-incubating-rc3 > > > > The git commit hash: > > 861788810642ef19769b097b82bee70b92e0ace0 > > > > The source and binary artifacts can be found at: > > https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.1-incubating-rc3 > > > > The staging repo: > > https://repository.apache.org/content/repositories/orgapacheceleborn-1040 > > > > Fingerprint of the PGP key release artifacts are signed with: > > 8FC8075E1FDC303276C676EE8001952629BCC75D > > > > My public key to verify signatures can be found in: > > https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS > > > > 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 (and the reason) > > > > Checklist for release: > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > Steps to validate the release: > > https://www.apache.org/info/verification.html > > > > Instructions for making binary artifacts from source: > > build/make-distribution.sh --release > > > > Thanks, > > Cheng Pan > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Release Apache Baremaps 0.7.2-rc3 (incubating)
Thanks a lot for the clarification, we will eventually get familiar with the process > On 11 Oct 2023, at 21:02, Julian Hyde wrote: > > Note that 3 of those +1s (me, Calvin, JB) are binding because they are > Incubator PMC members, 2 are not (Bertil, Leonard). > > 3 binding +1s is sufficient for the vote to pass. > > Congratulations! > > Julian > > On Tue, Oct 10, 2023 at 12:49 AM Bertil Chapuis wrote: >> >> Hello Everyone, >> >> The vote for Apache Baremaps 0.7.2-rc3 (incubating) is now closed. The >> results are summarised below. Thank you all for taking the time to provide >> valuable feedbacks for this release, we are getting very close from being >> fully compliant with the guidelines. >> >> Binding Votes: >> >> +1 votes [5]: >> - Leonard Cseres >> - Julian Hyde >> - Jean-Baptiste Onofré >> - Calvin Kirs >> - Bertil Chapuis >> >> 0 votes [0]: >> None >> >> -1 votes [0]: >> None >> >> Best regards, >> >> Bertil >> >> >> >>> On 7 Oct 2023, at 07:08, Calvin Kirs wrote: >>> >>> +1 （binding） >>> >>> I checked: >>> - incubating in name >>> - signatures and hashes are fine >>> - disclaimer-wip exists >>> - license and notice files look good >>> - file have correct ASF headers if necessary >>> >>> On Thu, Oct 5, 2023 at 7:19 PM Jean-Baptiste Onofré >>> wrote: +1 (binding) I checked: - signatures and hashes ok - asf headers - license, notice and disclaimer are there - no binary found in source distribution Thanks Regards JB Le mar. 3 oct. 2023 à 00:10, Bertil Chapuis a écrit : > Hello Everyone, > > This is a call for a vote to release Apache Baremaps 0.7.2 (incubating), > release candidate 3. Apache Baremaps is a toolkit and a set of > infrastructure components for creating, publishing, and operating online > maps. > > We would like to thanks everyone who has vetted the previous release > candidates and who has contributed to the project. This release candidate > fixes the issues identified in the previous vote thread: > https://lists.apache.org/thread/vzvl8rl5h5k9vj3j2xhbkn92zvn4db2f > > We now would like to request the Incubator PMC members to review and vote > on this new release candidate. > > You can read the release notes here: > https://github.com/apache/incubator-baremaps/releases/tag/v0.7.2-rc3 > > The commit to be voted upon: > https://github.com/apache/incubator-baremaps/tree/v0.7.2-rc3 > > Its hash is 823b55507eec425776d996b64b489c8235f6bb37. > > Its tag is v0.7.2-rc3. > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.2-rc3/ > > The hashes of the artifacts are as follows: > 658ed9f9d7836c774095bd6079a39c92b366da38d733a04f2334ca39e55d41001ea997c826f9024bae51034ee6861d153ef1948defff8ebf02ce18b79d52319b > ./apache-baremaps-0.7.2-incubating-src.tar.gz > 778a4c2e657b5f632f9abe547d68978da40f162bdddc6dc342586b40952b0c72a0c4f6976cc47f720134c7e547af58f1efa39ddb2441e7f57c7a35fee68a1915 > ./apache-baremaps-0.7.2-incubating-bin.tar.gz > > Release artifacts are signed with the following key: > http://people.apache.org/keys/committer/bchapuis.asc > https://downloads.apache.org/incubator/baremaps/KEYS > > The README file for the src distribution contains instructions for > building and testing the release. > > Please vote on releasing this package as Apache Baremaps 0.7.2. > > The vote is open for the next 72 hours and passes if a majority of at > least three +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Baremaps 0.7.2 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Best, > > Bertil > >>> >>> >>> >>> -- >>> Best wishes！ >>> CalvinKirs >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org > For additional commands, e-mail: dev-h...@baremaps.apache.org > signature.asc Description: Message signed with OpenPGP
[VOTE] Release Apache Pekko(incubating) gRPC 1.0.1-RC1
Hello Incubator Community, This is a call for a vote to release Apache Pekko(incubating) gRPC version 1.0.1-RC1. The discussion thread: https://lists.apache.org/thread/tlmk742qvm0tlfmk3o24cch41mtpwnx7 The Pekko PPMC vote result: https://lists.apache.org/thread/jsntxyy7wo5om0tqlp7rxzmz8oodt8pt The Pekko PPMC vote thread: https://lists.apache.org/thread/ly3q9kfsovtnk6l5m8y8s8kgfs739g9x The release candidate: https://dist.apache.org/repos/dist/dev/incubator/pekko/GRPC-1.0.1-RC1/ This release has been signed with a *recently updated* PGP key, available here: https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS Release Notes: https://pekko.apache.org/docs/pekko-grpc/current/release-notes/index.html Git branch for the release: https://github.com/apache/incubator-pekko-grpc/tree/v1.0.1-RC1 Git commit ID: 53f91e8efb0416831483c34ad9ee9c211d8d Please download, verify, and test. We have also staged jars in the Apache Nexus Repository. These were built with the same code as appears in this Source Release Candidate. We would appreciate if users could test with these too. If anyone finds any serious problems with these jars, please also notify us on this thread. https://repository.apache.org/content/groups/staging/org/apache/pekko/ In sbt, you can add this resolver. resolvers += "Apache Pekko Staging" at "https://repository.apache.org/content/groups/staging; The vote will be left open for at least 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason To learn more about Apache Pekko, please see https://pekko.apache.org/ Checklist for reference: [ ] Download links are valid. [ ] Checksums and signatures. [ ] LICENSE/NOTICE files exist [ ] No unexpected binary files [ ] Source files have ASF headers [ ] Can compile from source To compile from the source, please refer to: https://github.com/apache/incubator-pekko-grpc/blob/main/README.md#building-from-source Some notes about verifying downloads can be found at: https://pekko.apache.org/download.html#verifying-downloads Here is my +1 (binding). Matthew de Detrich has already voted +1 (binding) on the initial Pekko team vote. Thanks, PJ Fanning - 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.3.1-incubating-rc3
+1 binding. - incubating in the release kit name - The checksums and signatures are validated. - The LICENSE and NOTICE files look good to me. - There is a DISCLAIMER in the release kits - No binary files in the source release kits - I can build the source with the command ./build/make-distribution.sh --release Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, Oct 7, 2023 at 1:29 PM Cheng Pan wrote: > > Hi IPMC, > > This is a call for a vote to release Apache Celeborn (Incubating) > 0.3.1-incubating-rc3 > > The Apache Celeborn community has voted on and approved a proposal to > release Apache Celeborn (Incubating) version 0.3.1-incubating-rc3. > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > dev@celeborn vote thread: > https://lists.apache.org/thread/wt69x5h3jxrmozkjgh2v544sgpdqhnvq > > dev@celeborn vote result thread: > https://lists.apache.org/thread/p6m2ko6lok8wkbbswt1n2qhwm0rh4xf4 > > The git tag to be voted upon: > https://github.com/apache/incubator-celeborn/releases/tag/v0.3.1-incubating-rc3 > > The git commit hash: > 861788810642ef19769b097b82bee70b92e0ace0 > > The source and binary artifacts can be found at: > https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.1-incubating-rc3 > > The staging repo: > https://repository.apache.org/content/repositories/orgapacheceleborn-1040 > > Fingerprint of the PGP key release artifacts are signed with: > 8FC8075E1FDC303276C676EE8001952629BCC75D > > My public key to verify signatures can be found in: > https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS > > 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 (and the reason) > > Checklist for release: > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > Steps to validate the release: > https://www.apache.org/info/verification.html > > Instructions for making binary artifacts from source: > build/make-distribution.sh --release > > Thanks, > Cheng Pan > > > > - > 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
[VOTE] Release Apache OpenDAL(incubating) 0.41.0-rc.1 - Incubator Vote Round 1
Hello Incubator PMC, The Apache OpenDAL community has voted and approved the release of Apache OpenDAL(incubating) 0.41.0-rc.1. We would like to request the IPMC members to review and vote for this release. OpenDAL is a data access layer that allows users to easily and efficiently retrieve data from various storage services in a unified way. OpenDAL community vote thread: https://lists.apache.org/thread/zwr6m8qpgj82r7wkxmnovb6yv19hl7ng Vote result thread: https://lists.apache.org/thread/lm5t2f6v31lp8bmltoppqsxowxvos89x The release candidate: https://dist.apache.org/repos/dist/dev/incubator/opendal/0.41.0-rc.1/ This release has been signed with a PGP available here: https://downloads.apache.org/incubator/opendal/KEYS Git tag for the release: https://github.com/apache/incubator-opendal/releases/tag/v0.41.0-rc.1/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacheopendal-1015/ Please download, verify, and test. The VOTE will be open for at least 72 hours and until the necessary number of votes are reached. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason To learn more about Apache OpenDAL(incubating), please see https://opendal.apache.org/ Checklist for reference: [ ] Download links are valid. [ ] Checksums and signatures. [ ] LICENSE/NOTICE files exist [ ] No unexpected binary files [ ] All source files have ASF headers [ ] Can compile from source More detailed checklist please refer to: https://github.com/apache/incubator-opendal/tree/main/scripts To compile from the source, please refer to: https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md Here is a Python script in release to help you verify the release candidate: ./scripts/verify.py Thanks Sincerely, Suyan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[CANCEL][VOTE] Release Apache OpenDAL(incubating) - Incubator Vote Round 1
Hi Incubator PMC, Because of missing version in the last vote mail's subject, the last vote has been canceled. Sorry for any inconvenience. The last vote thread: https://lists.apache.org/thread/2y0t7zdjcgmhb3pcztdohxd3kmnn0jrc Sincerely, Suyan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache OpenDAL(incubating) - Incubator Vote Round 1
Hello Incubator PMC, The Apache OpenDAL community has voted and approved the release of Apache OpenDAL(incubating) 0.41.0-rc.1. We would like to request the IPMC members to review and vote for this release. OpenDAL is a data access layer that allows users to easily and efficiently retrieve data from various storage services in a unified way. OpenDAL community vote thread: https://lists.apache.org/thread/zwr6m8qpgj82r7wkxmnovb6yv19hl7ng Vote result thread: https://lists.apache.org/thread/lm5t2f6v31lp8bmltoppqsxowxvos89x The release candidate: https://dist.apache.org/repos/dist/dev/incubator/opendal/0.41.0-rc.1/ This release has been signed with a PGP available here: https://downloads.apache.org/incubator/opendal/KEYS Git tag for the release: https://github.com/apache/incubator-opendal/releases/tag/v0.41.0-rc.1/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacheopendal-1015/ Please download, verify, and test. The VOTE will be open for at least 72 hours and until the necessary number of votes are reached. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason To learn more about Apache OpenDAL(incubating), please see https://opendal.apache.org/ Checklist for reference: [ ] Download links are valid. [ ] Checksums and signatures. [ ] LICENSE/NOTICE files exist [ ] No unexpected binary files [ ] All source files have ASF headers [ ] Can compile from source More detailed checklist please refer to: https://github.com/apache/incubator-opendal/tree/main/scripts To compile from the source, please refer to: https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md Here is a Python script in release to help you verify the release candidate: ./scripts/verify.py Thanks Sincerely, Suyan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal of ResilientDB
Sure, please remove them [I do not have write access to the wiki]. Thank you kindly. --- Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis ExpoLab: https://expolab.org/ ResilientDB: https://resilientdb.com/ Phone: 914-319-7937 On Thu, Oct 12, 2023 at 12:02 AM Atri Sharma wrote: > I suggest removing them since it is leading to confusion. > > On Thu, Oct 12, 2023 at 12:27 PM Mohammad Sadoghi > wrote: > > > > Dear all, > > > > As for the question of the “Broader Contributing Members”, they do not > > qualify as initial committers as they have provided feedback / > contributed > > on the broader scope of ResilientDB, so we suggest either removing them > or > > keeping them in a separate category. I prefer keeping them as a separate > > category, but of course, we will follow the ASF recommendation.We are in > > the process of improving and upgrading our website, and we will add all > the > > initial committers to the website. Currently, from our website, we have > > also linked to our Apache proposal, which includes the complete list of > > initial committers.With regards to the question of forked repo vs. > branch, > > we are fine with either option. We have made our development public (no > > longer private), and we can work on the either public repo (main vs. > > forked), whichever mode is preferred by ASF.With regards to PR, moving > > forward, we will ensure PR reviews and issue discussions are all done on > > the public repo with complete visibility. > > > > --- > > Best Regards, > > Mohammad Sadoghi, PhD > > Associate Professor > > Exploratory Systems Lab (ExpoLab) > > Department of Computer Science > > University of California, Davis > > > > ExpoLab: https://expolab.org/ > > ResilientDB: https://resilientdb.com/ > > Phone: 914-319-7937 > > > > > > On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang > wrote: > > > > > Unlike the Linux kernel, we use the dev or main branch from the > > > official upstream repo to accept the PRs from the developer; we do the > > > release work on the other branch in the same repo. We don't use > > > another forked repo to keep those changes first. It will confuse the > > > contributor in finding the right developing branch on the project repo > > > to work on. > > > > > > I barely find the repo's PR reviews and issue discussions[1]. Without > > > sharing these development contexts, it is hard for the new contributor > > > to know the story behind the code change. We can improve the > > > situation during the incubation process. You can take the issue and > > > PRs of OpenDaL[2] as a polling example. > > > > > > BTW, the license header on the source code[3] is not the ASL > > > request[4]. We can address this kind of problem during the code > > > transfer. > > > > > > [1]https://github.com/resilientdb/resilientdb > > > [2]https://github.com/apache/incubator-opendal/ > > > [3] > > > > https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 > > > [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi > > > wrote: > > > > > > > > Dear all, > > > > > > > > *Question on Initial Committers:* > > > > As was mentioned earlier. The criteria that I used was to credit > anyone > > > who > > > > has worked on the ResilientDB project since 2018, acknowledging their > > > > contributions. Below is the detailed breakdown of our contributors. > So we > > > > can reduce the list as needed in accordance with ASF guidelines. As > for > > > the > > > > broader contributors, these are the folks who have supported > ResilientDB, > > > > e.g., formalization of the research ideas, discussion of how to > tackle a > > > > particular algorithm or its implementation, testing, and analysis. > > > However, > > > > these broader members have not contributed to the codebase. So this > is > > > why > > > > they were tagged differently.*ResilientDB Core *[all have signed > ICLA] > > > > Mohammad Sadoghi > > > > Junchao Chen > > > > Dakai Kang > > > > Suyash Gupta [Now at UC Berkeley] > > > > Sajjad Rahnama [Now at Oracle] > > > > Wayne Wang [Now at Hesai Technology] > > > > Julieta Duarte > > > > Glenn Chen > > > > *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > > > > Thamir Qadah [Umm Al-Qura University] > > > > Jinxiao Yu [Now at Amazon AWS] > > > > Arindaam Roy [Now at Square] > > > > Divjeet Singh Jas > > > > Apratim Shukla > > > > Priyal Soni [Now at Amazon AWS] > > > > Rohan Sogani [Now at Oracle] > > > > Kaustubh Shete > > > > Gopal Nambiar > > > > Saipranav Kotamreddy > > > > Haskell Lark Macaraig > > > > > > > > *Deprecated/Obsolete Features *[have been rewritten or removed] > > > > Jelle Hellings [Now at McMaster > > > University] > > > > Shesha Vishnu Prasad [Now at
Re: [DISCUSS] Incubating Proposal of ResilientDB
I suggest removing them since it is leading to confusion. On Thu, Oct 12, 2023 at 12:27 PM Mohammad Sadoghi wrote: > > Dear all, > > As for the question of the “Broader Contributing Members”, they do not > qualify as initial committers as they have provided feedback / contributed > on the broader scope of ResilientDB, so we suggest either removing them or > keeping them in a separate category. I prefer keeping them as a separate > category, but of course, we will follow the ASF recommendation.We are in > the process of improving and upgrading our website, and we will add all the > initial committers to the website. Currently, from our website, we have > also linked to our Apache proposal, which includes the complete list of > initial committers.With regards to the question of forked repo vs. branch, > we are fine with either option. We have made our development public (no > longer private), and we can work on the either public repo (main vs. > forked), whichever mode is preferred by ASF.With regards to PR, moving > forward, we will ensure PR reviews and issue discussions are all done on > the public repo with complete visibility. > > --- > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > ExpoLab: https://expolab.org/ > ResilientDB: https://resilientdb.com/ > Phone: 914-319-7937 > > > On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang wrote: > > > Unlike the Linux kernel, we use the dev or main branch from the > > official upstream repo to accept the PRs from the developer; we do the > > release work on the other branch in the same repo. We don't use > > another forked repo to keep those changes first. It will confuse the > > contributor in finding the right developing branch on the project repo > > to work on. > > > > I barely find the repo's PR reviews and issue discussions[1]. Without > > sharing these development contexts, it is hard for the new contributor > > to know the story behind the code change. We can improve the > > situation during the incubation process. You can take the issue and > > PRs of OpenDaL[2] as a polling example. > > > > BTW, the license header on the source code[3] is not the ASL > > request[4]. We can address this kind of problem during the code > > transfer. > > > > [1]https://github.com/resilientdb/resilientdb > > [2]https://github.com/apache/incubator-opendal/ > > [3] > > https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 > > [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi > > wrote: > > > > > > Dear all, > > > > > > *Question on Initial Committers:* > > > As was mentioned earlier. The criteria that I used was to credit anyone > > who > > > has worked on the ResilientDB project since 2018, acknowledging their > > > contributions. Below is the detailed breakdown of our contributors. So we > > > can reduce the list as needed in accordance with ASF guidelines. As for > > the > > > broader contributors, these are the folks who have supported ResilientDB, > > > e.g., formalization of the research ideas, discussion of how to tackle a > > > particular algorithm or its implementation, testing, and analysis. > > However, > > > these broader members have not contributed to the codebase. So this is > > why > > > they were tagged differently.*ResilientDB Core *[all have signed ICLA] > > > Mohammad Sadoghi > > > Junchao Chen > > > Dakai Kang > > > Suyash Gupta [Now at UC Berkeley] > > > Sajjad Rahnama [Now at Oracle] > > > Wayne Wang [Now at Hesai Technology] > > > Julieta Duarte > > > Glenn Chen > > > *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > > > Thamir Qadah [Umm Al-Qura University] > > > Jinxiao Yu [Now at Amazon AWS] > > > Arindaam Roy [Now at Square] > > > Divjeet Singh Jas > > > Apratim Shukla > > > Priyal Soni [Now at Amazon AWS] > > > Rohan Sogani [Now at Oracle] > > > Kaustubh Shete > > > Gopal Nambiar > > > Saipranav Kotamreddy > > > Haskell Lark Macaraig > > > > > > *Deprecated/Obsolete Features *[have been rewritten or removed] > > > Jelle Hellings [Now at McMaster > > University] > > > Shesha Vishnu Prasad [Now at Path] > > > Dhruv Krishnan [Now at Amazon AWS] > > > Shubham Pandey [Now at Cisco] > > > Steve Chen > > > Priya Holani [Now at Amazon AWS] > > > Haojun (Howard) Zhu > > > Robert HE [Now at Amazon AWS] > > > Shreenath Iyer [Now at Amazon AWS] > > > Domenic Cianfichi [Now at Amazon AWS] > > > Erik Linsenmayer [Now at General > > Atomics] > > > Shreyan Mohanty [Now at General Atomics] > > > Xinyuan Sun [Now at CertiK] > > > Patrick Liao [Now at Juniper Networks] > > > Tim Huang > > > Jared Givens > > > Aditya Bej > > > Seongwoo Choi > > > > > > *Question on Private Development:* > > > As per request, we have
Re: [DISCUSS] Incubating Proposal of ResilientDB
Dear all, As for the question of the “Broader Contributing Members”, they do not qualify as initial committers as they have provided feedback / contributed on the broader scope of ResilientDB, so we suggest either removing them or keeping them in a separate category. I prefer keeping them as a separate category, but of course, we will follow the ASF recommendation.We are in the process of improving and upgrading our website, and we will add all the initial committers to the website. Currently, from our website, we have also linked to our Apache proposal, which includes the complete list of initial committers.With regards to the question of forked repo vs. branch, we are fine with either option. We have made our development public (no longer private), and we can work on the either public repo (main vs. forked), whichever mode is preferred by ASF.With regards to PR, moving forward, we will ensure PR reviews and issue discussions are all done on the public repo with complete visibility. --- Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis ExpoLab: https://expolab.org/ ResilientDB: https://resilientdb.com/ Phone: 914-319-7937 On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang wrote: > Unlike the Linux kernel, we use the dev or main branch from the > official upstream repo to accept the PRs from the developer; we do the > release work on the other branch in the same repo. We don't use > another forked repo to keep those changes first. It will confuse the > contributor in finding the right developing branch on the project repo > to work on. > > I barely find the repo's PR reviews and issue discussions[1]. Without > sharing these development contexts, it is hard for the new contributor > to know the story behind the code change. We can improve the > situation during the incubation process. You can take the issue and > PRs of OpenDaL[2] as a polling example. > > BTW, the license header on the source code[3] is not the ASL > request[4]. We can address this kind of problem during the code > transfer. > > [1]https://github.com/resilientdb/resilientdb > [2]https://github.com/apache/incubator-opendal/ > [3] > https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 > [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi > wrote: > > > > Dear all, > > > > *Question on Initial Committers:* > > As was mentioned earlier. The criteria that I used was to credit anyone > who > > has worked on the ResilientDB project since 2018, acknowledging their > > contributions. Below is the detailed breakdown of our contributors. So we > > can reduce the list as needed in accordance with ASF guidelines. As for > the > > broader contributors, these are the folks who have supported ResilientDB, > > e.g., formalization of the research ideas, discussion of how to tackle a > > particular algorithm or its implementation, testing, and analysis. > However, > > these broader members have not contributed to the codebase. So this is > why > > they were tagged differently.*ResilientDB Core *[all have signed ICLA] > > Mohammad Sadoghi > > Junchao Chen > > Dakai Kang > > Suyash Gupta [Now at UC Berkeley] > > Sajjad Rahnama [Now at Oracle] > > Wayne Wang [Now at Hesai Technology] > > Julieta Duarte > > Glenn Chen > > *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > > Thamir Qadah [Umm Al-Qura University] > > Jinxiao Yu [Now at Amazon AWS] > > Arindaam Roy [Now at Square] > > Divjeet Singh Jas > > Apratim Shukla > > Priyal Soni [Now at Amazon AWS] > > Rohan Sogani [Now at Oracle] > > Kaustubh Shete > > Gopal Nambiar > > Saipranav Kotamreddy > > Haskell Lark Macaraig > > > > *Deprecated/Obsolete Features *[have been rewritten or removed] > > Jelle Hellings [Now at McMaster > University] > > Shesha Vishnu Prasad [Now at Path] > > Dhruv Krishnan [Now at Amazon AWS] > > Shubham Pandey [Now at Cisco] > > Steve Chen > > Priya Holani [Now at Amazon AWS] > > Haojun (Howard) Zhu > > Robert HE [Now at Amazon AWS] > > Shreenath Iyer [Now at Amazon AWS] > > Domenic Cianfichi [Now at Amazon AWS] > > Erik Linsenmayer [Now at General > Atomics] > > Shreyan Mohanty [Now at General Atomics] > > Xinyuan Sun [Now at CertiK] > > Patrick Liao [Now at Juniper Networks] > > Tim Huang > > Jared Givens > > Aditya Bej > > Seongwoo Choi > > > > *Question on Private Development:* > > As per request, we have transitioned away from local/private development. > > We have forked our public ResilientDB, and we began the process of moving > > all experimental features into this repo. All these ongoing features are > > available in this repo but are still under development and not yet ready > to > > be released to the main repository.*Our New Development Repo: * > >
