Instructions for adjusting tracer-sofa-boot-starter management policy

[glmapper]

tracer-sofa-boot-starter management

Starting from SOFATracer 3.1.0, the tracer-sofa-boot-starter will no longer be managed under https://github.com/sofastack/sofa-tracer. At that time, the version management and iteration of the tracer-sofa-boot-starter will be released Under https://github.com/sofastack/sofa-boot.

This approach is mainly to make the starter management and control of the sofa-stack component set more reasonable, and also more in line with spring boot's specifications on starter management.

In fact, we have started to migrate tracer-sofa-boot-starter since SOFABoot 3.2.0, but in order to maintain the continuity of the version, a version of tracer-sofa-boot-starter is also maintained in the tracer's own code warehouse.

Obviously this approach is very bad. We hope that the tracer warehouse only maintains the core API and component plugins, and hands over the automatic configuration capabilities to SOFABoot for unified management and control.

从 SOFATracer 3.1.0 版本开始，tracer-sofa-boot-starter 将不在放在 https://github.com/sofastack/sofa-tracer 下管理，届时 tracer-sofa-boot-starter 的版本管理及迭代将放在https://github.com/sofastack/sofa-boot 下。

这种做法主要是为了使得 sofa-stack 组件集的 starter 管控更加合理化，同时也更符合 springboot 关于 starter 管理的规范。

实际上我们从 SOFABoot 3.2.0 版本开始，就已经开始迁移 tracer-sofa-boot-starter， 但是为了保持版本的连续性，在 tracer 自己的代码仓库中同样也维护了一个版本的 tracer-sofa-boot-starter.

很明显这种做法是非常糟糕的。我们希望 tracer 仓库只维护核心 API 和 组件插件，将自动配置能力交给 SOFABoot 来统一管控。

New features will no longer sync to 2.x

Next, we do not consider syncing the new features to the SOFATracer 2.x version series (SpringBoot 1.x), the previous ones will only provide corresponding bugfixes.

接下来我们不考虑将新的 features 同步到 SOFATracer 2.x 版本系列(SpringBoot 1.x)，之前的将只提供相应的 bugfix。