New feature development and stability improvement are equally important to product. But adding new features will affect stability, dubbo uses the following version development pattern to achieve a good balance.
2.4.x. This is called the GA version, which can be applied in production. We are supposed only to fix bugs in this version, and increase the third version number when release.
2.5.x. We add new features to this version, so applications have opportunities try new features.
When features in
2.5.x are proved stable enough, we will announce
2.5.x as a beta release.
2.5.x proved stable after enough test on enough applications：
2.5.x, the GA Version, only do BugFix, the main version to be used. We can try to promote applications to upgrade to GA at the desired time.
2.4.x, no longer maintained. When bugs appear, applications have no choice but upgrade to the latest stable version- Sunset Clause
2.5.xfor new features.
Users should always keep in track with the GA Version, make sure all bugs were fixed.
There is a fake proposition: regular upgrades bring more risks. Here's the reasons: