Hi I just noted there is a release plan[1] in the JIRA, such as releasing 4.0.0 next month. I had to admit it's a really aggressive plan.
As a major release, we usually set some targets and make a plan, such as some kind of new features or roadmap and after some milestone releases we can finally do a major release. As we don't have this kind of discussion in the mailing list, I start it first. First, it's a good time to think about changing the package name at this major release, otherwise we will put more efforts to maintain the different code branches. If there are some Alibaba inside projects which is hard to change at a short time, my suggestion is keeping the RocketMQ 3.x.x branch for maintenance and upgrading the internal project step by step. It could buy us some time of the internal project upgrade if we start it right now. Second, most of the test codes are not in good sharp to help us catch the error. We need put some efforts to improve the test codes quality to build a solid framework for accepting the contribution from the community. Third, do we have any other feature development plan here? Regards, Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem
