Hi, Apache Seata Community: I have counted the modules that need to be compatible with the io.seata package. The specific modules have been forwarded here by g...@apache.org. We need to work together to provide backward compatibility support for these modules. Who is willing to claim the tasks of these modules? I will mark the seata server first and I am already following up, because I am the author of the seata server raft mode, and I am familiar with issues related to compatibility, so I will take this task first, and I hope everyone understands. Jianbin Chen, githubId: funky-eyes
funky-eyes (via GitHub) <g...@apache.org> 于 2024年1月24日周三 23:33写道： > > GitHub user funky-eyes added a comment to the discussion: How to smooth > the upgrade after transferring to an apache organization > > Involves modules that need to be compatible with the `io.seata package`. > seata-http-jakarta > seata-http > tcc > seata-saga-statelang > seata-saga-engine > seata-saga-engine-store > integration-tx-api > spring > rm-datasource > tm > seata-grpc > server > The modules with relatively low impact are. > seata-grpc > integration-tx-api (because 2.0 only launched, basically internal call, > external direct use of api should be less users) > seata-http-jakarta (springboot3 and tomcat10 should have fewer users for > now) > server (The raft cluster mode was only introduced in 2.0, and it is marked > as a sexual function, so it is theoretically possible that compatibility is > not 100% compatible) > > GitHub link: > https://github.com/apache/incubator-seata/discussions/6059#discussioncomment-8234316 > > ---- > This is an automatically sent email for dev@seata.apache.org. > To unsubscribe, please send an email to: dev-unsubscr...@seata.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org > For additional commands, e-mail: dev-h...@seata.apache.org > >
