Hi, Albumen，Yunkun I think the usual way is: 1. Create a 2.7.x branch from the master branch as the maintenance branch
2. Merge the 3.0 branch into the master branch, 3 And then delete branch 3.0 Albumen Kevin <[email protected]> 于2021年6月18日周五 下午5:20写道： > Hi YunKun, > > Existing PRs will work fine due to GitHub changing it automatically. > The problem is users who tracked master in local will break. > > I think it is necessary to rename the master branch to the 2.7.x branch. > However, we should consider whether to rename the 3.0 branch to the master > branch or not. > > On Fri, Jun 18, 2021 at 5:04 PM YunKun Huang <[email protected]> wrote: > > > or maybe we should rename 3.0 branch to master branch? > > not sure if it will broke existing PR > > > > On Thu, Jun 17, 2021 at 2:11 PM Xin Wang <[email protected]> > wrote: > > > > > > +1 to agree > > > > > > Horizon <[email protected]> 于2021年6月16日周三 上午11:27写道： > > > > > > > +1 > > > > > > > > > > > > > 2021年6月16日 10:38，Jun Liu <[email protected]> 写道： > > > > > > > > > > +1 > > > > > > > > > > 3.0 represents the next generation Dubbo and should be placed at a > > > > prominent position. > > > > > > > > > > Jun > > > > > > > > > >> On Jun 13, 2021, at 3:59 PM, Albumen Kevin <[email protected]> > > wrote: > > > > >> > > > > >> Hello Community, > > > > >> > > > > >> With everyone's strong support, Apache Dubbo 3.0 is about to be > > > > released. > > > > >> > > > > >> Shall we change the default branch in GitHub repo[1] to 3.0 > > branch[2], > > > > >> which can guide > > > > >> new contributors to contribute to Dubbo 3 easily, and rename the > > master > > > > >> branch to `2.7` branch? > > > > >> > > > > >> [1] https://github.com/apache/dubbo/branches > > > > >> [2] https://github.com/apache/dubbo/tree/3.0 > > > > >> > > > > >> Thanks, > > > > >> Albumen Kevin > > > > > > > > > > > > > > > >
