Re: [D] How to Retain Used By After Migrating to an Apache Organization [incubator-seata]

["funky-eyes (via GitHub)" <gi...@apache.org>]

GitHub user funky-eyes edited a discussion: How to Retain Used By After Migrating to an Apache Organization

我有几个想法：
1. 发布apache-seata的包后，发布一个io.seata:seata-all 1.9.0 内部无任何代码，只有maven依赖apache-seata-all的依赖包,并且去除shade io.seata的操作，这样只要有用户使用io.seata下的seata-all，就会引入org.apache.seata的依赖,随着时间,无论使用apacheseata还是io.seata的用户都会算到org.apache.seata:seata-all中

2. 发布一个io.seata下的seata，也是一样没有任何代码，被apache-seata所依赖，然后used by这块统计延续使用io.seata:seata-all即可
如果社区的各位有更多想法欢迎在此讨论

I have a few ideas:
1. After releasing the apache-seata package, we should release a seata package under io.seata with no code, but only a maven dependency on the apache-seata-all package. This way, users who use seata-all under io.seata will automatically import the dependencies of org.apache.seata.
2. We can also release a seata package under io.seata, which is also without any code, but is dependent on apache-seata. Then, the "used by" section can continue to track the usage of io.seata:seata-all. If anyone in the community has more ideas, please feel free to discuss them here.

GitHub link: https://github.com/apache/incubator-seata/discussions/6058

----
This is an automatically sent email for dev@seata.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@seata.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@seata.apache.org
For additional commands, e-mail: dev-help@seata.apache.org