merged, now it is critical to provide dubbo compatibility package as soon as possible, since the current code base will effect existing dubbo samples and dubbo apps.
BTW, +1 to maven groupId change without doubt. Thanks, -Ian. On Fri, Jun 15, 2018 at 2:23 PM Yong Zhu <diecui1...@gmail.com> wrote: > Since the pacakge has been rename to org.apache, new PRs can be sent with > confidence. > > Next step, I'll add dubbo-compatible. > > Another question, I suggest rename groupId to org.apache with this big > change, What do you think? > > On Thu, Jun 14, 2018 at 9:25 AM Yong Zhu <diecui1...@gmail.com> wrote: > > > Now, I'll start to do this task, and then send a PR to master. At the > same > > time, I'll add a new module named "dubbo-compatible" to support old > > extensions, this will take some time. > > > > On Fri, Jun 8, 2018 at 2:09 PM Ian Luo <ian....@gmail.com> wrote: > > > >> agree, let's address the exiting PRs as soon as possible, to make the > >> renaming package effort easier. > >> > >> -Ian. > >> > >> On Fri, Jun 8, 2018 at 10:31 AM Xin Wang <wang...@apache.org> wrote: > >> > >> > >Now, there also have 23 PRs under reviewing, we need to fix them > first, > >> > merge or close it > >> > > >> > I think what we need to do now is to set up a deadline to deal with > >> these > >> > 23 PRs quickly. > >> > > >> > > >> > Jun Liu <liu...@apache.org> 于2018年6月8日周五 上午10:04写道： > >> > > >> > > > I suggest that we have to freeze new comming PR after notification > >> > > community. > >> > > > >> > > I don’t think it’s necessary to freeze PRs. > >> > > > >> > > To some extend, it'is the PRs containing pretty much changes that > will > >> > > have most of the compatibility problems. Since currently most of the > >> > > features under progress are developing by the Dubbo team or some > >> > > contributors who keeps a close contact with Dubbo community, we can > >> avoid > >> > > the compatibility problem to the greatest extend. > >> > > > >> > > Even though, we should still make sure that the whole community get > >> fully > >> > > notified of the package rename plan, so they can start or refactor > >> their > >> > > patches based on the codebase before or after rename. > >> > > > >> > > Best regards, > >> > > Jun > >> > > > >> > > > On 7 Jun 2018, at 3:42 PM, Mercy <mercybl...@gmail.com> wrote: > >> > > > > >> > > > I suggest that we have to freeze new comming PR after notification > >> > > community. > >> > > > > >> > > > > >> > > > Kind regards, > >> > > > > >> > > > Mercy Ma > >> > > > > >> > > > > >> > > > 在 2018/6/7 下午3:32, Yong Zhu 写道: > >> > > >> Now, there also have 23 PRs under reviewing, we need to fix them > >> > first, > >> > > >> merge or close it. Then we rename the package ASAP. > >> > > > > >> > > > >> > > > >> > > >> > > >
