I think we can define the versions of all sub-projects independently. We don't need to put too many restrictions on these sub-projects.
Also, we can refer SpringBoot and SpringCloud, which have separate versions. For those sub-projects, we can maintain the dependent relationship. The most important thing is that we need to consider how to define the boundaries between different sub-projects. > On May 17, 2021, at 14:53, Jun Liu <[email protected]> wrote: > > I think it’s better to keep a separate version for each module for each > extension may evolve at different pace. > >> 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. > > I think we can treat the version of the Apache source package, the parent > project, and the version of the convenient binary packages, the children > modules, differently. For source package, we have a unified version and it > get increased each time. For Maven binary package, we can publish separately > by modules as needed with the module version increased independently. > > Jun > >> On May 10, 2021, at 9:34 PM, Albumen Kevin <[email protected]> wrote: >> >> 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 > >
