There is another issue that is shall us distinguish each module with different versions. Such as make 1.0.1 for spi-1 if it has published two versions and 1.0.0 for spi-2 in dubbo-spi-extensions. If we use the same version, we can publish the whole repo together in a once.
On Wed, May 12, 2021 at 10:27 AM YunKun Huang <[email protected]> wrote: > I think it's ok to have a spi-extension version to be different from > dubbo. Although it will cause some confusion for users, we have to > make it clear in the document how to choose right version. > > On Tue, May 11, 2021 at 11:11 AM ranke <[email protected]> wrote: > > > > Independent version number can refer to Dubbo API Docs. > > But I have two problems: > > 1. If there is a separate version number, will it cause confusion for > users? > > 2. If you use the same version number as apache/dubbo, you > have to release the version at the same time as apache/dubbo. But in > fact, some subprojects have not been modified and are compatible with the > new version. Or some subprojects are not ready to release, > so apache/dubbo needs to wait? > > > > > > > > > > ------------------ Original ------------------ > > From: "Albumen Kevin"<[email protected]>; > > Date: 2021年5月10日(星期一) 晚上9:34 > > To: "dev"<[email protected]>; > > Subject: [Discuss] The planning of dubbo-spi-extensions repo > > > > > > > > Hi Community, > > > > Currently we have a dubbo-spi-extensions repo[1] to contain some > > infrequently used extensions which is also not necessary to remove from > > dubbo. > > Such as some customized cluster implementation is only used when healthy > > checking, and there are some users who really depend on this > implementation. > > dubbo-spi-extensions repo is a good choice for these implementations, > which > > will not affect apache/dubbo for most users and provide a pluggable way > if > > users need it. > > > > Thanks for @haoyann hard work, we can make sure that dubbo-spi-extensions > > can work fine with ExtensionLoader. > > > > However, there are some questions should be resolved: > > > > 1. How can we define an extension that is needed to move > > to dubbo-spi-extensions while it is in apache/dubbo repo now? > > > > 2. How can we define the version of these sub projects? > > > > If we make these sub projects the same version at a time, we need to > > publish the whole repo timing, so we can make sure the extensions are up > to > > date. Such as a month? > > > > If we make these sub projects having different versions, how can we > publish > > only one of them if needed? > > > > Do you have any suggestions? > > > > [1] > > > https://lists.apache.org/thread.html/r9248ffdc11716d5e1089911652ef69eb39ec33aeeda133e6b5c2e441%40%3Cdev.dubbo.apache.org%3E > > > > Albumen >
