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 [email protected].
To unsubscribe, please send an email to: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to