I am generally agree with creating a new branch for incompatible changes. 1. But the naming of the branch looks inconsistent to me:
* develop: 2.7.x * master: 2.6.x * 2.5.x: 2.5.x What about next major version, is there a branch called 2.8.x or 3.0.x? 2. should every pull request sent against 2.7.x and be back ported to 2.6.x? On Fri, May 25, 2018 at 2:41 PM, Ian Luo <ian....@gmail.com> wrote: > good suggestion, it looks like we have to maintain two trunks. +1 > > On Fri, May 25, 2018 at 9:45 AM Jun Liu <liu...@apache.org> wrote: > >> I think we should create a new branch, for example “develop”, for the >> development of those upcoming incompatible or long-term features. By doing >> that, master branch and develop branch can evolve independently, and when >> develop branch is ready, it can be released with version 2.7.0, identifying >> the incompatibility with 2.6.x. >> >> Here’s some works i think need to start on a new branch: >> - Support for java 8 or higher. >> - Package renaming required in Apache IP Clearance. >> - Transfer some extensions to Dubbo eco-system[1][2]. >> - Some in compatible or long-term developing features: async api, metadata >> refactor, modularization…[3][4] >> >> 1. https://github.com/dubbo <https://github.com/dubbo> >> 2. >> https://lists.apache.org/thread.html/a5e5e1a09cb15b1d508cf22ce2bd674ddc915ffbfe16dda55dbc90ac@%3Cdev.dubbo.apache.org%3E >> < >> https://lists.apache.org/thread.html/a5e5e1a09cb15b1d508cf22ce2bd674ddc915ffbfe16dda55dbc90ac@%3Cdev.dubbo.apache.org%3E >> > >> 3. https://issues.apache.org/jira/browse/DUBBO-22 < >> https://issues.apache.org/jira/browse/DUBBO-22> >> 4. https://issues.apache.org/jira/browse/DUBBO-24 < >> https://issues.apache.org/jira/browse/DUBBO-24> >> >> Best regards, >> Jun -- Best Regards！ Huxing
