Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.1-incubating-rc3
Start from my own +1 (non-binding) Looking forward votes from IPMC members ~ Thanks, Cheng Pan > On Oct 7, 2023, at 13:29, 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
Re: [DISCUSS] Incubating Proposal of ResilientDB
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: * > https://github.com/msadoghi/resilientdb/*Notable Branches (Active Projects)* > Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe > Rotating Leader (lightweight recovery): > https://github.com/msadoghi/resilientdb/tree/hs > Queue-Oriented Concurrency Control (concurrent execution): > https://github.com/msadoghi/resilientdb/tree/QueccBranch > Smart Contract Concurrency: > https://github.com/msadoghi/resilientdb/tree/smartcontract_cc > > --- > 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 Mon, Oct 9, 2023 at 6:18 PM Dave Fisher wrote: > > > > > > > Sent from my iPhone > > > > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta > > > > > wrote: > > > > > > Hello All > > > > > > Let me try to add to Mohammad's response. We defined an initial committer > > > list of 40+ members as we wanted to give credit to everyone who has > > > collaborated with us on projects/papers that were built around > > ResilientDB. > > > But, the 20 contributors visible on github are the ones who worked on the > > > actual codebase, which we are trying to bring to ASF. The projects that > > > other folks worked on are independent from the ResilientDB codebase and > > > have no correlation with this release. > > > > > > So, following ASF guidelines, we are fine with
Re: [DISCUSS] Incubating Proposal of ResilientDB
I still have a question for the “Broader Contributing Members”: do we treat them as initial committers? It makes sense that we keep track of all the contributors on the project website so that no one will be surprised by the long list of initial committers. An extensive initial committer list doesn't mean we have a healthy, diverse community. It is incredibly challenging to bring those graduated students back to the project from my experience with IoTDB. When we consider the community-building work during the polling graduation evaluation, we just track the new committers we have during the incubation process. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Oct 10, 2023 at 7:43 PM 俊平堵 wrote: > > Agree with Roman and Dave that we can keep the original list. > I think Willem is just curious on the mismatch between commits and > committers, and the explanation here make sense to me. > > Thanks, > > JP > > Mohammad Sadoghi 于2023年10月10日周二 11:50写道： > > > 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: * > > https://github.com/msadoghi/resilientdb/*Notable Branches (Active > > Projects)* > > Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe > > Rotating Leader (lightweight recovery): > > https://github.com/msadoghi/resilientdb/tree/hs > > Queue-Oriented Concurrency Control (concurrent execution): > > https://github.com/msadoghi/resilientdb/tree/QueccBranch > > Smart Contract Concurrency: > > https://github.com/msadoghi/resilientdb/tree/smartcontract_cc > > > > --- > > 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 Mon, Oct 9, 2023 at 6:18 PM Dave Fisher wrote: > > > > > > > > > > > Sent from my iPhone > > > > > > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta > .invalid> > > > wrote: > > > > > > > > Hello All > > > > > > > > Let me try to add to Mohammad's response. We defined an initial > > committer > > > > list of 40+ members as we wanted to give credit to everyone who has > > > > collaborated with us on projects/papers that were built around > > > ResilientDB. > > > > But, the 20 contributors visible on github are the ones who worked on > > the > > > > actual codebase, which we are trying to bring to ASF. The projects that > > > > other folks worked on are independent from the ResilientDB codebase and > > > > have no correlation with this release. > > > > > > > > So, following ASF
Re: [RESULT][VOTE] Release Apache Baremaps 0.7.2-rc3 (incubating)
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: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Incubating Proposal of Seata
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
