Hi Lan, I think Mark means you could publish dubbo starter(also same for dubbo in another discussion) with ‘old’ group and ‘old’ name before transition to the ASF.
Best Regards, Tang Ke > 在 2018年3月8日，22:25，Kimm King <[email protected]> 写道： > > I think mentor means in another thread: > we could publish something to maven central repository as usual until > transition is done. > > > > KimmKing([email protected]) > == In me the tiger sniffs the rose. == > > > From: Ian Luo > Date: 2018-03-08 21:40 > To: dev > Subject: Re: On double dubbo starters > >> On 8 Mar 2018, at 9:22 PM, Ian Luo <[email protected]> wrote: >> >> Sure, then we will not publish anything to maven repository until transition >> is done. >> > > Oops, I think I misunderstood. Mark, could you pls. confirm we could still > publish release from the “old” repositories during the transition? > > Thanks, > -Ian. > > >> Adrian, I guess this decision shouldn’t stop your further development work >> since you could depend on the snapshot build anyway. We will try our best to >> work with Mark and other apache mentors to boost the transition as fast as >> possible. >> >> Thanks, >> -Ian. >> >> >> >>> On 8 Mar 2018, at 5:40 PM, Mark Thomas <[email protected]> wrote: >>> >>> On 07/03/18 11:41, Ian Luo wrote: >>>> Hi Mark, >>>> >>>> Pls. check my comments below. >>> >>> Thanks for the additional information. >>> >>> Until the code transitions to the ASF (which I hope is fairly soon), and >>> especially if the community needs a release, then you are able to >>> publish releases as you have done previously. >>> >>> Once the code transitions to the ASF, the ASF release policy applies. >>> Depending on where you start from, it can take a little work to get >>> everything aligned to the policy but that only needs to be done once. >>> >>> Mark >>> >>> >>>> >>>> Thanks, >>>> -Ian. >>>> >>>> >>>>> On 7 Mar 2018, at 6:09 PM, Mark Thomas <[email protected]> wrote: >>>>> >>>>> On 07/03/18 09:49, Ian Luo wrote: >>>>>> Hi Adrian, >>>>>> >>>>>> First of all, my apology for the confusion. The project under dubbo [1] >>>>>> group is the official project we plan to maintain in long term for >>>>>> Spring Boot support. I encourage you try it first and share your >>>>>> feedback if there’s any. >>>>>> >>>>>> In order to not block Adrian’s work, I suggest to publish it with the >>>>>> existing groupId/artifactId since we can always republish with the new >>>>>> groupId/artifactId in the next release cycle after the transition >>>>>> finishes. >>>>>> >>>>>> To dubbo’s mentors, I am not sure if it is appropriated for my proposal. >>>>>> Pls. correct me once you read the message since we plan to release >>>>>> spring-boot-starter officially very soon (by the end of this week or the >>>>>> early of the next week). >>>>>> >>>>>> Thanks, >>>>>> -Ian. >>>>>> >>>>>> 1. https://github.com/dubbo/dubbo-spring-boot-project >>>>> >>>>> Hi, >>>>> >>>>> I need a little more information before offering an opinion. >>>>> >>>>> 1. Who is the "we" that intends to publish the release? >>>> >>>> [iluo]: Here “we” means dubbo development team. >>>> >>>>> >>>>> 2. How will the release be named (including Maven co-ordinates)? >>>> >>>> [iluo]: It will be com.alibaba.boot:dubbo-spring-boot-starter at this >>>> moment. >>>> >>>>> >>>>> 3. Is it intended that this code will become part of Apache Dubbo? If >>>>> so, what stage is this code at in its transition to the ASF? >>>> >>>> [iluo]: It’s a side project [1] of Apache Dubbo. All projects under dubbo >>>> group [2] will be included in this transition, you could check details >>>> from JIRA issue DUBBO-3 [3]. >>>> >>>> >>>> 1. https://github.com/dubbo/dubbo-spring-boot-project >>>> 2. https://github.com/dubbo >>>> 3. https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3 >>>> >>>>> >>>>> Thanks, >>>>> >>>>> Mark >>>>> >>>>> >>>>>> >>>>>> >>>>>>> On 7 Mar 2018, at 5:04 PM, Adrian Cole <[email protected]> wrote: >>>>>>> >>>>>>> Hi, all >>>>>>> >>>>>>> I'm working on spring-cloud-sleuth tracing integration with dubbo. >>>>>>> We've had users requesting dubbo for a while now for spring boot >>>>>>> applications. >>>>>>> >>>>>>> https://github.com/spring-cloud/spring-cloud-sleuth/issues/710 >>>>>>> >>>>>>> One of the commitments we made was to have dubbo tracing included for >>>>>>> spring boot 2 applications, leveraging the efforts we made in the >>>>>>> Zipkin library Brave (which similarly had a backlog of dubbo >>>>>>> interest). >>>>>>> >>>>>>> The good news is that, I've been able to get this working, which is >>>>>>> awesome. >>>>>>> >>>>>>> https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing >>>>>>> >>>>>>> I'm only waiting a couple small patches and we are ready to go! The >>>>>>> community have been great and the plugin changes quickly in the right >>>>>>> direction. >>>>>>> >>>>>>> I ran into a glitch as I was told that the plugin I use, the "alibaba" >>>>>>> variant, is not official. Rather, the "dubbo" one was. >>>>>>> >>>>>>> https://github.com/alibaba/dubbo-spring-boot-starter < I am using this >>>>>>> and it works >>>>>>> https://github.com/dubbo/dubbo-spring-boot-project < haven't tried >>>>>>> this, yet >>>>>>> >>>>>>> I would like to try the other version, but it seems to be in release >>>>>>> limbo. For example, it is not published anywhere and there are some >>>>>>> concerns about publishing it while apache takes its course. >>>>>>> >>>>>>> https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3 >>>>>>> >>>>>>> Meanwhile, I actually like the plugin I am using and the person >>>>>>> maintaining it is good. This is a tough situation to be in where what >>>>>>> is working is not recommended, and what is recommended I have to build >>>>>>> or consume snapshot of. >>>>>>> >>>>>>> How should we proceed on this? >>>>>>> -A >>>> >>>> >>> >>
