Re: [DISCUSS] Dubbo Release schedule

On Thu, Apr 19, 2018 at 10:22 AM, Jun Liu wrote: > Hi ALL, > > > 0. Should we have release manager for these artifacts? Is there any > > committer volunteer to be release manager? > > Fortunately, haven't missed this release yet. I’d like to be the release > manager for the

Re: [DISCUSS] Dubbo Release schedule

On Thu, Apr 19, 2018 at 11:48 AM, Huxing Zhang wrote: > Hi, > > On Thu, Apr 19, 2018 at 11:23 AM, Justin Mclean > wrote: > > Hi, > > > >> It is not mandatory to change the project groupId to org.apache.dubbo in > >> the first release. Is that right?

Re: [DISCUSS] Dubbo Release schedule

hi, Justin As John said in https://lists.apache.org/thread.html/c4bc85049b02b179ef1c785b7c1a3d29c5832e389a93f2b0d91151a0@%3Cdev.dubbo.apache.org%3E It is not mandatory to change the project groupId to org.apache.dubbo in the first release. Is that right? We will finished it before graduating.

Re: [DISCUSS] Dubbo Release schedule

>> 2. What should be included in the 2.6.x release? My suggestion is >> label the issues and pull request with a milestone like >> "2.6.2-release”. > > +1 milestone, every committer should check the milestone before a merge or > commit. > Actually, we already have a milestone ‘2.6.2’ tracking

Re: [DISCUSS] Dubbo Release schedule

Hi ALL, > 0. Should we have release manager for these artifacts? Is there any > committer volunteer to be release manager? Fortunately, haven't missed this release yet. I’d like to be the release manager for the first apache release. > 1. Should we keep the release cycle for 2.6.x? Our first

Re: [DISCUSS] Dubbo Release schedule

Hi, > I would suggest making a release branch and not doing a code freeze as the > release may take a little time to get right. > > One issue I’m concerned about is IP clearance [1] as that is likely to block > the release. I would like to follow and double-check the IP clearance process, any

Re: [DISCUSS] Dubbo Release schedule

Hi, > 0. Should we have release manager for these artifacts? Is there any > committer volunteer to be release manager? In general Apache project do have release managers. > 1. Should we keep the release cycle for 2.6.x? Our first Apache > release might take some time because we have bunch of

Re: [DISCUSS] Dubbo Release schedule

Ping. On Thu, 12 Apr 2018 at 14:36, Huxing Zhang wrote: > Hi All, > > For now, the dubbo community have three release artifact: > 1. dubbo 2.6.x > 2. dubbo 2.5.x > 3. dubbo-spring-boot-starter > > The release cycle of 2.6.x is roughly a month, while 2.5.x is > uncertain

[DISCUSS] Dubbo Release schedule

Hi All, For now, the dubbo community have three release artifact: 1. dubbo 2.6.x 2. dubbo 2.5.x 3. dubbo-spring-boot-starter The release cycle of 2.6.x is roughly a month, while 2.5.x is uncertain because it is a maintenance branch that only accept bugfix. dubbo-spring-boot-starter only have 1