-
Notifications
You must be signed in to change notification settings - Fork 26.5k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dubbo Java Roadmap #13065
Comments
Github完善 是否加个历史issue治理,现在open的900多 |
性能这里可以深度挖掘下,每天跑一次把遗留的和性能问题提前挖掘出来,一起优化下 |
dubbo admin 与dubbo兼容低版本这一块是升级用户的通用的一个痛点可以看看能不能专门来挖掘一下做一些适配 |
虚拟线程也要马上兼容一下,JDK21马上发射了。 |
Triple 协议对比 Dubbo 协议的使用限制、不兼容列表 |
Hi there, |
The majority of Dubbo users are now using jdk 8. So I think we might do that on a new branch like |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
For Dubbo3, there are currently three major active versions:
3.1
,3.2
, and3.3
in the community. Among them,3.2
is the recommended stable version while3.3
is currently in thebeta
stage which will replace3.2
as the latest stable version in the coming months.As of version
3.3.0-beta.1
, the core features we have planned for Dubbo3 will be covered. So from this version on, Dubbo3 will enter the long-term stability maintenance phase, which means that we will not introduce any big features for any new Dubbo3 versions in the future, and the community will focus on iteration and stability assurance of existing features. Based on this, we have made the Roadmap as listed below:中文版本
对于 Dubbo3 而言,当前社区维护有 3.1、3.2、3.3 三个大的版本,其中 3.2 是当前推荐的稳定生产版本,3.3 正处于 beta 阶段,在接下来几个月将取代 3.2 成为最新稳定版本。
截止 3.3.0-beta.1 版本,整个 Dubbo3 规划的核心功能均已开发完成。从这个版本开始,Dubbo3 将进入长期稳定维护阶段,这意味着我们将不会再为任何的 Dubbo3 新版本引入新的功能规划,社区将专注在已有功能的迭代与稳定性保证上。基于这样的基调,我们制定了下文中的 Roadmap。
3.3.0-beta 系列迭代
轻量化
remoting 与 protocol 层重构
项目规范化 & 影响体验的关键问题
文档升级
extension 库
ref: dubbo extended tasks(扩展库规划)
benchmark 机制
kubernetes 最佳实践
一些最佳实践
Native
The text was updated successfully, but these errors were encountered: