Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Mercy Ma]

What's more, Apache Dubbo Spring Boot 2.7.0 will be the infrastructure of
Spring Cloud (Incubator) Alibaba Service-to-Service calls, which will be
released at the end of February 2019.

Github: https://github.com/spring-cloud-incubator/spring-cloud-alibaba

Kind regards,
Mercy Ma

On Wed, Jan 30, 2019 at 2:53 PM Mercy  wrote:

> Hi,
>
>
> The source code of Dubbo Spring Boot has been ready, and it will be
> about to issue a vote soon.
>
>
> Kind regards,
>
> Mercy Ma
>
> 在 2019/1/30 下午1:00, Huxing Zhang 写道:
> > Hi All,
> >
> > As 2.7.0 has just released.
> > I am thinking that we can start the process of release
> > dubbo-spring-boot-starter and dubbo-ops.
> > Mercy and Minxuan, can you share your plan on this?
> >
> > On Tue, Jan 29, 2019 at 4:11 PM Huxing Zhang  wrote:
> >> Hi All,
> >>
> >> The 2.7.0 release just passed incubator vote.
> >> I am going to publish the maven artifacts.
> >>
> >>
> >> --
> >> Best Regards！
> >> Huxing
> >
> >
>

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Ian Luo]

Sounds great.

On Wed, Jan 30, 2019 at 1:15 PM Minxuan Zhuang  wrote:

> Dubbo ops is ready, I'll call for vote today
>
> On Wed, Jan 30, 2019 at 1:00 PM Huxing Zhang  wrote:
>
> > Hi All,
> >
> > As 2.7.0 has just released.
> > I am thinking that we can start the process of release
> > dubbo-spring-boot-starter and dubbo-ops.
> > Mercy and Minxuan, can you share your plan on this?
> >
> > On Tue, Jan 29, 2019 at 4:11 PM Huxing Zhang  wrote:
> > >
> > > Hi All,
> > >
> > > The 2.7.0 release just passed incubator vote.
> > > I am going to publish the maven artifacts.
> > >
> > >
> > > --
> > > Best Regards！
> > > Huxing
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Minxuan Zhuang]

Dubbo ops is ready, I'll call for vote today

On Wed, Jan 30, 2019 at 1:00 PM Huxing Zhang  wrote:

> Hi All,
>
> As 2.7.0 has just released.
> I am thinking that we can start the process of release
> dubbo-spring-boot-starter and dubbo-ops.
> Mercy and Minxuan, can you share your plan on this?
>
> On Tue, Jan 29, 2019 at 4:11 PM Huxing Zhang  wrote:
> >
> > Hi All,
> >
> > The 2.7.0 release just passed incubator vote.
> > I am going to publish the maven artifacts.
> >
> >
> > --
> > Best Regards！
> > Huxing
>
>
>
> --
> Best Regards！
> Huxing
>

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi All,

The 2.7.0 release just passed incubator vote.
I am going to publish the maven artifacts.


-- 
Best Regards！
Huxing

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Imteyaz Khan]

Thanks a lot Jun.

On Tue, Jan 22, 2019 at 5:51 PM Ian Luo  wrote:

> Awesome. Thank you, Jun.
>
> -Ian.
>
> On Tue, Jan 22, 2019 at 5:53 PM jun liu  wrote:
>
> > 2.7.0-release has just been merged into master, please help to review.
> >
> > Jun
> >
> > > On Jan 21, 2019, at 10:42 AM, Xin Wang 
> wrote:
> > >
> > >> I am merging back the 2.7.0-release branch to master to avoid having
> too
> > > many conflicts if do it too late, then we may need to constantly do the
> > > merge with every few days before vote is done.
> > >
> > > Support this , then everyone can review the code on the master branch ,
> > > and find some issues earlier
> > >
> > > jun liu  于2019年1月21日周一 上午10:21写道：
> > >
> > >> I am merging back the 2.7.0-release branch to master to avoid having
> too
> > >> many conflicts if do it too late, then we may need to constantly do
> the
> > >> merge with every few days before vote is done.
> > >>
> > >> Jun
> > >>
> > >>> On Jan 18, 2019, at 2:28 PM, Huxing Zhang  wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> I still found some inconsistency between the source release and the
> > >>> Git tag dubbo-2.7.0:
> > >>>
> > >>> Only in apache-dubbo-incubating-2.7.0-source-release: all
> > >>> Only in apache-dubbo-incubating-2.7.0-source-release: bom
> > >>> Only in apache-dubbo-incubating-2.7.0-source-release:
> dependencies-bom
> > >>> Only in apache-dubbo-incubating-2.7.0-source-release: distribution
> > >>> Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
> > >>> Only in
> > >>
> >
> apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
> > >>> work
> > >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> > >>> dubbo-demo-consumer
> > >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> > >>> dubbo-demo-provider
> > >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
> > >>> dubbo-metrics-default
> > >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> > >>> dubbo-test-benchmark
> > >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> > >>> dubbo-test-examples
> > >>>
> > >>> It is possibly due to my local environment, I am going to do it again
> > >>> with clean checkout of Dubbo 2.7.0-release branch.
> > >>>
> > >>> On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang 
> > wrote:
> > 
> >  Hi,
> > 
> >  I found that there is a file test.patch in source release, which was
> >  the patch I used to restore the commit I reverted yesterday.
> >  This is not what we want, I am going to remove this file and
> > re-tagging
> > >> 2.7.0.
> > 
> > 
> >  On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang 
> > wrote:
> > >
> > > Hi,
> > >
> > > On Fri, Jan 18, 2019 at 12:08 AM jun liu 
> > wrote:
> > >>
> > >>> Jun, could you please summarize an English version of the release
> > >> note.
> > >>> I will send the vote email once it is done.
> > >>
> > >> It’s now available here:
> > >>
> >
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> > >
> > > Thanks for that, it looks good to me.
> > >
> > >> I think it’s time to prepare the upgrade guide and user docs now,
> > >> which is also a key part for this release.
> > >
> > > Yes, we can do that while we are doing the release vote.
> > >
> > > I am starting the vote today.
> > >>
> > >> Jun
> > >>
> > >>> On Jan 17, 2019, at 11:58 PM, Huxing Zhang 
> > >> wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> All the preparation seems going well.
> > >>> I have successfully uploaded 2.7.0 to staging repo, and upload
> the
> > >>> release candidate to svn.
> > >>> I saw that the release note is still in Chinese.
> > >>>
> > >>> Jun, could you please summarize an English version of the release
> > >> note.
> > >>> I will send the vote email once it is done.
> > >>>
> > >>> On Thu, Jan 17, 2019 at 5:48 PM victory 
> > >> wrote:
> > 
> >  I have check the file , it is the same as pull request #3263.
> > 
> > 
> >  Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> > 
> > > Hi Victory,
> > >
> > > I've mistakenly reverted your recent pull request[1].
> > > Luckily I have restored it via the commit email message.
> > > I've push it to 2.7.0-release branch already.
> > > Would you please help to check it?
> > >
> > >
> > > [1] https://github.com/apache/incubator-dubbo/pull/3263
> > >
> > > On Thu, Jan 17, 2019 at 5:08 PM victory  >
> > >> wrote:
> > >>
> > >> I have review the code and it work well in
> > >>
> > >
> > >>
> >
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> > >>
> > >> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Ian Luo]

Awesome. Thank you, Jun.

-Ian.

On Tue, Jan 22, 2019 at 5:53 PM jun liu  wrote:

> 2.7.0-release has just been merged into master, please help to review.
>
> Jun
>
> > On Jan 21, 2019, at 10:42 AM, Xin Wang  wrote:
> >
> >> I am merging back the 2.7.0-release branch to master to avoid having too
> > many conflicts if do it too late, then we may need to constantly do the
> > merge with every few days before vote is done.
> >
> > Support this , then everyone can review the code on the master branch ,
> > and find some issues earlier
> >
> > jun liu  于2019年1月21日周一 上午10:21写道：
> >
> >> I am merging back the 2.7.0-release branch to master to avoid having too
> >> many conflicts if do it too late, then we may need to constantly do the
> >> merge with every few days before vote is done.
> >>
> >> Jun
> >>
> >>> On Jan 18, 2019, at 2:28 PM, Huxing Zhang  wrote:
> >>>
> >>> Hi,
> >>>
> >>> I still found some inconsistency between the source release and the
> >>> Git tag dubbo-2.7.0:
> >>>
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: all
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: bom
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: dependencies-bom
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: distribution
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
> >>> Only in
> >>
> apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
> >>> work
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> >>> dubbo-demo-consumer
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> >>> dubbo-demo-provider
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
> >>> dubbo-metrics-default
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> >>> dubbo-test-benchmark
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> >>> dubbo-test-examples
> >>>
> >>> It is possibly due to my local environment, I am going to do it again
> >>> with clean checkout of Dubbo 2.7.0-release branch.
> >>>
> >>> On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang 
> wrote:
> 
>  Hi,
> 
>  I found that there is a file test.patch in source release, which was
>  the patch I used to restore the commit I reverted yesterday.
>  This is not what we want, I am going to remove this file and
> re-tagging
> >> 2.7.0.
> 
> 
>  On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang 
> wrote:
> >
> > Hi,
> >
> > On Fri, Jan 18, 2019 at 12:08 AM jun liu 
> wrote:
> >>
> >>> Jun, could you please summarize an English version of the release
> >> note.
> >>> I will send the vote email once it is done.
> >>
> >> It’s now available here:
> >>
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> >
> > Thanks for that, it looks good to me.
> >
> >> I think it’s time to prepare the upgrade guide and user docs now,
> >> which is also a key part for this release.
> >
> > Yes, we can do that while we are doing the release vote.
> >
> > I am starting the vote today.
> >>
> >> Jun
> >>
> >>> On Jan 17, 2019, at 11:58 PM, Huxing Zhang 
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> All the preparation seems going well.
> >>> I have successfully uploaded 2.7.0 to staging repo, and upload the
> >>> release candidate to svn.
> >>> I saw that the release note is still in Chinese.
> >>>
> >>> Jun, could you please summarize an English version of the release
> >> note.
> >>> I will send the vote email once it is done.
> >>>
> >>> On Thu, Jan 17, 2019 at 5:48 PM victory 
> >> wrote:
> 
>  I have check the file , it is the same as pull request #3263.
> 
> 
>  Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> 
> > Hi Victory,
> >
> > I've mistakenly reverted your recent pull request[1].
> > Luckily I have restored it via the commit email message.
> > I've push it to 2.7.0-release branch already.
> > Would you please help to check it?
> >
> >
> > [1] https://github.com/apache/incubator-dubbo/pull/3263
> >
> > On Thu, Jan 17, 2019 at 5:08 PM victory 
> >> wrote:
> >>
> >> I have review the code and it work well in
> >>
> >
> >>
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> >>
> >> I have merged this pull request into 2.7.0-release.
> >>
> >> Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> >>
> >>> Hi,
> >>>
> >>> This looks like a blocking issue, I've already tagged 2.7.0, I
> >> will
> >>> wait for it and re-do the tagging.
> >>>
> >>> On Thu, Jan 17, 2019 at 2:49 PM jun 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Xin Wang]

> 2.7.0-release has just been merged into master, please help to review.

good job ,  now everyone can get the new features on the master branch

jun liu  于2019年1月22日周二 下午5:53写道：

> 2.7.0-release has just been merged into master, please help to review.
>
> Jun
>
> > On Jan 21, 2019, at 10:42 AM, Xin Wang  wrote:
> >
> >> I am merging back the 2.7.0-release branch to master to avoid having too
> > many conflicts if do it too late, then we may need to constantly do the
> > merge with every few days before vote is done.
> >
> > Support this , then everyone can review the code on the master branch ,
> > and find some issues earlier
> >
> > jun liu  于2019年1月21日周一 上午10:21写道：
> >
> >> I am merging back the 2.7.0-release branch to master to avoid having too
> >> many conflicts if do it too late, then we may need to constantly do the
> >> merge with every few days before vote is done.
> >>
> >> Jun
> >>
> >>> On Jan 18, 2019, at 2:28 PM, Huxing Zhang  wrote:
> >>>
> >>> Hi,
> >>>
> >>> I still found some inconsistency between the source release and the
> >>> Git tag dubbo-2.7.0:
> >>>
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: all
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: bom
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: dependencies-bom
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: distribution
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
> >>> Only in
> >>
> apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
> >>> work
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> >>> dubbo-demo-consumer
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> >>> dubbo-demo-provider
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
> >>> dubbo-metrics-default
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> >>> dubbo-test-benchmark
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> >>> dubbo-test-examples
> >>>
> >>> It is possibly due to my local environment, I am going to do it again
> >>> with clean checkout of Dubbo 2.7.0-release branch.
> >>>
> >>> On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang 
> wrote:
> 
>  Hi,
> 
>  I found that there is a file test.patch in source release, which was
>  the patch I used to restore the commit I reverted yesterday.
>  This is not what we want, I am going to remove this file and
> re-tagging
> >> 2.7.0.
> 
> 
>  On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang 
> wrote:
> >
> > Hi,
> >
> > On Fri, Jan 18, 2019 at 12:08 AM jun liu 
> wrote:
> >>
> >>> Jun, could you please summarize an English version of the release
> >> note.
> >>> I will send the vote email once it is done.
> >>
> >> It’s now available here:
> >>
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> >
> > Thanks for that, it looks good to me.
> >
> >> I think it’s time to prepare the upgrade guide and user docs now,
> >> which is also a key part for this release.
> >
> > Yes, we can do that while we are doing the release vote.
> >
> > I am starting the vote today.
> >>
> >> Jun
> >>
> >>> On Jan 17, 2019, at 11:58 PM, Huxing Zhang 
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> All the preparation seems going well.
> >>> I have successfully uploaded 2.7.0 to staging repo, and upload the
> >>> release candidate to svn.
> >>> I saw that the release note is still in Chinese.
> >>>
> >>> Jun, could you please summarize an English version of the release
> >> note.
> >>> I will send the vote email once it is done.
> >>>
> >>> On Thu, Jan 17, 2019 at 5:48 PM victory 
> >> wrote:
> 
>  I have check the file , it is the same as pull request #3263.
> 
> 
>  Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> 
> > Hi Victory,
> >
> > I've mistakenly reverted your recent pull request[1].
> > Luckily I have restored it via the commit email message.
> > I've push it to 2.7.0-release branch already.
> > Would you please help to check it?
> >
> >
> > [1] https://github.com/apache/incubator-dubbo/pull/3263
> >
> > On Thu, Jan 17, 2019 at 5:08 PM victory 
> >> wrote:
> >>
> >> I have review the code and it work well in
> >>
> >
> >>
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> >>
> >> I have merged this pull request into 2.7.0-release.
> >>
> >> Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> >>
> >>> Hi,
> >>>
> >>> This looks like a blocking issue, I've already tagged 2.7.0, I
> >> will
> >>> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

2.7.0-release has just been merged into master, please help to review.

Jun

> On Jan 21, 2019, at 10:42 AM, Xin Wang  wrote:
> 
>> I am merging back the 2.7.0-release branch to master to avoid having too
> many conflicts if do it too late, then we may need to constantly do the
> merge with every few days before vote is done.
> 
> Support this , then everyone can review the code on the master branch ,
> and find some issues earlier
> 
> jun liu  于2019年1月21日周一 上午10:21写道：
> 
>> I am merging back the 2.7.0-release branch to master to avoid having too
>> many conflicts if do it too late, then we may need to constantly do the
>> merge with every few days before vote is done.
>> 
>> Jun
>> 
>>> On Jan 18, 2019, at 2:28 PM, Huxing Zhang  wrote:
>>> 
>>> Hi,
>>> 
>>> I still found some inconsistency between the source release and the
>>> Git tag dubbo-2.7.0:
>>> 
>>> Only in apache-dubbo-incubating-2.7.0-source-release: all
>>> Only in apache-dubbo-incubating-2.7.0-source-release: bom
>>> Only in apache-dubbo-incubating-2.7.0-source-release: dependencies-bom
>>> Only in apache-dubbo-incubating-2.7.0-source-release: distribution
>>> Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
>>> Only in
>> apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
>>> work
>>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
>>> dubbo-demo-consumer
>>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
>>> dubbo-demo-provider
>>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
>>> dubbo-metrics-default
>>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
>>> dubbo-test-benchmark
>>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
>>> dubbo-test-examples
>>> 
>>> It is possibly due to my local environment, I am going to do it again
>>> with clean checkout of Dubbo 2.7.0-release branch.
>>> 
>>> On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang  wrote:
 
 Hi,
 
 I found that there is a file test.patch in source release, which was
 the patch I used to restore the commit I reverted yesterday.
 This is not what we want, I am going to remove this file and re-tagging
>> 2.7.0.
 
 
 On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang  wrote:
> 
> Hi,
> 
> On Fri, Jan 18, 2019 at 12:08 AM jun liu  wrote:
>> 
>>> Jun, could you please summarize an English version of the release
>> note.
>>> I will send the vote email once it is done.
>> 
>> It’s now available here:
>> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> 
> Thanks for that, it looks good to me.
> 
>> I think it’s time to prepare the upgrade guide and user docs now,
>> which is also a key part for this release.
> 
> Yes, we can do that while we are doing the release vote.
> 
> I am starting the vote today.
>> 
>> Jun
>> 
>>> On Jan 17, 2019, at 11:58 PM, Huxing Zhang 
>> wrote:
>>> 
>>> Hi,
>>> 
>>> All the preparation seems going well.
>>> I have successfully uploaded 2.7.0 to staging repo, and upload the
>>> release candidate to svn.
>>> I saw that the release note is still in Chinese.
>>> 
>>> Jun, could you please summarize an English version of the release
>> note.
>>> I will send the vote email once it is done.
>>> 
>>> On Thu, Jan 17, 2019 at 5:48 PM victory 
>> wrote:
 
 I have check the file , it is the same as pull request #3263.
 
 
 Huxing Zhang  于2019年1月17日周四 下午5:34写道：
 
> Hi Victory,
> 
> I've mistakenly reverted your recent pull request[1].
> Luckily I have restored it via the commit email message.
> I've push it to 2.7.0-release branch already.
> Would you please help to check it?
> 
> 
> [1] https://github.com/apache/incubator-dubbo/pull/3263
> 
> On Thu, Jan 17, 2019 at 5:08 PM victory 
>> wrote:
>> 
>> I have review the code and it work well in
>> 
> 
>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
>> 
>> I have merged this pull request into 2.7.0-release.
>> 
>> Huxing Zhang  于2019年1月17日周四 下午2:59写道：
>> 
>>> Hi,
>>> 
>>> This looks like a blocking issue, I've already tagged 2.7.0, I
>> will
>>> wait for it and re-do the tagging.
>>> 
>>> On Thu, Jan 17, 2019 at 2:49 PM jun liu 
>> wrote:
 
> I am seeing that all the issue has been cleaned for the 2.7.0
>>> milestone.
> It looks like all the things have been settled, I am planning
>> to
> tag
> the 2.7.0 release today.
 
 One more issue to be solved 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

On Mon, Jan 21, 2019 at 10:21 AM jun liu  wrote:
>
> I am merging back the 2.7.0-release branch to master to avoid having too many 
> conflicts if do it too late, then we may need to constantly do the merge with 
> every few days before vote is done.

Be careful that I just forcely updated 2.7.0-release, because I have
to revert the version bump commits by maven release plugin.
>
> Jun
>
> > On Jan 18, 2019, at 2:28 PM, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > I still found some inconsistency between the source release and the
> > Git tag dubbo-2.7.0:
> >
> > Only in apache-dubbo-incubating-2.7.0-source-release: all
> > Only in apache-dubbo-incubating-2.7.0-source-release: bom
> > Only in apache-dubbo-incubating-2.7.0-source-release: dependencies-bom
> > Only in apache-dubbo-incubating-2.7.0-source-release: distribution
> > Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
> > Only in 
> > apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
> > work
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> > dubbo-demo-consumer
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> > dubbo-demo-provider
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
> > dubbo-metrics-default
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> > dubbo-test-benchmark
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> > dubbo-test-examples
> >
> > It is possibly due to my local environment, I am going to do it again
> > with clean checkout of Dubbo 2.7.0-release branch.
> >
> > On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang  wrote:
> >>
> >> Hi,
> >>
> >> I found that there is a file test.patch in source release, which was
> >> the patch I used to restore the commit I reverted yesterday.
> >> This is not what we want, I am going to remove this file and re-tagging 
> >> 2.7.0.
> >>
> >>
> >> On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang  wrote:
> >>>
> >>> Hi,
> >>>
> >>> On Fri, Jan 18, 2019 at 12:08 AM jun liu  wrote:
> 
> > Jun, could you please summarize an English version of the release note.
> > I will send the vote email once it is done.
> 
>  It’s now available here: 
>  https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> >>>
> >>> Thanks for that, it looks good to me.
> >>>
>  I think it’s time to prepare the upgrade guide and user docs now, which 
>  is also a key part for this release.
> >>>
> >>> Yes, we can do that while we are doing the release vote.
> >>>
> >>> I am starting the vote today.
> 
>  Jun
> 
> > On Jan 17, 2019, at 11:58 PM, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > All the preparation seems going well.
> > I have successfully uploaded 2.7.0 to staging repo, and upload the
> > release candidate to svn.
> > I saw that the release note is still in Chinese.
> >
> > Jun, could you please summarize an English version of the release note.
> > I will send the vote email once it is done.
> >
> > On Thu, Jan 17, 2019 at 5:48 PM victory  wrote:
> >>
> >> I have check the file , it is the same as pull request #3263.
> >>
> >>
> >> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> >>
> >>> Hi Victory,
> >>>
> >>> I've mistakenly reverted your recent pull request[1].
> >>> Luckily I have restored it via the commit email message.
> >>> I've push it to 2.7.0-release branch already.
> >>> Would you please help to check it?
> >>>
> >>>
> >>> [1] https://github.com/apache/incubator-dubbo/pull/3263
> >>>
> >>> On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
> 
>  I have review the code and it work well in
> 
> >>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> 
>  I have merged this pull request into 2.7.0-release.
> 
>  Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> 
> > Hi,
> >
> > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > wait for it and re-do the tagging.
> >
> > On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> >>
> >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> >>> It looks like all the things have been settled, I am planning to
> >>> tag
> >>> the 2.7.0 release today.
> >>
> >> One more issue to be solved before vote.
> >> Thanks to the suggestions from the Apollo[1] community, I 
> >> submitted a
> > PR[2] to polish the Apollo extension. Please help to review.
> >>
> >> 1. https://github.com/ctripcorp/apollo
> >> 2. https://github.com/apache/incubator-dubbo/pull/3263
> >>
> >> Jun
> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Yuhao Bi]

To avoid unnecessary problem brought by merging branches.
Should we use a git branch model, or we already have one?
AFAIK there are several well-known branch model, like Github flow, Gitlab
flow, Git flow, Atlassian workflow.
They all have there own pros and cons.
Should we stick with one of these branch models?

Thanks,
Yuhao

Xin Wang  于2019年1月21日周一 上午10:42写道：

> >  I am merging back the 2.7.0-release branch to master to avoid having too
> many conflicts if do it too late, then we may need to constantly do the
> merge with every few days before vote is done.
>
> Support this , then everyone can review the code on the master branch ,
> and find some issues earlier
>
> jun liu  于2019年1月21日周一 上午10:21写道：
>
> > I am merging back the 2.7.0-release branch to master to avoid having too
> > many conflicts if do it too late, then we may need to constantly do the
> > merge with every few days before vote is done.
> >
> > Jun
> >
> > > On Jan 18, 2019, at 2:28 PM, Huxing Zhang  wrote:
> > >
> > > Hi,
> > >
> > > I still found some inconsistency between the source release and the
> > > Git tag dubbo-2.7.0:
> > >
> > > Only in apache-dubbo-incubating-2.7.0-source-release: all
> > > Only in apache-dubbo-incubating-2.7.0-source-release: bom
> > > Only in apache-dubbo-incubating-2.7.0-source-release: dependencies-bom
> > > Only in apache-dubbo-incubating-2.7.0-source-release: distribution
> > > Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
> > > Only in
> >
> apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
> > > work
> > > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> > > dubbo-demo-consumer
> > > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> > > dubbo-demo-provider
> > > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
> > > dubbo-metrics-default
> > > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> > > dubbo-test-benchmark
> > > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> > > dubbo-test-examples
> > >
> > > It is possibly due to my local environment, I am going to do it again
> > > with clean checkout of Dubbo 2.7.0-release branch.
> > >
> > > On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang 
> wrote:
> > >>
> > >> Hi,
> > >>
> > >> I found that there is a file test.patch in source release, which was
> > >> the patch I used to restore the commit I reverted yesterday.
> > >> This is not what we want, I am going to remove this file and
> re-tagging
> > 2.7.0.
> > >>
> > >>
> > >> On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang 
> wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> On Fri, Jan 18, 2019 at 12:08 AM jun liu 
> wrote:
> > 
> > > Jun, could you please summarize an English version of the release
> > note.
> > > I will send the vote email once it is done.
> > 
> >  It’s now available here:
> >
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> > >>>
> > >>> Thanks for that, it looks good to me.
> > >>>
> >  I think it’s time to prepare the upgrade guide and user docs now,
> > which is also a key part for this release.
> > >>>
> > >>> Yes, we can do that while we are doing the release vote.
> > >>>
> > >>> I am starting the vote today.
> > 
> >  Jun
> > 
> > > On Jan 17, 2019, at 11:58 PM, Huxing Zhang 
> > wrote:
> > >
> > > Hi,
> > >
> > > All the preparation seems going well.
> > > I have successfully uploaded 2.7.0 to staging repo, and upload the
> > > release candidate to svn.
> > > I saw that the release note is still in Chinese.
> > >
> > > Jun, could you please summarize an English version of the release
> > note.
> > > I will send the vote email once it is done.
> > >
> > > On Thu, Jan 17, 2019 at 5:48 PM victory 
> > wrote:
> > >>
> > >> I have check the file , it is the same as pull request #3263.
> > >>
> > >>
> > >> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> > >>
> > >>> Hi Victory,
> > >>>
> > >>> I've mistakenly reverted your recent pull request[1].
> > >>> Luckily I have restored it via the commit email message.
> > >>> I've push it to 2.7.0-release branch already.
> > >>> Would you please help to check it?
> > >>>
> > >>>
> > >>> [1] https://github.com/apache/incubator-dubbo/pull/3263
> > >>>
> > >>> On Thu, Jan 17, 2019 at 5:08 PM victory 
> > wrote:
> > 
> >  I have review the code and it work well in
> > 
> > >>>
> >
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> > 
> >  I have merged this pull request into 2.7.0-release.
> > 
> >  Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> > 
> > > Hi,
> > >
> > > This looks like a blocking issue, I've already tagged 2.7.0, I
> > will

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Xin Wang]

>  I am merging back the 2.7.0-release branch to master to avoid having too
many conflicts if do it too late, then we may need to constantly do the
merge with every few days before vote is done.

Support this , then everyone can review the code on the master branch ,
and find some issues earlier

jun liu  于2019年1月21日周一 上午10:21写道：

> I am merging back the 2.7.0-release branch to master to avoid having too
> many conflicts if do it too late, then we may need to constantly do the
> merge with every few days before vote is done.
>
> Jun
>
> > On Jan 18, 2019, at 2:28 PM, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > I still found some inconsistency between the source release and the
> > Git tag dubbo-2.7.0:
> >
> > Only in apache-dubbo-incubating-2.7.0-source-release: all
> > Only in apache-dubbo-incubating-2.7.0-source-release: bom
> > Only in apache-dubbo-incubating-2.7.0-source-release: dependencies-bom
> > Only in apache-dubbo-incubating-2.7.0-source-release: distribution
> > Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
> > Only in
> apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
> > work
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> > dubbo-demo-consumer
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> > dubbo-demo-provider
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
> > dubbo-metrics-default
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> > dubbo-test-benchmark
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> > dubbo-test-examples
> >
> > It is possibly due to my local environment, I am going to do it again
> > with clean checkout of Dubbo 2.7.0-release branch.
> >
> > On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang  wrote:
> >>
> >> Hi,
> >>
> >> I found that there is a file test.patch in source release, which was
> >> the patch I used to restore the commit I reverted yesterday.
> >> This is not what we want, I am going to remove this file and re-tagging
> 2.7.0.
> >>
> >>
> >> On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang  wrote:
> >>>
> >>> Hi,
> >>>
> >>> On Fri, Jan 18, 2019 at 12:08 AM jun liu  wrote:
> 
> > Jun, could you please summarize an English version of the release
> note.
> > I will send the vote email once it is done.
> 
>  It’s now available here:
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> >>>
> >>> Thanks for that, it looks good to me.
> >>>
>  I think it’s time to prepare the upgrade guide and user docs now,
> which is also a key part for this release.
> >>>
> >>> Yes, we can do that while we are doing the release vote.
> >>>
> >>> I am starting the vote today.
> 
>  Jun
> 
> > On Jan 17, 2019, at 11:58 PM, Huxing Zhang 
> wrote:
> >
> > Hi,
> >
> > All the preparation seems going well.
> > I have successfully uploaded 2.7.0 to staging repo, and upload the
> > release candidate to svn.
> > I saw that the release note is still in Chinese.
> >
> > Jun, could you please summarize an English version of the release
> note.
> > I will send the vote email once it is done.
> >
> > On Thu, Jan 17, 2019 at 5:48 PM victory 
> wrote:
> >>
> >> I have check the file , it is the same as pull request #3263.
> >>
> >>
> >> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> >>
> >>> Hi Victory,
> >>>
> >>> I've mistakenly reverted your recent pull request[1].
> >>> Luckily I have restored it via the commit email message.
> >>> I've push it to 2.7.0-release branch already.
> >>> Would you please help to check it?
> >>>
> >>>
> >>> [1] https://github.com/apache/incubator-dubbo/pull/3263
> >>>
> >>> On Thu, Jan 17, 2019 at 5:08 PM victory 
> wrote:
> 
>  I have review the code and it work well in
> 
> >>>
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> 
>  I have merged this pull request into 2.7.0-release.
> 
>  Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> 
> > Hi,
> >
> > This looks like a blocking issue, I've already tagged 2.7.0, I
> will
> > wait for it and re-do the tagging.
> >
> > On Thu, Jan 17, 2019 at 2:49 PM jun liu 
> wrote:
> >>
> >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> >>> It looks like all the things have been settled, I am planning
> to
> >>> tag
> >>> the 2.7.0 release today.
> >>
> >> One more issue to be solved before vote.
> >> Thanks to the suggestions from the Apollo[1] community, I
> submitted a
> > PR[2] to polish the Apollo extension. Please help to review.
> >>
> >> 1. 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

I am merging back the 2.7.0-release branch to master to avoid having too many 
conflicts if do it too late, then we may need to constantly do the merge with 
every few days before vote is done.

Jun 

> On Jan 18, 2019, at 2:28 PM, Huxing Zhang  wrote:
> 
> Hi,
> 
> I still found some inconsistency between the source release and the
> Git tag dubbo-2.7.0:
> 
> Only in apache-dubbo-incubating-2.7.0-source-release: all
> Only in apache-dubbo-incubating-2.7.0-source-release: bom
> Only in apache-dubbo-incubating-2.7.0-source-release: dependencies-bom
> Only in apache-dubbo-incubating-2.7.0-source-release: distribution
> Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
> Only in 
> apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
> work
> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> dubbo-demo-consumer
> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> dubbo-demo-provider
> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
> dubbo-metrics-default
> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> dubbo-test-benchmark
> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> dubbo-test-examples
> 
> It is possibly due to my local environment, I am going to do it again
> with clean checkout of Dubbo 2.7.0-release branch.
> 
> On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang  wrote:
>> 
>> Hi,
>> 
>> I found that there is a file test.patch in source release, which was
>> the patch I used to restore the commit I reverted yesterday.
>> This is not what we want, I am going to remove this file and re-tagging 
>> 2.7.0.
>> 
>> 
>> On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang  wrote:
>>> 
>>> Hi,
>>> 
>>> On Fri, Jan 18, 2019 at 12:08 AM jun liu  wrote:
 
> Jun, could you please summarize an English version of the release note.
> I will send the vote email once it is done.
 
 It’s now available here: 
 https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
>>> 
>>> Thanks for that, it looks good to me.
>>> 
 I think it’s time to prepare the upgrade guide and user docs now, which is 
 also a key part for this release.
>>> 
>>> Yes, we can do that while we are doing the release vote.
>>> 
>>> I am starting the vote today.
 
 Jun
 
> On Jan 17, 2019, at 11:58 PM, Huxing Zhang  wrote:
> 
> Hi,
> 
> All the preparation seems going well.
> I have successfully uploaded 2.7.0 to staging repo, and upload the
> release candidate to svn.
> I saw that the release note is still in Chinese.
> 
> Jun, could you please summarize an English version of the release note.
> I will send the vote email once it is done.
> 
> On Thu, Jan 17, 2019 at 5:48 PM victory  wrote:
>> 
>> I have check the file , it is the same as pull request #3263.
>> 
>> 
>> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
>> 
>>> Hi Victory,
>>> 
>>> I've mistakenly reverted your recent pull request[1].
>>> Luckily I have restored it via the commit email message.
>>> I've push it to 2.7.0-release branch already.
>>> Would you please help to check it?
>>> 
>>> 
>>> [1] https://github.com/apache/incubator-dubbo/pull/3263
>>> 
>>> On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
 
 I have review the code and it work well in
 
>>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
 
 I have merged this pull request into 2.7.0-release.
 
 Huxing Zhang  于2019年1月17日周四 下午2:59写道：
 
> Hi,
> 
> This looks like a blocking issue, I've already tagged 2.7.0, I will
> wait for it and re-do the tagging.
> 
> On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
>> 
>>> I am seeing that all the issue has been cleaned for the 2.7.0
> milestone.
>>> It looks like all the things have been settled, I am planning to
>>> tag
>>> the 2.7.0 release today.
>> 
>> One more issue to be solved before vote.
>> Thanks to the suggestions from the Apollo[1] community, I submitted a
> PR[2] to polish the Apollo extension. Please help to review.
>> 
>> 1. https://github.com/ctripcorp/apollo
>> 2. https://github.com/apache/incubator-dubbo/pull/3263
>> 
>> Jun
>> 
>>> On Jan 17, 2019, at 10:41 AM, Huxing Zhang 
>>> wrote:
>>> 
>>> Hi All,
>>> 
>>> I am seeing that all the issue has been cleaned for the 2.7.0
> milestone.
>>> It looks like all the things have been settled, I am planning to
>>> tag
>>> the 2.7.0 release today.
>>> 
>>> dubbo-ops and dubbo-spring-boot-project 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

I still found some inconsistency between the source release and the
Git tag dubbo-2.7.0:

Only in apache-dubbo-incubating-2.7.0-source-release: all
Only in apache-dubbo-incubating-2.7.0-source-release: bom
Only in apache-dubbo-incubating-2.7.0-source-release: dependencies-bom
Only in apache-dubbo-incubating-2.7.0-source-release: distribution
Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
Only in 
apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
work
Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
dubbo-demo-consumer
Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
dubbo-demo-provider
Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
dubbo-metrics-default
Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
dubbo-test-benchmark
Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
dubbo-test-examples

It is possibly due to my local environment, I am going to do it again
with clean checkout of Dubbo 2.7.0-release branch.

On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang  wrote:
>
> Hi,
>
> I found that there is a file test.patch in source release, which was
> the patch I used to restore the commit I reverted yesterday.
> This is not what we want, I am going to remove this file and re-tagging 2.7.0.
>
>
> On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang  wrote:
> >
> > Hi,
> >
> > On Fri, Jan 18, 2019 at 12:08 AM jun liu  wrote:
> > >
> > > > Jun, could you please summarize an English version of the release note.
> > > > I will send the vote email once it is done.
> > >
> > > It’s now available here: 
> > > https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> >
> > Thanks for that, it looks good to me.
> >
> > > I think it’s time to prepare the upgrade guide and user docs now, which 
> > > is also a key part for this release.
> >
> > Yes, we can do that while we are doing the release vote.
> >
> > I am starting the vote today.
> > >
> > > Jun
> > >
> > > > On Jan 17, 2019, at 11:58 PM, Huxing Zhang  wrote:
> > > >
> > > > Hi,
> > > >
> > > > All the preparation seems going well.
> > > > I have successfully uploaded 2.7.0 to staging repo, and upload the
> > > > release candidate to svn.
> > > > I saw that the release note is still in Chinese.
> > > >
> > > > Jun, could you please summarize an English version of the release note.
> > > > I will send the vote email once it is done.
> > > >
> > > > On Thu, Jan 17, 2019 at 5:48 PM victory  wrote:
> > > >>
> > > >> I have check the file , it is the same as pull request #3263.
> > > >>
> > > >>
> > > >> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> > > >>
> > > >>> Hi Victory,
> > > >>>
> > > >>> I've mistakenly reverted your recent pull request[1].
> > > >>> Luckily I have restored it via the commit email message.
> > > >>> I've push it to 2.7.0-release branch already.
> > > >>> Would you please help to check it?
> > > >>>
> > > >>>
> > > >>> [1] https://github.com/apache/incubator-dubbo/pull/3263
> > > >>>
> > > >>> On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
> > > 
> > >  I have review the code and it work well in
> > > 
> > > >>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> > > 
> > >  I have merged this pull request into 2.7.0-release.
> > > 
> > >  Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> > > 
> > > > Hi,
> > > >
> > > > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > > > wait for it and re-do the tagging.
> > > >
> > > > On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> > > >>
> > > >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > > > milestone.
> > > >>> It looks like all the things have been settled, I am planning to
> > > >>> tag
> > > >>> the 2.7.0 release today.
> > > >>
> > > >> One more issue to be solved before vote.
> > > >> Thanks to the suggestions from the Apollo[1] community, I 
> > > >> submitted a
> > > > PR[2] to polish the Apollo extension. Please help to review.
> > > >>
> > > >> 1. https://github.com/ctripcorp/apollo
> > > >> 2. https://github.com/apache/incubator-dubbo/pull/3263
> > > >>
> > > >> Jun
> > > >>
> > > >>> On Jan 17, 2019, at 10:41 AM, Huxing Zhang 
> > > >>> wrote:
> > > >>>
> > > >>> Hi All,
> > > >>>
> > > >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > > > milestone.
> > > >>> It looks like all the things have been settled, I am planning to
> > > >>> tag
> > > >>> the 2.7.0 release today.
> > > >>>
> > > >>> dubbo-ops and dubbo-spring-boot-project should be released after
> > > >>> Dubbo
> > > >>> 2.7.0 release.
> > > >>>
> > > >>> On Wed, Jan 16, 2019 at 5:02 PM jun liu  > > >>>  > > > ken.lj...@gmail.com>> wrote:
> > > 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

I found that there is a file test.patch in source release, which was
the patch I used to restore the commit I reverted yesterday.
This is not what we want, I am going to remove this file and re-tagging 2.7.0.


On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang  wrote:
>
> Hi,
>
> On Fri, Jan 18, 2019 at 12:08 AM jun liu  wrote:
> >
> > > Jun, could you please summarize an English version of the release note.
> > > I will send the vote email once it is done.
> >
> > It’s now available here: 
> > https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
>
> Thanks for that, it looks good to me.
>
> > I think it’s time to prepare the upgrade guide and user docs now, which is 
> > also a key part for this release.
>
> Yes, we can do that while we are doing the release vote.
>
> I am starting the vote today.
> >
> > Jun
> >
> > > On Jan 17, 2019, at 11:58 PM, Huxing Zhang  wrote:
> > >
> > > Hi,
> > >
> > > All the preparation seems going well.
> > > I have successfully uploaded 2.7.0 to staging repo, and upload the
> > > release candidate to svn.
> > > I saw that the release note is still in Chinese.
> > >
> > > Jun, could you please summarize an English version of the release note.
> > > I will send the vote email once it is done.
> > >
> > > On Thu, Jan 17, 2019 at 5:48 PM victory  wrote:
> > >>
> > >> I have check the file , it is the same as pull request #3263.
> > >>
> > >>
> > >> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> > >>
> > >>> Hi Victory,
> > >>>
> > >>> I've mistakenly reverted your recent pull request[1].
> > >>> Luckily I have restored it via the commit email message.
> > >>> I've push it to 2.7.0-release branch already.
> > >>> Would you please help to check it?
> > >>>
> > >>>
> > >>> [1] https://github.com/apache/incubator-dubbo/pull/3263
> > >>>
> > >>> On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
> > 
> >  I have review the code and it work well in
> > 
> > >>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> > 
> >  I have merged this pull request into 2.7.0-release.
> > 
> >  Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> > 
> > > Hi,
> > >
> > > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > > wait for it and re-do the tagging.
> > >
> > > On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> > >>
> > >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > > milestone.
> > >>> It looks like all the things have been settled, I am planning to
> > >>> tag
> > >>> the 2.7.0 release today.
> > >>
> > >> One more issue to be solved before vote.
> > >> Thanks to the suggestions from the Apollo[1] community, I submitted a
> > > PR[2] to polish the Apollo extension. Please help to review.
> > >>
> > >> 1. https://github.com/ctripcorp/apollo
> > >> 2. https://github.com/apache/incubator-dubbo/pull/3263
> > >>
> > >> Jun
> > >>
> > >>> On Jan 17, 2019, at 10:41 AM, Huxing Zhang 
> > >>> wrote:
> > >>>
> > >>> Hi All,
> > >>>
> > >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > > milestone.
> > >>> It looks like all the things have been settled, I am planning to
> > >>> tag
> > >>> the 2.7.0 release today.
> > >>>
> > >>> dubbo-ops and dubbo-spring-boot-project should be released after
> > >>> Dubbo
> > >>> 2.7.0 release.
> > >>>
> > >>> On Wed, Jan 16, 2019 at 5:02 PM jun liu  > >>>  > > ken.lj...@gmail.com>> wrote:
> > 
> > > There is no need to shade gson into dubbo.jar, just need depency
> > >>> gson
> > > library.
> > >
> > > I have fixed it .
> > > https://github.com/apache/incubator-dubbo/pull/3246 <
> > > https://github.com/apache/incubator-dubbo/pull/3246> <
> > > https://github.com/apache/incubator-dubbo/pull/3246 <
> > > https://github.com/apache/incubator-dubbo/pull/3246>>
> >  Agree.
> > 
> >  Well done,  merged.
> > 
> >  Jun
> > 
> > > On Jan 16, 2019, at 4:15 PM, victory 
> > >>> wrote:
> > >
> > > There is no need to shade gson into dubbo.jar, just need depency
> > >>> gson
> > > library.
> > >
> > > I have fixed it .
> > > https://github.com/apache/incubator-dubbo/pull/3246
> > >
> > > Ian Luo  于2019年1月16日周三 下午2:34写道：
> > >
> > >> We should not shade gson binaries into dubbo all in one jar
> > >>> file,
> > > even
> > >> though there's no license issue. It is simply we should not do
> > >>> this,
> > >> instead, we should make sure dubbo all in one jar should have a
> > > transitive
> > >> dependency to gson library.
> > >>
> > >> I noticed it's caused
> > > by'com.google.code.gson:gson' in
> > >> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Ian Luo]

The release note looks nice. Now let's wait for the vote.

Cheers,
-Ian.

On Fri, Jan 18, 2019 at 9:48 AM Huxing Zhang  wrote:

> Hi,
>
> On Fri, Jan 18, 2019 at 12:08 AM jun liu  wrote:
> >
> > > Jun, could you please summarize an English version of the release note.
> > > I will send the vote email once it is done.
> >
> > It’s now available here:
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
>
> Thanks for that, it looks good to me.
>
> > I think it’s time to prepare the upgrade guide and user docs now, which
> is also a key part for this release.
>
> Yes, we can do that while we are doing the release vote.
>
> I am starting the vote today.
> >
> > Jun
> >
> > > On Jan 17, 2019, at 11:58 PM, Huxing Zhang  wrote:
> > >
> > > Hi,
> > >
> > > All the preparation seems going well.
> > > I have successfully uploaded 2.7.0 to staging repo, and upload the
> > > release candidate to svn.
> > > I saw that the release note is still in Chinese.
> > >
> > > Jun, could you please summarize an English version of the release note.
> > > I will send the vote email once it is done.
> > >
> > > On Thu, Jan 17, 2019 at 5:48 PM victory  wrote:
> > >>
> > >> I have check the file , it is the same as pull request #3263.
> > >>
> > >>
> > >> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> > >>
> > >>> Hi Victory,
> > >>>
> > >>> I've mistakenly reverted your recent pull request[1].
> > >>> Luckily I have restored it via the commit email message.
> > >>> I've push it to 2.7.0-release branch already.
> > >>> Would you please help to check it?
> > >>>
> > >>>
> > >>> [1] https://github.com/apache/incubator-dubbo/pull/3263
> > >>>
> > >>> On Thu, Jan 17, 2019 at 5:08 PM victory 
> wrote:
> > 
> >  I have review the code and it work well in
> > 
> > >>>
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> > 
> >  I have merged this pull request into 2.7.0-release.
> > 
> >  Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> > 
> > > Hi,
> > >
> > > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > > wait for it and re-do the tagging.
> > >
> > > On Thu, Jan 17, 2019 at 2:49 PM jun liu 
> wrote:
> > >>
> > >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > > milestone.
> > >>> It looks like all the things have been settled, I am planning to
> > >>> tag
> > >>> the 2.7.0 release today.
> > >>
> > >> One more issue to be solved before vote.
> > >> Thanks to the suggestions from the Apollo[1] community, I
> submitted a
> > > PR[2] to polish the Apollo extension. Please help to review.
> > >>
> > >> 1. https://github.com/ctripcorp/apollo
> > >> 2. https://github.com/apache/incubator-dubbo/pull/3263
> > >>
> > >> Jun
> > >>
> > >>> On Jan 17, 2019, at 10:41 AM, Huxing Zhang 
> > >>> wrote:
> > >>>
> > >>> Hi All,
> > >>>
> > >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > > milestone.
> > >>> It looks like all the things have been settled, I am planning to
> > >>> tag
> > >>> the 2.7.0 release today.
> > >>>
> > >>> dubbo-ops and dubbo-spring-boot-project should be released after
> > >>> Dubbo
> > >>> 2.7.0 release.
> > >>>
> > >>> On Wed, Jan 16, 2019 at 5:02 PM jun liu  > >>>  > > ken.lj...@gmail.com>> wrote:
> > 
> > > There is no need to shade gson into dubbo.jar, just need
> depency
> > >>> gson
> > > library.
> > >
> > > I have fixed it .
> > > https://github.com/apache/incubator-dubbo/pull/3246 <
> > > https://github.com/apache/incubator-dubbo/pull/3246> <
> > > https://github.com/apache/incubator-dubbo/pull/3246 <
> > > https://github.com/apache/incubator-dubbo/pull/3246>>
> >  Agree.
> > 
> >  Well done,  merged.
> > 
> >  Jun
> > 
> > > On Jan 16, 2019, at 4:15 PM, victory 
> > >>> wrote:
> > >
> > > There is no need to shade gson into dubbo.jar, just need
> depency
> > >>> gson
> > > library.
> > >
> > > I have fixed it .
> > > https://github.com/apache/incubator-dubbo/pull/3246
> > >
> > > Ian Luo  于2019年1月16日周三 下午2:34写道：
> > >
> > >> We should not shade gson binaries into dubbo all in one jar
> > >>> file,
> > > even
> > >> though there's no license issue. It is simply we should not do
> > >>> this,
> > >> instead, we should make sure dubbo all in one jar should have
> a
> > > transitive
> > >> dependency to gson library.
> > >>
> > >> I noticed it's caused
> > > by'com.google.code.gson:gson' in
> > >> dubbo-all/pom.xml. We should fix it.
> > >>
> > >> Thanks,
> > >> -Ian.
> > >>
> > >>
> > >> On 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

On Fri, Jan 18, 2019 at 12:08 AM jun liu  wrote:
>
> > Jun, could you please summarize an English version of the release note.
> > I will send the vote email once it is done.
>
> It’s now available here: 
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270

Thanks for that, it looks good to me.

> I think it’s time to prepare the upgrade guide and user docs now, which is 
> also a key part for this release.

Yes, we can do that while we are doing the release vote.

I am starting the vote today.
>
> Jun
>
> > On Jan 17, 2019, at 11:58 PM, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > All the preparation seems going well.
> > I have successfully uploaded 2.7.0 to staging repo, and upload the
> > release candidate to svn.
> > I saw that the release note is still in Chinese.
> >
> > Jun, could you please summarize an English version of the release note.
> > I will send the vote email once it is done.
> >
> > On Thu, Jan 17, 2019 at 5:48 PM victory  wrote:
> >>
> >> I have check the file , it is the same as pull request #3263.
> >>
> >>
> >> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> >>
> >>> Hi Victory,
> >>>
> >>> I've mistakenly reverted your recent pull request[1].
> >>> Luckily I have restored it via the commit email message.
> >>> I've push it to 2.7.0-release branch already.
> >>> Would you please help to check it?
> >>>
> >>>
> >>> [1] https://github.com/apache/incubator-dubbo/pull/3263
> >>>
> >>> On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
> 
>  I have review the code and it work well in
> 
> >>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> 
>  I have merged this pull request into 2.7.0-release.
> 
>  Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> 
> > Hi,
> >
> > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > wait for it and re-do the tagging.
> >
> > On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> >>
> >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> >>> It looks like all the things have been settled, I am planning to
> >>> tag
> >>> the 2.7.0 release today.
> >>
> >> One more issue to be solved before vote.
> >> Thanks to the suggestions from the Apollo[1] community, I submitted a
> > PR[2] to polish the Apollo extension. Please help to review.
> >>
> >> 1. https://github.com/ctripcorp/apollo
> >> 2. https://github.com/apache/incubator-dubbo/pull/3263
> >>
> >> Jun
> >>
> >>> On Jan 17, 2019, at 10:41 AM, Huxing Zhang 
> >>> wrote:
> >>>
> >>> Hi All,
> >>>
> >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> >>> It looks like all the things have been settled, I am planning to
> >>> tag
> >>> the 2.7.0 release today.
> >>>
> >>> dubbo-ops and dubbo-spring-boot-project should be released after
> >>> Dubbo
> >>> 2.7.0 release.
> >>>
> >>> On Wed, Jan 16, 2019 at 5:02 PM jun liu  >>>  > ken.lj...@gmail.com>> wrote:
> 
> > There is no need to shade gson into dubbo.jar, just need depency
> >>> gson
> > library.
> >
> > I have fixed it .
> > https://github.com/apache/incubator-dubbo/pull/3246 <
> > https://github.com/apache/incubator-dubbo/pull/3246> <
> > https://github.com/apache/incubator-dubbo/pull/3246 <
> > https://github.com/apache/incubator-dubbo/pull/3246>>
>  Agree.
> 
>  Well done,  merged.
> 
>  Jun
> 
> > On Jan 16, 2019, at 4:15 PM, victory 
> >>> wrote:
> >
> > There is no need to shade gson into dubbo.jar, just need depency
> >>> gson
> > library.
> >
> > I have fixed it .
> > https://github.com/apache/incubator-dubbo/pull/3246
> >
> > Ian Luo  于2019年1月16日周三 下午2:34写道：
> >
> >> We should not shade gson binaries into dubbo all in one jar
> >>> file,
> > even
> >> though there's no license issue. It is simply we should not do
> >>> this,
> >> instead, we should make sure dubbo all in one jar should have a
> > transitive
> >> dependency to gson library.
> >>
> >> I noticed it's caused
> > by'com.google.code.gson:gson' in
> >> dubbo-all/pom.xml. We should fix it.
> >>
> >> Thanks,
> >> -Ian.
> >>
> >>
> >> On Tue, Jan 15, 2019 at 5:16 PM jun liu 
> > wrote:
> >>
> >>> I noticed that a third-party source code ‘com.google <
> > http://com.google/
> >>> .gson.*’
> >>> has been compiled into the convenient maven binary jar of
> >>> 2.7.0 -
> >>> dubbo-2.7.0.jar :
> >>>
> >>> .
> >>> ├── META-INF
> >>> │   ├── DEPENDENCIES
> >>> │   ├── 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Xin Wang]

good job

jun liu  于 2019年1月18日周五 上午12:08写道：

> > Jun, could you please summarize an English version of the release note.
> > I will send the vote email once it is done.
>
> It’s now available here:
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> I think it’s time to prepare the upgrade guide and user docs now, which is
> also a key part for this release.
>
> Jun
>
> > On Jan 17, 2019, at 11:58 PM, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > All the preparation seems going well.
> > I have successfully uploaded 2.7.0 to staging repo, and upload the
> > release candidate to svn.
> > I saw that the release note is still in Chinese.
> >
> > Jun, could you please summarize an English version of the release note.
> > I will send the vote email once it is done.
> >
> > On Thu, Jan 17, 2019 at 5:48 PM victory  wrote:
> >>
> >> I have check the file , it is the same as pull request #3263.
> >>
> >>
> >> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> >>
> >>> Hi Victory,
> >>>
> >>> I've mistakenly reverted your recent pull request[1].
> >>> Luckily I have restored it via the commit email message.
> >>> I've push it to 2.7.0-release branch already.
> >>> Would you please help to check it?
> >>>
> >>>
> >>> [1] https://github.com/apache/incubator-dubbo/pull/3263
> >>>
> >>> On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
> 
>  I have review the code and it work well in
> 
> >>>
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> 
>  I have merged this pull request into 2.7.0-release.
> 
>  Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> 
> > Hi,
> >
> > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > wait for it and re-do the tagging.
> >
> > On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> >>
> >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> >>> It looks like all the things have been settled, I am planning to
> >>> tag
> >>> the 2.7.0 release today.
> >>
> >> One more issue to be solved before vote.
> >> Thanks to the suggestions from the Apollo[1] community, I submitted
> a
> > PR[2] to polish the Apollo extension. Please help to review.
> >>
> >> 1. https://github.com/ctripcorp/apollo
> >> 2. https://github.com/apache/incubator-dubbo/pull/3263
> >>
> >> Jun
> >>
> >>> On Jan 17, 2019, at 10:41 AM, Huxing Zhang 
> >>> wrote:
> >>>
> >>> Hi All,
> >>>
> >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> >>> It looks like all the things have been settled, I am planning to
> >>> tag
> >>> the 2.7.0 release today.
> >>>
> >>> dubbo-ops and dubbo-spring-boot-project should be released after
> >>> Dubbo
> >>> 2.7.0 release.
> >>>
> >>> On Wed, Jan 16, 2019 at 5:02 PM jun liu  >>>  > ken.lj...@gmail.com>> wrote:
> 
> > There is no need to shade gson into dubbo.jar, just need depency
> >>> gson
> > library.
> >
> > I have fixed it .
> > https://github.com/apache/incubator-dubbo/pull/3246 <
> > https://github.com/apache/incubator-dubbo/pull/3246> <
> > https://github.com/apache/incubator-dubbo/pull/3246 <
> > https://github.com/apache/incubator-dubbo/pull/3246>>
>  Agree.
> 
>  Well done,  merged.
> 
>  Jun
> 
> > On Jan 16, 2019, at 4:15 PM, victory 
> >>> wrote:
> >
> > There is no need to shade gson into dubbo.jar, just need depency
> >>> gson
> > library.
> >
> > I have fixed it .
> > https://github.com/apache/incubator-dubbo/pull/3246
> >
> > Ian Luo  于2019年1月16日周三 下午2:34写道：
> >
> >> We should not shade gson binaries into dubbo all in one jar
> >>> file,
> > even
> >> though there's no license issue. It is simply we should not do
> >>> this,
> >> instead, we should make sure dubbo all in one jar should have a
> > transitive
> >> dependency to gson library.
> >>
> >> I noticed it's caused
> > by'com.google.code.gson:gson' in
> >> dubbo-all/pom.xml. We should fix it.
> >>
> >> Thanks,
> >> -Ian.
> >>
> >>
> >> On Tue, Jan 15, 2019 at 5:16 PM jun liu 
> > wrote:
> >>
> >>> I noticed that a third-party source code ‘com.google <
> > http://com.google/
> >>> .gson.*’
> >>> has been compiled into the convenient maven binary jar of
> >>> 2.7.0 -
> >>> dubbo-2.7.0.jar :
> >>>
> >>> .
> >>> ├── META-INF
> >>> │   ├── DEPENDENCIES
> >>> │   ├── LICENSE
> >>> │   ├── MANIFEST.MF
> >>> │   ├── NOTICE
> >>> │   ├── assembly
> >>> │   │   └── bin
> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

> Jun, could you please summarize an English version of the release note.
> I will send the vote email once it is done.

It’s now available here: 
https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
I think it’s time to prepare the upgrade guide and user docs now, which is also 
a key part for this release.

Jun

> On Jan 17, 2019, at 11:58 PM, Huxing Zhang  wrote:
> 
> Hi,
> 
> All the preparation seems going well.
> I have successfully uploaded 2.7.0 to staging repo, and upload the
> release candidate to svn.
> I saw that the release note is still in Chinese.
> 
> Jun, could you please summarize an English version of the release note.
> I will send the vote email once it is done.
> 
> On Thu, Jan 17, 2019 at 5:48 PM victory  wrote:
>> 
>> I have check the file , it is the same as pull request #3263.
>> 
>> 
>> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
>> 
>>> Hi Victory,
>>> 
>>> I've mistakenly reverted your recent pull request[1].
>>> Luckily I have restored it via the commit email message.
>>> I've push it to 2.7.0-release branch already.
>>> Would you please help to check it?
>>> 
>>> 
>>> [1] https://github.com/apache/incubator-dubbo/pull/3263
>>> 
>>> On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
 
 I have review the code and it work well in
 
>>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
 
 I have merged this pull request into 2.7.0-release.
 
 Huxing Zhang  于2019年1月17日周四 下午2:59写道：
 
> Hi,
> 
> This looks like a blocking issue, I've already tagged 2.7.0, I will
> wait for it and re-do the tagging.
> 
> On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
>> 
>>> I am seeing that all the issue has been cleaned for the 2.7.0
> milestone.
>>> It looks like all the things have been settled, I am planning to
>>> tag
>>> the 2.7.0 release today.
>> 
>> One more issue to be solved before vote.
>> Thanks to the suggestions from the Apollo[1] community, I submitted a
> PR[2] to polish the Apollo extension. Please help to review.
>> 
>> 1. https://github.com/ctripcorp/apollo
>> 2. https://github.com/apache/incubator-dubbo/pull/3263
>> 
>> Jun
>> 
>>> On Jan 17, 2019, at 10:41 AM, Huxing Zhang 
>>> wrote:
>>> 
>>> Hi All,
>>> 
>>> I am seeing that all the issue has been cleaned for the 2.7.0
> milestone.
>>> It looks like all the things have been settled, I am planning to
>>> tag
>>> the 2.7.0 release today.
>>> 
>>> dubbo-ops and dubbo-spring-boot-project should be released after
>>> Dubbo
>>> 2.7.0 release.
>>> 
>>> On Wed, Jan 16, 2019 at 5:02 PM jun liu >>  ken.lj...@gmail.com>> wrote:
 
> There is no need to shade gson into dubbo.jar, just need depency
>>> gson
> library.
> 
> I have fixed it .
> https://github.com/apache/incubator-dubbo/pull/3246 <
> https://github.com/apache/incubator-dubbo/pull/3246> <
> https://github.com/apache/incubator-dubbo/pull/3246 <
> https://github.com/apache/incubator-dubbo/pull/3246>>
 Agree.
 
 Well done,  merged.
 
 Jun
 
> On Jan 16, 2019, at 4:15 PM, victory 
>>> wrote:
> 
> There is no need to shade gson into dubbo.jar, just need depency
>>> gson
> library.
> 
> I have fixed it .
> https://github.com/apache/incubator-dubbo/pull/3246
> 
> Ian Luo  于2019年1月16日周三 下午2:34写道：
> 
>> We should not shade gson binaries into dubbo all in one jar
>>> file,
> even
>> though there's no license issue. It is simply we should not do
>>> this,
>> instead, we should make sure dubbo all in one jar should have a
> transitive
>> dependency to gson library.
>> 
>> I noticed it's caused
> by'com.google.code.gson:gson' in
>> dubbo-all/pom.xml. We should fix it.
>> 
>> Thanks,
>> -Ian.
>> 
>> 
>> On Tue, Jan 15, 2019 at 5:16 PM jun liu 
> wrote:
>> 
>>> I noticed that a third-party source code ‘com.google <
> http://com.google/
>>> .gson.*’
>>> has been compiled into the convenient maven binary jar of
>>> 2.7.0 -
>>> dubbo-2.7.0.jar :
>>> 
>>> .
>>> ├── META-INF
>>> │   ├── DEPENDENCIES
>>> │   ├── LICENSE
>>> │   ├── MANIFEST.MF
>>> │   ├── NOTICE
>>> │   ├── assembly
>>> │   │   └── bin
>>> │   ├── compat
>>> │   │   └── dubbo.xsd
>>> │   ├── dubbo
>>> │   │   └── internal
>>> │   ├── dubbo.xsd
>>> │   ├── maven
>>> │   │   ├── com.alibaba
>>> │   │   ├── com.google.code.gson
>>> │   │   └── org.apache.dubbo
>>> │   

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

All the preparation seems going well.
I have successfully uploaded 2.7.0 to staging repo, and upload the
release candidate to svn.
I saw that the release note is still in Chinese.

Jun, could you please summarize an English version of the release note.
I will send the vote email once it is done.

On Thu, Jan 17, 2019 at 5:48 PM victory  wrote:
>
> I have check the file , it is the same as pull request #3263.
>
>
> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
>
> > Hi Victory,
> >
> > I've mistakenly reverted your recent pull request[1].
> > Luckily I have restored it via the commit email message.
> > I've push it to 2.7.0-release branch already.
> > Would you please help to check it?
> >
> >
> > [1] https://github.com/apache/incubator-dubbo/pull/3263
> >
> > On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
> > >
> > > I have review the code and it work well in
> > >
> > https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> > >
> > > I have merged this pull request into 2.7.0-release.
> > >
> > > Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> > >
> > > > Hi,
> > > >
> > > > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > > > wait for it and re-do the tagging.
> > > >
> > > > On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> > > > >
> > > > > > I am seeing that all the issue has been cleaned for the 2.7.0
> > > > milestone.
> > > > > > It looks like all the things have been settled, I am planning to
> > tag
> > > > > > the 2.7.0 release today.
> > > > >
> > > > > One more issue to be solved before vote.
> > > > > Thanks to the suggestions from the Apollo[1] community, I submitted a
> > > > PR[2] to polish the Apollo extension. Please help to review.
> > > > >
> > > > > 1. https://github.com/ctripcorp/apollo
> > > > > 2. https://github.com/apache/incubator-dubbo/pull/3263
> > > > >
> > > > > Jun
> > > > >
> > > > > > On Jan 17, 2019, at 10:41 AM, Huxing Zhang 
> > wrote:
> > > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > I am seeing that all the issue has been cleaned for the 2.7.0
> > > > milestone.
> > > > > > It looks like all the things have been settled, I am planning to
> > tag
> > > > > > the 2.7.0 release today.
> > > > > >
> > > > > > dubbo-ops and dubbo-spring-boot-project should be released after
> > Dubbo
> > > > > > 2.7.0 release.
> > > > > >
> > > > > > On Wed, Jan 16, 2019 at 5:02 PM jun liu  >  > > > ken.lj...@gmail.com>> wrote:
> > > > > >>
> > > > > >>> There is no need to shade gson into dubbo.jar, just need depency
> > gson
> > > > > >>> library.
> > > > > >>>
> > > > > >>> I have fixed it .
> > > > https://github.com/apache/incubator-dubbo/pull/3246 <
> > > > https://github.com/apache/incubator-dubbo/pull/3246> <
> > > > https://github.com/apache/incubator-dubbo/pull/3246 <
> > > > https://github.com/apache/incubator-dubbo/pull/3246>>
> > > > > >> Agree.
> > > > > >>
> > > > > >> Well done,  merged.
> > > > > >>
> > > > > >> Jun
> > > > > >>
> > > > > >>> On Jan 16, 2019, at 4:15 PM, victory 
> > wrote:
> > > > > >>>
> > > > > >>> There is no need to shade gson into dubbo.jar, just need depency
> > gson
> > > > > >>> library.
> > > > > >>>
> > > > > >>> I have fixed it .
> > > > https://github.com/apache/incubator-dubbo/pull/3246
> > > > > >>>
> > > > > >>> Ian Luo  于2019年1月16日周三 下午2:34写道：
> > > > > >>>
> > > > >  We should not shade gson binaries into dubbo all in one jar
> > file,
> > > > even
> > > > >  though there's no license issue. It is simply we should not do
> > this,
> > > > >  instead, we should make sure dubbo all in one jar should have a
> > > > transitive
> > > > >  dependency to gson library.
> > > > > 
> > > > >  I noticed it's caused
> > > > by'com.google.code.gson:gson' in
> > > > >  dubbo-all/pom.xml. We should fix it.
> > > > > 
> > > > >  Thanks,
> > > > >  -Ian.
> > > > > 
> > > > > 
> > > > >  On Tue, Jan 15, 2019 at 5:16 PM jun liu 
> > > > wrote:
> > > > > 
> > > > > > I noticed that a third-party source code ‘com.google <
> > > > http://com.google/
> > > > > > .gson.*’
> > > > > > has been compiled into the convenient maven binary jar of
> > 2.7.0 -
> > > > > > dubbo-2.7.0.jar :
> > > > > >
> > > > > > .
> > > > > > ├── META-INF
> > > > > > │   ├── DEPENDENCIES
> > > > > > │   ├── LICENSE
> > > > > > │   ├── MANIFEST.MF
> > > > > > │   ├── NOTICE
> > > > > > │   ├── assembly
> > > > > > │   │   └── bin
> > > > > > │   ├── compat
> > > > > > │   │   └── dubbo.xsd
> > > > > > │   ├── dubbo
> > > > > > │   │   └── internal
> > > > > > │   ├── dubbo.xsd
> > > > > > │   ├── maven
> > > > > > │   │   ├── com.alibaba
> > > > > > │   │   ├── com.google.code.gson
> > > > > > │   │   └── org.apache.dubbo
> > > > > > │   ├── spring.handlers
> > > > > > │   └── spring.schemas
> > > > > > ├── com
> > > > > 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[victory]

I have check the file , it is the same as pull request #3263.


Huxing Zhang  于2019年1月17日周四 下午5:34写道：

> Hi Victory,
>
> I've mistakenly reverted your recent pull request[1].
> Luckily I have restored it via the commit email message.
> I've push it to 2.7.0-release branch already.
> Would you please help to check it?
>
>
> [1] https://github.com/apache/incubator-dubbo/pull/3263
>
> On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
> >
> > I have review the code and it work well in
> >
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> >
> > I have merged this pull request into 2.7.0-release.
> >
> > Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> >
> > > Hi,
> > >
> > > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > > wait for it and re-do the tagging.
> > >
> > > On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> > > >
> > > > > I am seeing that all the issue has been cleaned for the 2.7.0
> > > milestone.
> > > > > It looks like all the things have been settled, I am planning to
> tag
> > > > > the 2.7.0 release today.
> > > >
> > > > One more issue to be solved before vote.
> > > > Thanks to the suggestions from the Apollo[1] community, I submitted a
> > > PR[2] to polish the Apollo extension. Please help to review.
> > > >
> > > > 1. https://github.com/ctripcorp/apollo
> > > > 2. https://github.com/apache/incubator-dubbo/pull/3263
> > > >
> > > > Jun
> > > >
> > > > > On Jan 17, 2019, at 10:41 AM, Huxing Zhang 
> wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > > I am seeing that all the issue has been cleaned for the 2.7.0
> > > milestone.
> > > > > It looks like all the things have been settled, I am planning to
> tag
> > > > > the 2.7.0 release today.
> > > > >
> > > > > dubbo-ops and dubbo-spring-boot-project should be released after
> Dubbo
> > > > > 2.7.0 release.
> > > > >
> > > > > On Wed, Jan 16, 2019 at 5:02 PM jun liu   > > ken.lj...@gmail.com>> wrote:
> > > > >>
> > > > >>> There is no need to shade gson into dubbo.jar, just need depency
> gson
> > > > >>> library.
> > > > >>>
> > > > >>> I have fixed it .
> > > https://github.com/apache/incubator-dubbo/pull/3246 <
> > > https://github.com/apache/incubator-dubbo/pull/3246> <
> > > https://github.com/apache/incubator-dubbo/pull/3246 <
> > > https://github.com/apache/incubator-dubbo/pull/3246>>
> > > > >> Agree.
> > > > >>
> > > > >> Well done,  merged.
> > > > >>
> > > > >> Jun
> > > > >>
> > > > >>> On Jan 16, 2019, at 4:15 PM, victory 
> wrote:
> > > > >>>
> > > > >>> There is no need to shade gson into dubbo.jar, just need depency
> gson
> > > > >>> library.
> > > > >>>
> > > > >>> I have fixed it .
> > > https://github.com/apache/incubator-dubbo/pull/3246
> > > > >>>
> > > > >>> Ian Luo  于2019年1月16日周三 下午2:34写道：
> > > > >>>
> > > >  We should not shade gson binaries into dubbo all in one jar
> file,
> > > even
> > > >  though there's no license issue. It is simply we should not do
> this,
> > > >  instead, we should make sure dubbo all in one jar should have a
> > > transitive
> > > >  dependency to gson library.
> > > > 
> > > >  I noticed it's caused
> > > by'com.google.code.gson:gson' in
> > > >  dubbo-all/pom.xml. We should fix it.
> > > > 
> > > >  Thanks,
> > > >  -Ian.
> > > > 
> > > > 
> > > >  On Tue, Jan 15, 2019 at 5:16 PM jun liu 
> > > wrote:
> > > > 
> > > > > I noticed that a third-party source code ‘com.google <
> > > http://com.google/
> > > > > .gson.*’
> > > > > has been compiled into the convenient maven binary jar of
> 2.7.0 -
> > > > > dubbo-2.7.0.jar :
> > > > >
> > > > > .
> > > > > ├── META-INF
> > > > > │   ├── DEPENDENCIES
> > > > > │   ├── LICENSE
> > > > > │   ├── MANIFEST.MF
> > > > > │   ├── NOTICE
> > > > > │   ├── assembly
> > > > > │   │   └── bin
> > > > > │   ├── compat
> > > > > │   │   └── dubbo.xsd
> > > > > │   ├── dubbo
> > > > > │   │   └── internal
> > > > > │   ├── dubbo.xsd
> > > > > │   ├── maven
> > > > > │   │   ├── com.alibaba
> > > > > │   │   ├── com.google.code.gson
> > > > > │   │   └── org.apache.dubbo
> > > > > │   ├── spring.handlers
> > > > > │   └── spring.schemas
> > > > > ├── com
> > > > > │   ├── alibaba
> > > > > │   │   ├── com
> > > > > │   │   └── dubbo
> > > > > │   └── google
> > > > > │   └── gson
> > > > > └── org
> > > > >   └── apache
> > > > >   └── dubbo
> > > > >
> > > > >
> > > > > Since this binary jar (dubbo-2.7.0.jar) will be included in the
> > > Apache
> > > > > Binary Release, should we update the LICENSE or NOTICE file in
> the
> > > Binary
> > > > > Release to announce the existence of these binary files?
> > > > >
> > > > > BTW, ‘com.google .gson’ is declared to be
> unde
> > > >  Apache
> > > > 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

On Thu, Jan 17, 2019 at 5:38 PM jun liu  wrote:
>
> I’ve confirmed the commit, all fine, pls., go ahead and enjoy.

Good, doing.

>
> Jun
>
> > On Jan 17, 2019, at 5:34 PM, Huxing Zhang  wrote:
> >
> > Hi Victory,
> >
> > I've mistakenly reverted your recent pull request[1].
> > Luckily I have restored it via the commit email message.
> > I've push it to 2.7.0-release branch already.
> > Would you please help to check it?
> >
> >
> > [1] https://github.com/apache/incubator-dubbo/pull/3263
> >
> > On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
> >>
> >> I have review the code and it work well in
> >> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> >>
> >> I have merged this pull request into 2.7.0-release.
> >>
> >> Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> >>
> >>> Hi,
> >>>
> >>> This looks like a blocking issue, I've already tagged 2.7.0, I will
> >>> wait for it and re-do the tagging.
> >>>
> >>> On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> 
> > I am seeing that all the issue has been cleaned for the 2.7.0
> >>> milestone.
> > It looks like all the things have been settled, I am planning to tag
> > the 2.7.0 release today.
> 
>  One more issue to be solved before vote.
>  Thanks to the suggestions from the Apollo[1] community, I submitted a
> >>> PR[2] to polish the Apollo extension. Please help to review.
> 
>  1. https://github.com/ctripcorp/apollo
>  2. https://github.com/apache/incubator-dubbo/pull/3263
> 
>  Jun
> 
> > On Jan 17, 2019, at 10:41 AM, Huxing Zhang  wrote:
> >
> > Hi All,
> >
> > I am seeing that all the issue has been cleaned for the 2.7.0
> >>> milestone.
> > It looks like all the things have been settled, I am planning to tag
> > the 2.7.0 release today.
> >
> > dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> > 2.7.0 release.
> >
> > On Wed, Jan 16, 2019 at 5:02 PM jun liu  >>> ken.lj...@gmail.com>> wrote:
> >>
> >>> There is no need to shade gson into dubbo.jar, just need depency gson
> >>> library.
> >>>
> >>> I have fixed it .
> >>> https://github.com/apache/incubator-dubbo/pull/3246 <
> >>> https://github.com/apache/incubator-dubbo/pull/3246> <
> >>> https://github.com/apache/incubator-dubbo/pull/3246 <
> >>> https://github.com/apache/incubator-dubbo/pull/3246>>
> >> Agree.
> >>
> >> Well done,  merged.
> >>
> >> Jun
> >>
> >>> On Jan 16, 2019, at 4:15 PM, victory  wrote:
> >>>
> >>> There is no need to shade gson into dubbo.jar, just need depency gson
> >>> library.
> >>>
> >>> I have fixed it .
> >>> https://github.com/apache/incubator-dubbo/pull/3246
> >>>
> >>> Ian Luo  于2019年1月16日周三 下午2:34写道：
> >>>
>  We should not shade gson binaries into dubbo all in one jar file,
> >>> even
>  though there's no license issue. It is simply we should not do this,
>  instead, we should make sure dubbo all in one jar should have a
> >>> transitive
>  dependency to gson library.
> 
>  I noticed it's caused
> >>> by'com.google.code.gson:gson' in
>  dubbo-all/pom.xml. We should fix it.
> 
>  Thanks,
>  -Ian.
> 
> 
>  On Tue, Jan 15, 2019 at 5:16 PM jun liu 
> >>> wrote:
> 
> > I noticed that a third-party source code ‘com.google <
> >>> http://com.google/
> > .gson.*’
> > has been compiled into the convenient maven binary jar of 2.7.0 -
> > dubbo-2.7.0.jar :
> >
> > .
> > ├── META-INF
> > │   ├── DEPENDENCIES
> > │   ├── LICENSE
> > │   ├── MANIFEST.MF
> > │   ├── NOTICE
> > │   ├── assembly
> > │   │   └── bin
> > │   ├── compat
> > │   │   └── dubbo.xsd
> > │   ├── dubbo
> > │   │   └── internal
> > │   ├── dubbo.xsd
> > │   ├── maven
> > │   │   ├── com.alibaba
> > │   │   ├── com.google.code.gson
> > │   │   └── org.apache.dubbo
> > │   ├── spring.handlers
> > │   └── spring.schemas
> > ├── com
> > │   ├── alibaba
> > │   │   ├── com
> > │   │   └── dubbo
> > │   └── google
> > │   └── gson
> > └── org
> >  └── apache
> >  └── dubbo
> >
> >
> > Since this binary jar (dubbo-2.7.0.jar) will be included in the
> >>> Apache
> > Binary Release, should we update the LICENSE or NOTICE file in the
> >>> Binary
> > Release to announce the existence of these binary files?
> >
> > BTW, ‘com.google .gson’ is declared to be unde
>  Apache
> > License 2.0.
> >
> > You can directly download the latest SNAPSHOT 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

I’ve confirmed the commit, all fine, pls., go ahead and enjoy.

Jun

> On Jan 17, 2019, at 5:34 PM, Huxing Zhang  wrote:
> 
> Hi Victory,
> 
> I've mistakenly reverted your recent pull request[1].
> Luckily I have restored it via the commit email message.
> I've push it to 2.7.0-release branch already.
> Would you please help to check it?
> 
> 
> [1] https://github.com/apache/incubator-dubbo/pull/3263
> 
> On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
>> 
>> I have review the code and it work well in
>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
>> 
>> I have merged this pull request into 2.7.0-release.
>> 
>> Huxing Zhang  于2019年1月17日周四 下午2:59写道：
>> 
>>> Hi,
>>> 
>>> This looks like a blocking issue, I've already tagged 2.7.0, I will
>>> wait for it and re-do the tagging.
>>> 
>>> On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
 
> I am seeing that all the issue has been cleaned for the 2.7.0
>>> milestone.
> It looks like all the things have been settled, I am planning to tag
> the 2.7.0 release today.
 
 One more issue to be solved before vote.
 Thanks to the suggestions from the Apollo[1] community, I submitted a
>>> PR[2] to polish the Apollo extension. Please help to review.
 
 1. https://github.com/ctripcorp/apollo
 2. https://github.com/apache/incubator-dubbo/pull/3263
 
 Jun
 
> On Jan 17, 2019, at 10:41 AM, Huxing Zhang  wrote:
> 
> Hi All,
> 
> I am seeing that all the issue has been cleaned for the 2.7.0
>>> milestone.
> It looks like all the things have been settled, I am planning to tag
> the 2.7.0 release today.
> 
> dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> 2.7.0 release.
> 
> On Wed, Jan 16, 2019 at 5:02 PM jun liu >> ken.lj...@gmail.com>> wrote:
>> 
>>> There is no need to shade gson into dubbo.jar, just need depency gson
>>> library.
>>> 
>>> I have fixed it .
>>> https://github.com/apache/incubator-dubbo/pull/3246 <
>>> https://github.com/apache/incubator-dubbo/pull/3246> <
>>> https://github.com/apache/incubator-dubbo/pull/3246 <
>>> https://github.com/apache/incubator-dubbo/pull/3246>>
>> Agree.
>> 
>> Well done,  merged.
>> 
>> Jun
>> 
>>> On Jan 16, 2019, at 4:15 PM, victory  wrote:
>>> 
>>> There is no need to shade gson into dubbo.jar, just need depency gson
>>> library.
>>> 
>>> I have fixed it .
>>> https://github.com/apache/incubator-dubbo/pull/3246
>>> 
>>> Ian Luo  于2019年1月16日周三 下午2:34写道：
>>> 
 We should not shade gson binaries into dubbo all in one jar file,
>>> even
 though there's no license issue. It is simply we should not do this,
 instead, we should make sure dubbo all in one jar should have a
>>> transitive
 dependency to gson library.
 
 I noticed it's caused
>>> by'com.google.code.gson:gson' in
 dubbo-all/pom.xml. We should fix it.
 
 Thanks,
 -Ian.
 
 
 On Tue, Jan 15, 2019 at 5:16 PM jun liu 
>>> wrote:
 
> I noticed that a third-party source code ‘com.google <
>>> http://com.google/
> .gson.*’
> has been compiled into the convenient maven binary jar of 2.7.0 -
> dubbo-2.7.0.jar :
> 
> .
> ├── META-INF
> │   ├── DEPENDENCIES
> │   ├── LICENSE
> │   ├── MANIFEST.MF
> │   ├── NOTICE
> │   ├── assembly
> │   │   └── bin
> │   ├── compat
> │   │   └── dubbo.xsd
> │   ├── dubbo
> │   │   └── internal
> │   ├── dubbo.xsd
> │   ├── maven
> │   │   ├── com.alibaba
> │   │   ├── com.google.code.gson
> │   │   └── org.apache.dubbo
> │   ├── spring.handlers
> │   └── spring.schemas
> ├── com
> │   ├── alibaba
> │   │   ├── com
> │   │   └── dubbo
> │   └── google
> │   └── gson
> └── org
>  └── apache
>  └── dubbo
> 
> 
> Since this binary jar (dubbo-2.7.0.jar) will be included in the
>>> Apache
> Binary Release, should we update the LICENSE or NOTICE file in the
>>> Binary
> Release to announce the existence of these binary files?
> 
> BTW, ‘com.google .gson’ is declared to be unde
 Apache
> License 2.0.
> 
> You can directly download the latest SNAPSHOT release of
>>> 2.7.0-SNAPSHOT
 in
> here[1] and unzip and check the contents to better understand what
>>> I am
> trying to describe here.
> 
> 1.
> 
 
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi Victory,

I've mistakenly reverted your recent pull request[1].
Luckily I have restored it via the commit email message.
I've push it to 2.7.0-release branch already.
Would you please help to check it?


[1] https://github.com/apache/incubator-dubbo/pull/3263

On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
>
> I have review the code and it work well in
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
>
> I have merged this pull request into 2.7.0-release.
>
> Huxing Zhang  于2019年1月17日周四 下午2:59写道：
>
> > Hi,
> >
> > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > wait for it and re-do the tagging.
> >
> > On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> > >
> > > > I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> > > > It looks like all the things have been settled, I am planning to tag
> > > > the 2.7.0 release today.
> > >
> > > One more issue to be solved before vote.
> > > Thanks to the suggestions from the Apollo[1] community, I submitted a
> > PR[2] to polish the Apollo extension. Please help to review.
> > >
> > > 1. https://github.com/ctripcorp/apollo
> > > 2. https://github.com/apache/incubator-dubbo/pull/3263
> > >
> > > Jun
> > >
> > > > On Jan 17, 2019, at 10:41 AM, Huxing Zhang  wrote:
> > > >
> > > > Hi All,
> > > >
> > > > I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> > > > It looks like all the things have been settled, I am planning to tag
> > > > the 2.7.0 release today.
> > > >
> > > > dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> > > > 2.7.0 release.
> > > >
> > > > On Wed, Jan 16, 2019 at 5:02 PM jun liu  > ken.lj...@gmail.com>> wrote:
> > > >>
> > > >>> There is no need to shade gson into dubbo.jar, just need depency gson
> > > >>> library.
> > > >>>
> > > >>> I have fixed it .
> > https://github.com/apache/incubator-dubbo/pull/3246 <
> > https://github.com/apache/incubator-dubbo/pull/3246> <
> > https://github.com/apache/incubator-dubbo/pull/3246 <
> > https://github.com/apache/incubator-dubbo/pull/3246>>
> > > >> Agree.
> > > >>
> > > >> Well done,  merged.
> > > >>
> > > >> Jun
> > > >>
> > > >>> On Jan 16, 2019, at 4:15 PM, victory  wrote:
> > > >>>
> > > >>> There is no need to shade gson into dubbo.jar, just need depency gson
> > > >>> library.
> > > >>>
> > > >>> I have fixed it .
> > https://github.com/apache/incubator-dubbo/pull/3246
> > > >>>
> > > >>> Ian Luo  于2019年1月16日周三 下午2:34写道：
> > > >>>
> > >  We should not shade gson binaries into dubbo all in one jar file,
> > even
> > >  though there's no license issue. It is simply we should not do this,
> > >  instead, we should make sure dubbo all in one jar should have a
> > transitive
> > >  dependency to gson library.
> > > 
> > >  I noticed it's caused
> > by'com.google.code.gson:gson' in
> > >  dubbo-all/pom.xml. We should fix it.
> > > 
> > >  Thanks,
> > >  -Ian.
> > > 
> > > 
> > >  On Tue, Jan 15, 2019 at 5:16 PM jun liu 
> > wrote:
> > > 
> > > > I noticed that a third-party source code ‘com.google <
> > http://com.google/
> > > > .gson.*’
> > > > has been compiled into the convenient maven binary jar of 2.7.0 -
> > > > dubbo-2.7.0.jar :
> > > >
> > > > .
> > > > ├── META-INF
> > > > │   ├── DEPENDENCIES
> > > > │   ├── LICENSE
> > > > │   ├── MANIFEST.MF
> > > > │   ├── NOTICE
> > > > │   ├── assembly
> > > > │   │   └── bin
> > > > │   ├── compat
> > > > │   │   └── dubbo.xsd
> > > > │   ├── dubbo
> > > > │   │   └── internal
> > > > │   ├── dubbo.xsd
> > > > │   ├── maven
> > > > │   │   ├── com.alibaba
> > > > │   │   ├── com.google.code.gson
> > > > │   │   └── org.apache.dubbo
> > > > │   ├── spring.handlers
> > > > │   └── spring.schemas
> > > > ├── com
> > > > │   ├── alibaba
> > > > │   │   ├── com
> > > > │   │   └── dubbo
> > > > │   └── google
> > > > │   └── gson
> > > > └── org
> > > >   └── apache
> > > >   └── dubbo
> > > >
> > > >
> > > > Since this binary jar (dubbo-2.7.0.jar) will be included in the
> > Apache
> > > > Binary Release, should we update the LICENSE or NOTICE file in the
> > Binary
> > > > Release to announce the existence of these binary files?
> > > >
> > > > BTW, ‘com.google .gson’ is declared to be unde
> > >  Apache
> > > > License 2.0.
> > > >
> > > > You can directly download the latest SNAPSHOT release of
> > 2.7.0-SNAPSHOT
> > >  in
> > > > here[1] and unzip and check the contents to better understand what
> > I am
> > > > trying to describe here.
> > > >
> > > > 1.
> > > >
> > > 
> > 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
>
> I have review the code and it work well in
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
>
> I have merged this pull request into 2.7.0-release.

Good. I will start to work on re-tagging 2.7.0. Hopefully I can start
the vote process today. :)

>
> Huxing Zhang  于2019年1月17日周四 下午2:59写道：
>
> > Hi,
> >
> > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > wait for it and re-do the tagging.
> >
> > On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> > >
> > > > I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> > > > It looks like all the things have been settled, I am planning to tag
> > > > the 2.7.0 release today.
> > >
> > > One more issue to be solved before vote.
> > > Thanks to the suggestions from the Apollo[1] community, I submitted a
> > PR[2] to polish the Apollo extension. Please help to review.
> > >
> > > 1. https://github.com/ctripcorp/apollo
> > > 2. https://github.com/apache/incubator-dubbo/pull/3263
> > >
> > > Jun
> > >
> > > > On Jan 17, 2019, at 10:41 AM, Huxing Zhang  wrote:
> > > >
> > > > Hi All,
> > > >
> > > > I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> > > > It looks like all the things have been settled, I am planning to tag
> > > > the 2.7.0 release today.
> > > >
> > > > dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> > > > 2.7.0 release.
> > > >
> > > > On Wed, Jan 16, 2019 at 5:02 PM jun liu  > ken.lj...@gmail.com>> wrote:
> > > >>
> > > >>> There is no need to shade gson into dubbo.jar, just need depency gson
> > > >>> library.
> > > >>>
> > > >>> I have fixed it .
> > https://github.com/apache/incubator-dubbo/pull/3246 <
> > https://github.com/apache/incubator-dubbo/pull/3246> <
> > https://github.com/apache/incubator-dubbo/pull/3246 <
> > https://github.com/apache/incubator-dubbo/pull/3246>>
> > > >> Agree.
> > > >>
> > > >> Well done,  merged.
> > > >>
> > > >> Jun
> > > >>
> > > >>> On Jan 16, 2019, at 4:15 PM, victory  wrote:
> > > >>>
> > > >>> There is no need to shade gson into dubbo.jar, just need depency gson
> > > >>> library.
> > > >>>
> > > >>> I have fixed it .
> > https://github.com/apache/incubator-dubbo/pull/3246
> > > >>>
> > > >>> Ian Luo  于2019年1月16日周三 下午2:34写道：
> > > >>>
> > >  We should not shade gson binaries into dubbo all in one jar file,
> > even
> > >  though there's no license issue. It is simply we should not do this,
> > >  instead, we should make sure dubbo all in one jar should have a
> > transitive
> > >  dependency to gson library.
> > > 
> > >  I noticed it's caused
> > by'com.google.code.gson:gson' in
> > >  dubbo-all/pom.xml. We should fix it.
> > > 
> > >  Thanks,
> > >  -Ian.
> > > 
> > > 
> > >  On Tue, Jan 15, 2019 at 5:16 PM jun liu 
> > wrote:
> > > 
> > > > I noticed that a third-party source code ‘com.google <
> > http://com.google/
> > > > .gson.*’
> > > > has been compiled into the convenient maven binary jar of 2.7.0 -
> > > > dubbo-2.7.0.jar :
> > > >
> > > > .
> > > > ├── META-INF
> > > > │   ├── DEPENDENCIES
> > > > │   ├── LICENSE
> > > > │   ├── MANIFEST.MF
> > > > │   ├── NOTICE
> > > > │   ├── assembly
> > > > │   │   └── bin
> > > > │   ├── compat
> > > > │   │   └── dubbo.xsd
> > > > │   ├── dubbo
> > > > │   │   └── internal
> > > > │   ├── dubbo.xsd
> > > > │   ├── maven
> > > > │   │   ├── com.alibaba
> > > > │   │   ├── com.google.code.gson
> > > > │   │   └── org.apache.dubbo
> > > > │   ├── spring.handlers
> > > > │   └── spring.schemas
> > > > ├── com
> > > > │   ├── alibaba
> > > > │   │   ├── com
> > > > │   │   └── dubbo
> > > > │   └── google
> > > > │   └── gson
> > > > └── org
> > > >   └── apache
> > > >   └── dubbo
> > > >
> > > >
> > > > Since this binary jar (dubbo-2.7.0.jar) will be included in the
> > Apache
> > > > Binary Release, should we update the LICENSE or NOTICE file in the
> > Binary
> > > > Release to announce the existence of these binary files?
> > > >
> > > > BTW, ‘com.google .gson’ is declared to be unde
> > >  Apache
> > > > License 2.0.
> > > >
> > > > You can directly download the latest SNAPSHOT release of
> > 2.7.0-SNAPSHOT
> > >  in
> > > > here[1] and unzip and check the contents to better understand what
> > I am
> > > > trying to describe here.
> > > >
> > > > 1.
> > > >
> > > 
> > https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> > > >
> > > > Jun
> > > >
> > > >> On Jan 13, 2019, at 5:58 PM, Huxing Zhang 
> > wrote:
> > > >>
> > > >> Hi Jun,
> > > >>
> > 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[victory]

I have review the code and it work well in
https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo

I have merged this pull request into 2.7.0-release.

Huxing Zhang  于2019年1月17日周四 下午2:59写道：

> Hi,
>
> This looks like a blocking issue, I've already tagged 2.7.0, I will
> wait for it and re-do the tagging.
>
> On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> >
> > > I am seeing that all the issue has been cleaned for the 2.7.0
> milestone.
> > > It looks like all the things have been settled, I am planning to tag
> > > the 2.7.0 release today.
> >
> > One more issue to be solved before vote.
> > Thanks to the suggestions from the Apollo[1] community, I submitted a
> PR[2] to polish the Apollo extension. Please help to review.
> >
> > 1. https://github.com/ctripcorp/apollo
> > 2. https://github.com/apache/incubator-dubbo/pull/3263
> >
> > Jun
> >
> > > On Jan 17, 2019, at 10:41 AM, Huxing Zhang  wrote:
> > >
> > > Hi All,
> > >
> > > I am seeing that all the issue has been cleaned for the 2.7.0
> milestone.
> > > It looks like all the things have been settled, I am planning to tag
> > > the 2.7.0 release today.
> > >
> > > dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> > > 2.7.0 release.
> > >
> > > On Wed, Jan 16, 2019 at 5:02 PM jun liu  ken.lj...@gmail.com>> wrote:
> > >>
> > >>> There is no need to shade gson into dubbo.jar, just need depency gson
> > >>> library.
> > >>>
> > >>> I have fixed it .
> https://github.com/apache/incubator-dubbo/pull/3246 <
> https://github.com/apache/incubator-dubbo/pull/3246> <
> https://github.com/apache/incubator-dubbo/pull/3246 <
> https://github.com/apache/incubator-dubbo/pull/3246>>
> > >> Agree.
> > >>
> > >> Well done,  merged.
> > >>
> > >> Jun
> > >>
> > >>> On Jan 16, 2019, at 4:15 PM, victory  wrote:
> > >>>
> > >>> There is no need to shade gson into dubbo.jar, just need depency gson
> > >>> library.
> > >>>
> > >>> I have fixed it .
> https://github.com/apache/incubator-dubbo/pull/3246
> > >>>
> > >>> Ian Luo  于2019年1月16日周三 下午2:34写道：
> > >>>
> >  We should not shade gson binaries into dubbo all in one jar file,
> even
> >  though there's no license issue. It is simply we should not do this,
> >  instead, we should make sure dubbo all in one jar should have a
> transitive
> >  dependency to gson library.
> > 
> >  I noticed it's caused
> by'com.google.code.gson:gson' in
> >  dubbo-all/pom.xml. We should fix it.
> > 
> >  Thanks,
> >  -Ian.
> > 
> > 
> >  On Tue, Jan 15, 2019 at 5:16 PM jun liu 
> wrote:
> > 
> > > I noticed that a third-party source code ‘com.google <
> http://com.google/
> > > .gson.*’
> > > has been compiled into the convenient maven binary jar of 2.7.0 -
> > > dubbo-2.7.0.jar :
> > >
> > > .
> > > ├── META-INF
> > > │   ├── DEPENDENCIES
> > > │   ├── LICENSE
> > > │   ├── MANIFEST.MF
> > > │   ├── NOTICE
> > > │   ├── assembly
> > > │   │   └── bin
> > > │   ├── compat
> > > │   │   └── dubbo.xsd
> > > │   ├── dubbo
> > > │   │   └── internal
> > > │   ├── dubbo.xsd
> > > │   ├── maven
> > > │   │   ├── com.alibaba
> > > │   │   ├── com.google.code.gson
> > > │   │   └── org.apache.dubbo
> > > │   ├── spring.handlers
> > > │   └── spring.schemas
> > > ├── com
> > > │   ├── alibaba
> > > │   │   ├── com
> > > │   │   └── dubbo
> > > │   └── google
> > > │   └── gson
> > > └── org
> > >   └── apache
> > >   └── dubbo
> > >
> > >
> > > Since this binary jar (dubbo-2.7.0.jar) will be included in the
> Apache
> > > Binary Release, should we update the LICENSE or NOTICE file in the
> Binary
> > > Release to announce the existence of these binary files?
> > >
> > > BTW, ‘com.google .gson’ is declared to be unde
> >  Apache
> > > License 2.0.
> > >
> > > You can directly download the latest SNAPSHOT release of
> 2.7.0-SNAPSHOT
> >  in
> > > here[1] and unzip and check the contents to better understand what
> I am
> > > trying to describe here.
> > >
> > > 1.
> > >
> > 
> https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> > >
> > > Jun
> > >
> > >> On Jan 13, 2019, at 5:58 PM, Huxing Zhang 
> wrote:
> > >>
> > >> Hi Jun,
> > >>
> > >> Could you summarize the current status of the 2.7-release branch?
> > >> I see there are still several enhancement on this branch.
> > >>
> > >> As this is the first time to prepare for a release for me, I am
> trying
> > >> to walk through the release steps[1].
> > >> I might try to deploy snapshot to maven repository.
> > >>
> > >> Once we feel it is ready to do the release, I will start the
> formal
> > >> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

This looks like a blocking issue, I've already tagged 2.7.0, I will
wait for it and re-do the tagging.

On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
>
> > I am seeing that all the issue has been cleaned for the 2.7.0 milestone.
> > It looks like all the things have been settled, I am planning to tag
> > the 2.7.0 release today.
>
> One more issue to be solved before vote.
> Thanks to the suggestions from the Apollo[1] community, I submitted a PR[2] 
> to polish the Apollo extension. Please help to review.
>
> 1. https://github.com/ctripcorp/apollo
> 2. https://github.com/apache/incubator-dubbo/pull/3263
>
> Jun
>
> > On Jan 17, 2019, at 10:41 AM, Huxing Zhang  wrote:
> >
> > Hi All,
> >
> > I am seeing that all the issue has been cleaned for the 2.7.0 milestone.
> > It looks like all the things have been settled, I am planning to tag
> > the 2.7.0 release today.
> >
> > dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> > 2.7.0 release.
> >
> > On Wed, Jan 16, 2019 at 5:02 PM jun liu  > > wrote:
> >>
> >>> There is no need to shade gson into dubbo.jar, just need depency gson
> >>> library.
> >>>
> >>> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246 
> >>>  
> >>>  >>> >
> >> Agree.
> >>
> >> Well done,  merged.
> >>
> >> Jun
> >>
> >>> On Jan 16, 2019, at 4:15 PM, victory  wrote:
> >>>
> >>> There is no need to shade gson into dubbo.jar, just need depency gson
> >>> library.
> >>>
> >>> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246
> >>>
> >>> Ian Luo  于2019年1月16日周三 下午2:34写道：
> >>>
>  We should not shade gson binaries into dubbo all in one jar file, even
>  though there's no license issue. It is simply we should not do this,
>  instead, we should make sure dubbo all in one jar should have a 
>  transitive
>  dependency to gson library.
> 
>  I noticed it's caused by'com.google.code.gson:gson' in
>  dubbo-all/pom.xml. We should fix it.
> 
>  Thanks,
>  -Ian.
> 
> 
>  On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:
> 
> > I noticed that a third-party source code ‘com.google  > .gson.*’
> > has been compiled into the convenient maven binary jar of 2.7.0 -
> > dubbo-2.7.0.jar :
> >
> > .
> > ├── META-INF
> > │   ├── DEPENDENCIES
> > │   ├── LICENSE
> > │   ├── MANIFEST.MF
> > │   ├── NOTICE
> > │   ├── assembly
> > │   │   └── bin
> > │   ├── compat
> > │   │   └── dubbo.xsd
> > │   ├── dubbo
> > │   │   └── internal
> > │   ├── dubbo.xsd
> > │   ├── maven
> > │   │   ├── com.alibaba
> > │   │   ├── com.google.code.gson
> > │   │   └── org.apache.dubbo
> > │   ├── spring.handlers
> > │   └── spring.schemas
> > ├── com
> > │   ├── alibaba
> > │   │   ├── com
> > │   │   └── dubbo
> > │   └── google
> > │   └── gson
> > └── org
> >   └── apache
> >   └── dubbo
> >
> >
> > Since this binary jar (dubbo-2.7.0.jar) will be included in the Apache
> > Binary Release, should we update the LICENSE or NOTICE file in the 
> > Binary
> > Release to announce the existence of these binary files?
> >
> > BTW, ‘com.google .gson’ is declared to be unde
>  Apache
> > License 2.0.
> >
> > You can directly download the latest SNAPSHOT release of 2.7.0-SNAPSHOT
>  in
> > here[1] and unzip and check the contents to better understand what I am
> > trying to describe here.
> >
> > 1.
> >
>  https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> >
> > Jun
> >
> >> On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
> >>
> >> Hi Jun,
> >>
> >> Could you summarize the current status of the 2.7-release branch?
> >> I see there are still several enhancement on this branch.
> >>
> >> As this is the first time to prepare for a release for me, I am trying
> >> to walk through the release steps[1].
> >> I might try to deploy snapshot to maven repository.
> >>
> >> Once we feel it is ready to do the release, I will start the formal
> >> release process.
> >>
> >>
> >> [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> >>
> >>
> >> --
> >> Best Regards！
> >> Huxing
> >>
> >> On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> >>>
> >
> > Nice work!
> >
> > I think we should let the community to participate more in the
>  release
> > process, for example,
> > 1. check out a release branch called 2.7.0-release
> > 2. encourage people to check it 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

> I am seeing that all the issue has been cleaned for the 2.7.0 milestone.
> It looks like all the things have been settled, I am planning to tag
> the 2.7.0 release today.

One more issue to be solved before vote. 
Thanks to the suggestions from the Apollo[1] community, I submitted a PR[2] to 
polish the Apollo extension. Please help to review.

1. https://github.com/ctripcorp/apollo
2. https://github.com/apache/incubator-dubbo/pull/3263

Jun

> On Jan 17, 2019, at 10:41 AM, Huxing Zhang  wrote:
> 
> Hi All,
> 
> I am seeing that all the issue has been cleaned for the 2.7.0 milestone.
> It looks like all the things have been settled, I am planning to tag
> the 2.7.0 release today.
> 
> dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> 2.7.0 release.
> 
> On Wed, Jan 16, 2019 at 5:02 PM jun liu  > wrote:
>> 
>>> There is no need to shade gson into dubbo.jar, just need depency gson
>>> library.
>>> 
>>> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246 
>>>  
>>> >> >
>> Agree.
>> 
>> Well done,  merged.
>> 
>> Jun
>> 
>>> On Jan 16, 2019, at 4:15 PM, victory  wrote:
>>> 
>>> There is no need to shade gson into dubbo.jar, just need depency gson
>>> library.
>>> 
>>> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246
>>> 
>>> Ian Luo  于2019年1月16日周三 下午2:34写道：
>>> 
 We should not shade gson binaries into dubbo all in one jar file, even
 though there's no license issue. It is simply we should not do this,
 instead, we should make sure dubbo all in one jar should have a transitive
 dependency to gson library.
 
 I noticed it's caused by'com.google.code.gson:gson' in
 dubbo-all/pom.xml. We should fix it.
 
 Thanks,
 -Ian.
 
 
 On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:
 
> I noticed that a third-party source code ‘com.google  .gson.*’
> has been compiled into the convenient maven binary jar of 2.7.0 -
> dubbo-2.7.0.jar :
> 
> .
> ├── META-INF
> │   ├── DEPENDENCIES
> │   ├── LICENSE
> │   ├── MANIFEST.MF
> │   ├── NOTICE
> │   ├── assembly
> │   │   └── bin
> │   ├── compat
> │   │   └── dubbo.xsd
> │   ├── dubbo
> │   │   └── internal
> │   ├── dubbo.xsd
> │   ├── maven
> │   │   ├── com.alibaba
> │   │   ├── com.google.code.gson
> │   │   └── org.apache.dubbo
> │   ├── spring.handlers
> │   └── spring.schemas
> ├── com
> │   ├── alibaba
> │   │   ├── com
> │   │   └── dubbo
> │   └── google
> │   └── gson
> └── org
>   └── apache
>   └── dubbo
> 
> 
> Since this binary jar (dubbo-2.7.0.jar) will be included in the Apache
> Binary Release, should we update the LICENSE or NOTICE file in the Binary
> Release to announce the existence of these binary files?
> 
> BTW, ‘com.google .gson’ is declared to be unde
 Apache
> License 2.0.
> 
> You can directly download the latest SNAPSHOT release of 2.7.0-SNAPSHOT
 in
> here[1] and unzip and check the contents to better understand what I am
> trying to describe here.
> 
> 1.
> 
 https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> 
> Jun
> 
>> On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
>> 
>> Hi Jun,
>> 
>> Could you summarize the current status of the 2.7-release branch?
>> I see there are still several enhancement on this branch.
>> 
>> As this is the first time to prepare for a release for me, I am trying
>> to walk through the release steps[1].
>> I might try to deploy snapshot to maven repository.
>> 
>> Once we feel it is ready to do the release, I will start the formal
>> release process.
>> 
>> 
>> [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
>> 
>> 
>> --
>> Best Regards！
>> Huxing
>> 
>> On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
>>> 
> 
> Nice work!
> 
> I think we should let the community to participate more in the
 release
> process, for example,
> 1. check out a release branch called 2.7.0-release
> 2. encourage people to check it out, test it and report if there is
> any regressions, bugs or issues.
> 3. while we are doing the test, we can start going through the ASF
> release process locally, once we think it is ready to start a formal
> release note, it can be done very quickly.
> 
> By the way, we need decide the release manager of 2.7.0 release. Is
> there anyone who volunteer to do that?

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[yuhang xiu]

awesome.
Looking forward to dubbo 2.7.
I just looked at the milestones of 2.7. It looks like there is no problem.


Huxing Zhang  于2019年1月17日周四 上午10:42写道：

> Hi All,
>
> I am seeing that all the issue has been cleaned for the 2.7.0 milestone.
> It looks like all the things have been settled, I am planning to tag
> the 2.7.0 release today.
>
> dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> 2.7.0 release.
>
> On Wed, Jan 16, 2019 at 5:02 PM jun liu  wrote:
> >
> > > There is no need to shade gson into dubbo.jar, just need depency gson
> > > library.
> > >
> > > I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246
> 
> > Agree.
> >
> > Well done,  merged.
> >
> > Jun
> >
> > > On Jan 16, 2019, at 4:15 PM, victory  wrote:
> > >
> > > There is no need to shade gson into dubbo.jar, just need depency gson
> > > library.
> > >
> > > I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246
> > >
> > > Ian Luo  于2019年1月16日周三 下午2:34写道：
> > >
> > >> We should not shade gson binaries into dubbo all in one jar file, even
> > >> though there's no license issue. It is simply we should not do this,
> > >> instead, we should make sure dubbo all in one jar should have a
> transitive
> > >> dependency to gson library.
> > >>
> > >> I noticed it's caused
> by'com.google.code.gson:gson' in
> > >> dubbo-all/pom.xml. We should fix it.
> > >>
> > >> Thanks,
> > >> -Ian.
> > >>
> > >>
> > >> On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:
> > >>
> > >>> I noticed that a third-party source code ‘com.google <
> http://com.google/
> > >>> .gson.*’
> > >>> has been compiled into the convenient maven binary jar of 2.7.0 -
> > >>> dubbo-2.7.0.jar :
> > >>>
> > >>> .
> > >>> ├── META-INF
> > >>> │   ├── DEPENDENCIES
> > >>> │   ├── LICENSE
> > >>> │   ├── MANIFEST.MF
> > >>> │   ├── NOTICE
> > >>> │   ├── assembly
> > >>> │   │   └── bin
> > >>> │   ├── compat
> > >>> │   │   └── dubbo.xsd
> > >>> │   ├── dubbo
> > >>> │   │   └── internal
> > >>> │   ├── dubbo.xsd
> > >>> │   ├── maven
> > >>> │   │   ├── com.alibaba
> > >>> │   │   ├── com.google.code.gson
> > >>> │   │   └── org.apache.dubbo
> > >>> │   ├── spring.handlers
> > >>> │   └── spring.schemas
> > >>> ├── com
> > >>> │   ├── alibaba
> > >>> │   │   ├── com
> > >>> │   │   └── dubbo
> > >>> │   └── google
> > >>> │   └── gson
> > >>> └── org
> > >>>└── apache
> > >>>└── dubbo
> > >>>
> > >>>
> > >>> Since this binary jar (dubbo-2.7.0.jar) will be included in the
> Apache
> > >>> Binary Release, should we update the LICENSE or NOTICE file in the
> Binary
> > >>> Release to announce the existence of these binary files?
> > >>>
> > >>> BTW, ‘com.google .gson’ is declared to be unde
> > >> Apache
> > >>> License 2.0.
> > >>>
> > >>> You can directly download the latest SNAPSHOT release of
> 2.7.0-SNAPSHOT
> > >> in
> > >>> here[1] and unzip and check the contents to better understand what I
> am
> > >>> trying to describe here.
> > >>>
> > >>> 1.
> > >>>
> > >>
> https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> > >>>
> > >>> Jun
> > >>>
> >  On Jan 13, 2019, at 5:58 PM, Huxing Zhang 
> wrote:
> > 
> >  Hi Jun,
> > 
> >  Could you summarize the current status of the 2.7-release branch?
> >  I see there are still several enhancement on this branch.
> > 
> >  As this is the first time to prepare for a release for me, I am
> trying
> >  to walk through the release steps[1].
> >  I might try to deploy snapshot to maven repository.
> > 
> >  Once we feel it is ready to do the release, I will start the formal
> >  release process.
> > 
> > 
> >  [1]
> http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> > 
> > 
> >  --
> >  Best Regards！
> >  Huxing
> > 
> >  On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> > >
> > >>>
> > >>> Nice work!
> > >>>
> > >>> I think we should let the community to participate more in the
> > >> release
> > >>> process, for example,
> > >>> 1. check out a release branch called 2.7.0-release
> > >>> 2. encourage people to check it out, test it and report if there
> is
> > >>> any regressions, bugs or issues.
> > >>> 3. while we are doing the test, we can start going through the
> ASF
> > >>> release process locally, once we think it is ready to start a
> formal
> > >>> release note, it can be done very quickly.
> > >>>
> > >>> By the way, we need decide the release manager of 2.7.0 release.
> Is
> > >>> there anyone who volunteer to do that?
> > >
> > > Sorry, I missed this mail.
> > > * 2.7.0-release has been created
> > > * we've froze the codebase, test is underway.
> > >
> > >> I'd like to be the release manager if no one is claiming it.
> > >
> > > Great, I can 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

> There is no need to shade gson into dubbo.jar, just need depency gson
> library.
> 
> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246 
> 
Agree.

Well done,  merged.

Jun

> On Jan 16, 2019, at 4:15 PM, victory  wrote:
> 
> There is no need to shade gson into dubbo.jar, just need depency gson
> library.
> 
> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246
> 
> Ian Luo  于2019年1月16日周三 下午2:34写道：
> 
>> We should not shade gson binaries into dubbo all in one jar file, even
>> though there's no license issue. It is simply we should not do this,
>> instead, we should make sure dubbo all in one jar should have a transitive
>> dependency to gson library.
>> 
>> I noticed it's caused by'com.google.code.gson:gson' in
>> dubbo-all/pom.xml. We should fix it.
>> 
>> Thanks,
>> -Ian.
>> 
>> 
>> On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:
>> 
>>> I noticed that a third-party source code ‘com.google >> .gson.*’
>>> has been compiled into the convenient maven binary jar of 2.7.0 -
>>> dubbo-2.7.0.jar :
>>> 
>>> .
>>> ├── META-INF
>>> │   ├── DEPENDENCIES
>>> │   ├── LICENSE
>>> │   ├── MANIFEST.MF
>>> │   ├── NOTICE
>>> │   ├── assembly
>>> │   │   └── bin
>>> │   ├── compat
>>> │   │   └── dubbo.xsd
>>> │   ├── dubbo
>>> │   │   └── internal
>>> │   ├── dubbo.xsd
>>> │   ├── maven
>>> │   │   ├── com.alibaba
>>> │   │   ├── com.google.code.gson
>>> │   │   └── org.apache.dubbo
>>> │   ├── spring.handlers
>>> │   └── spring.schemas
>>> ├── com
>>> │   ├── alibaba
>>> │   │   ├── com
>>> │   │   └── dubbo
>>> │   └── google
>>> │   └── gson
>>> └── org
>>>└── apache
>>>└── dubbo
>>> 
>>> 
>>> Since this binary jar (dubbo-2.7.0.jar) will be included in the Apache
>>> Binary Release, should we update the LICENSE or NOTICE file in the Binary
>>> Release to announce the existence of these binary files?
>>> 
>>> BTW, ‘com.google .gson’ is declared to be unde
>> Apache
>>> License 2.0.
>>> 
>>> You can directly download the latest SNAPSHOT release of 2.7.0-SNAPSHOT
>> in
>>> here[1] and unzip and check the contents to better understand what I am
>>> trying to describe here.
>>> 
>>> 1.
>>> 
>> https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
>>> 
>>> Jun
>>> 
 On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
 
 Hi Jun,
 
 Could you summarize the current status of the 2.7-release branch?
 I see there are still several enhancement on this branch.
 
 As this is the first time to prepare for a release for me, I am trying
 to walk through the release steps[1].
 I might try to deploy snapshot to maven repository.
 
 Once we feel it is ready to do the release, I will start the formal
 release process.
 
 
 [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
 
 
 --
 Best Regards！
 Huxing
 
 On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> 
>>> 
>>> Nice work!
>>> 
>>> I think we should let the community to participate more in the
>> release
>>> process, for example,
>>> 1. check out a release branch called 2.7.0-release
>>> 2. encourage people to check it out, test it and report if there is
>>> any regressions, bugs or issues.
>>> 3. while we are doing the test, we can start going through the ASF
>>> release process locally, once we think it is ready to start a formal
>>> release note, it can be done very quickly.
>>> 
>>> By the way, we need decide the release manager of 2.7.0 release. Is
>>> there anyone who volunteer to do that?
> 
> Sorry, I missed this mail.
> * 2.7.0-release has been created
> * we've froze the codebase, test is underway.
> 
>> I'd like to be the release manager if no one is claiming it.
> 
> Great, I can help you with the source/binary packaging and tagging
>>> things.
> 
> Jun
> 
>> On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
>> 
>> Hi,
>> 
>> On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang 
>>> wrote:
>>> 
>>> Nice work!
>>> 
>>> I think we should let the community to participate more in the
>> release
>>> process, for example,
>>> 1. check out a release branch called 2.7.0-release
>>> 2. encourage people to check it out, test it and report if there is
>>> any regressions, bugs or issues.
>>> 3. while we are doing the test, we can start going through the ASF
>>> release process locally, once we think it is ready to start a formal
>>> release note, it can be done very quickly.
>>> 
>>> By the way, we need decide the release manager of 2.7.0 release. Is
>>> there anyone who volunteer to do that?
>> 
>> I'd like to be the release manager if no one is claiming it.
>>> 
>>> On Thu, Dec 27, 2018 at 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[victory]

There is no need to shade gson into dubbo.jar, just need depency gson
library.

I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246

Ian Luo  于2019年1月16日周三 下午2:34写道：

> We should not shade gson binaries into dubbo all in one jar file, even
> though there's no license issue. It is simply we should not do this,
> instead, we should make sure dubbo all in one jar should have a transitive
> dependency to gson library.
>
> I noticed it's caused by'com.google.code.gson:gson' in
> dubbo-all/pom.xml. We should fix it.
>
> Thanks,
> -Ian.
>
>
> On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:
>
> > I noticed that a third-party source code ‘com.google  >.gson.*’
> > has been compiled into the convenient maven binary jar of 2.7.0 -
> > dubbo-2.7.0.jar :
> > 
> > .
> > ├── META-INF
> > │   ├── DEPENDENCIES
> > │   ├── LICENSE
> > │   ├── MANIFEST.MF
> > │   ├── NOTICE
> > │   ├── assembly
> > │   │   └── bin
> > │   ├── compat
> > │   │   └── dubbo.xsd
> > │   ├── dubbo
> > │   │   └── internal
> > │   ├── dubbo.xsd
> > │   ├── maven
> > │   │   ├── com.alibaba
> > │   │   ├── com.google.code.gson
> > │   │   └── org.apache.dubbo
> > │   ├── spring.handlers
> > │   └── spring.schemas
> > ├── com
> > │   ├── alibaba
> > │   │   ├── com
> > │   │   └── dubbo
> > │   └── google
> > │   └── gson
> > └── org
> > └── apache
> > └── dubbo
> >
> >
> > Since this binary jar (dubbo-2.7.0.jar) will be included in the Apache
> > Binary Release, should we update the LICENSE or NOTICE file in the Binary
> > Release to announce the existence of these binary files?
> >
> > BTW, ‘com.google .gson’ is declared to be unde
> Apache
> > License 2.0.
> >
> > You can directly download the latest SNAPSHOT release of 2.7.0-SNAPSHOT
> in
> > here[1] and unzip and check the contents to better understand what I am
> > trying to describe here.
> >
> > 1.
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> >
> > Jun
> >
> > > On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
> > >
> > > Hi Jun,
> > >
> > > Could you summarize the current status of the 2.7-release branch?
> > > I see there are still several enhancement on this branch.
> > >
> > > As this is the first time to prepare for a release for me, I am trying
> > > to walk through the release steps[1].
> > > I might try to deploy snapshot to maven repository.
> > >
> > > Once we feel it is ready to do the release, I will start the formal
> > > release process.
> > >
> > >
> > > [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> > >
> > >
> > > --
> > > Best Regards！
> > > Huxing
> > >
> > > On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> > >>
> > 
> >  Nice work!
> > 
> >  I think we should let the community to participate more in the
> release
> >  process, for example,
> >  1. check out a release branch called 2.7.0-release
> >  2. encourage people to check it out, test it and report if there is
> >  any regressions, bugs or issues.
> >  3. while we are doing the test, we can start going through the ASF
> >  release process locally, once we think it is ready to start a formal
> >  release note, it can be done very quickly.
> > 
> >  By the way, we need decide the release manager of 2.7.0 release. Is
> >  there anyone who volunteer to do that?
> > >>
> > >> Sorry, I missed this mail.
> > >> * 2.7.0-release has been created
> > >> * we've froze the codebase, test is underway.
> > >>
> > >>> I'd like to be the release manager if no one is claiming it.
> > >>
> > >> Great, I can help you with the source/binary packaging and tagging
> > things.
> > >>
> > >> Jun
> > >>
> > >>> On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang 
> > wrote:
> > 
> >  Nice work!
> > 
> >  I think we should let the community to participate more in the
> release
> >  process, for example,
> >  1. check out a release branch called 2.7.0-release
> >  2. encourage people to check it out, test it and report if there is
> >  any regressions, bugs or issues.
> >  3. while we are doing the test, we can start going through the ASF
> >  release process locally, once we think it is ready to start a formal
> >  release note, it can be done very quickly.
> > 
> >  By the way, we need decide the release manager of 2.7.0 release. Is
> >  there anyone who volunteer to do that?
> > >>>
> > >>> I'd like to be the release manager if no one is claiming it.
> > 
> >  On Thu, Dec 27, 2018 at 11:53 PM jun liu 
> wrote:
> > >
> > > Hi, All
> > >
> > > I am writing this mail to
> > >
> > > * Keep you refreshed of the latest status about v2.7.0.
> > > * Call for efforts on code review and tests
> > > * Discuss possible release schedules of v2.7.0.
> > >

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Ian Luo]

We should not shade gson binaries into dubbo all in one jar file, even
though there's no license issue. It is simply we should not do this,
instead, we should make sure dubbo all in one jar should have a transitive
dependency to gson library.

I noticed it's caused by'com.google.code.gson:gson' in
dubbo-all/pom.xml. We should fix it.

Thanks,
-Ian.


On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:

> I noticed that a third-party source code ‘com.google 
> .gson.*’
> has been compiled into the convenient maven binary jar of 2.7.0 -
> dubbo-2.7.0.jar :
> 
> .
> ├── META-INF
> │   ├── DEPENDENCIES
> │   ├── LICENSE
> │   ├── MANIFEST.MF
> │   ├── NOTICE
> │   ├── assembly
> │   │   └── bin
> │   ├── compat
> │   │   └── dubbo.xsd
> │   ├── dubbo
> │   │   └── internal
> │   ├── dubbo.xsd
> │   ├── maven
> │   │   ├── com.alibaba
> │   │   ├── com.google.code.gson
> │   │   └── org.apache.dubbo
> │   ├── spring.handlers
> │   └── spring.schemas
> ├── com
> │   ├── alibaba
> │   │   ├── com
> │   │   └── dubbo
> │   └── google
> │   └── gson
> └── org
> └── apache
> └── dubbo
>
>
> Since this binary jar (dubbo-2.7.0.jar) will be included in the Apache
> Binary Release, should we update the LICENSE or NOTICE file in the Binary
> Release to announce the existence of these binary files?
>
> BTW, ‘com.google .gson’ is declared to be unde Apache
> License 2.0.
>
> You can directly download the latest SNAPSHOT release of 2.7.0-SNAPSHOT in
> here[1] and unzip and check the contents to better understand what I am
> trying to describe here.
>
> 1.
> https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
>
> Jun
>
> > On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
> >
> > Hi Jun,
> >
> > Could you summarize the current status of the 2.7-release branch?
> > I see there are still several enhancement on this branch.
> >
> > As this is the first time to prepare for a release for me, I am trying
> > to walk through the release steps[1].
> > I might try to deploy snapshot to maven repository.
> >
> > Once we feel it is ready to do the release, I will start the formal
> > release process.
> >
> >
> > [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> >
> >
> > --
> > Best Regards！
> > Huxing
> >
> > On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> >>
> 
>  Nice work!
> 
>  I think we should let the community to participate more in the release
>  process, for example,
>  1. check out a release branch called 2.7.0-release
>  2. encourage people to check it out, test it and report if there is
>  any regressions, bugs or issues.
>  3. while we are doing the test, we can start going through the ASF
>  release process locally, once we think it is ready to start a formal
>  release note, it can be done very quickly.
> 
>  By the way, we need decide the release manager of 2.7.0 release. Is
>  there anyone who volunteer to do that?
> >>
> >> Sorry, I missed this mail.
> >> * 2.7.0-release has been created
> >> * we've froze the codebase, test is underway.
> >>
> >>> I'd like to be the release manager if no one is claiming it.
> >>
> >> Great, I can help you with the source/binary packaging and tagging
> things.
> >>
> >> Jun
> >>
> >>> On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
> >>>
> >>> Hi,
> >>>
> >>> On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang 
> wrote:
> 
>  Nice work!
> 
>  I think we should let the community to participate more in the release
>  process, for example,
>  1. check out a release branch called 2.7.0-release
>  2. encourage people to check it out, test it and report if there is
>  any regressions, bugs or issues.
>  3. while we are doing the test, we can start going through the ASF
>  release process locally, once we think it is ready to start a formal
>  release note, it can be done very quickly.
> 
>  By the way, we need decide the release manager of 2.7.0 release. Is
>  there anyone who volunteer to do that?
> >>>
> >>> I'd like to be the release manager if no one is claiming it.
> 
>  On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
> >
> > Hi, All
> >
> > I am writing this mail to
> >
> > * Keep you refreshed of the latest status about v2.7.0.
> > * Call for efforts on code review and tests
> > * Discuss possible release schedules of v2.7.0.
> >
> > About v2.7, it’s going to be a milestone version, in which will make
> some significant changes. Most importantly, we will complete all IP
> Clearance related works. Technically speaking, it’s from this version on
> that a Dubbo release starts fully follows the Apache rules (lawfully),
> totally independent from any other third-party organizations or companies.
> Secondly, this version will include many new features that have received
> wide attention from the community, by 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

I noticed that a third-party source code ‘com.google 
.gson.*’ has been compiled into the convenient maven binary 
jar of 2.7.0 - dubbo-2.7.0.jar :

.
├── META-INF
│   ├── DEPENDENCIES
│   ├── LICENSE
│   ├── MANIFEST.MF
│   ├── NOTICE
│   ├── assembly
│   │   └── bin
│   ├── compat
│   │   └── dubbo.xsd
│   ├── dubbo
│   │   └── internal
│   ├── dubbo.xsd
│   ├── maven
│   │   ├── com.alibaba
│   │   ├── com.google.code.gson
│   │   └── org.apache.dubbo
│   ├── spring.handlers
│   └── spring.schemas
├── com
│   ├── alibaba
│   │   ├── com
│   │   └── dubbo
│   └── google
│   └── gson
└── org
└── apache
└── dubbo


Since this binary jar (dubbo-2.7.0.jar) will be included in the Apache Binary 
Release, should we update the LICENSE or NOTICE file in the Binary Release to 
announce the existence of these binary files?

BTW, ‘com.google .gson’ is declared to be unde Apache 
License 2.0.

You can directly download the latest SNAPSHOT release of 2.7.0-SNAPSHOT in 
here[1] and unzip and check the contents to better understand what I am trying 
to describe here.

1. 
https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/

Jun

> On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
> 
> Hi Jun,
> 
> Could you summarize the current status of the 2.7-release branch?
> I see there are still several enhancement on this branch.
> 
> As this is the first time to prepare for a release for me, I am trying
> to walk through the release steps[1].
> I might try to deploy snapshot to maven repository.
> 
> Once we feel it is ready to do the release, I will start the formal
> release process.
> 
> 
> [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> 
> 
> -- 
> Best Regards！
> Huxing
> 
> On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
>> 
 
 Nice work!
 
 I think we should let the community to participate more in the release
 process, for example,
 1. check out a release branch called 2.7.0-release
 2. encourage people to check it out, test it and report if there is
 any regressions, bugs or issues.
 3. while we are doing the test, we can start going through the ASF
 release process locally, once we think it is ready to start a formal
 release note, it can be done very quickly.
 
 By the way, we need decide the release manager of 2.7.0 release. Is
 there anyone who volunteer to do that?
>> 
>> Sorry, I missed this mail.
>> * 2.7.0-release has been created
>> * we've froze the codebase, test is underway.
>> 
>>> I'd like to be the release manager if no one is claiming it.
>> 
>> Great, I can help you with the source/binary packaging and tagging things.
>> 
>> Jun
>> 
>>> On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
>>> 
>>> Hi,
>>> 
>>> On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang  wrote:
 
 Nice work!
 
 I think we should let the community to participate more in the release
 process, for example,
 1. check out a release branch called 2.7.0-release
 2. encourage people to check it out, test it and report if there is
 any regressions, bugs or issues.
 3. while we are doing the test, we can start going through the ASF
 release process locally, once we think it is ready to start a formal
 release note, it can be done very quickly.
 
 By the way, we need decide the release manager of 2.7.0 release. Is
 there anyone who volunteer to do that?
>>> 
>>> I'd like to be the release manager if no one is claiming it.
 
 On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
> 
> Hi, All
> 
> I am writing this mail to
> 
> * Keep you refreshed of the latest status about v2.7.0.
> * Call for efforts on code review and tests
> * Discuss possible release schedules of v2.7.0.
> 
> About v2.7, it’s going to be a milestone version, in which will make some 
> significant changes. Most importantly, we will complete all IP Clearance 
> related works. Technically speaking, it’s from this version on that a 
> Dubbo release starts fully follows the Apache rules (lawfully), totally 
> independent from any other third-party organizations or companies. 
> Secondly, this version will include many new features that have received 
> wide attention from the community, by supporting these features, we can 
> better resolve the community’s long accumulated demands. Last but not 
> least, we have made some architectural changes in this version, made 
> Dubbo closer to the micro-service architecture, take the newly introduced 
> configuration center as an example, it can work both as the center of 
> Externalized Configuration at startup and as the center of service 
> management configurations at runtime.
> 
> To summarize, the contents already included in the CodeBase are:
> 
> * Config Center: Zookeeper, Apollo, Nacos

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

PRs and issues regarding 2.7.0 raised recently:

Bugfixes:
1. https://github.com/apache/incubator-dubbo/pull/3233
2. https://github.com/apache/incubator-dubbo/pull/3232
3. https://github.com/apache/incubator-dubbo/pull/3229
4. https://github.com/apache/incubator-dubbo/pull/3224

* Async Enhancement
5. https://github.com/apache/incubator-dubbo/pull/3185
6. https://github.com/apache/incubator-dubbo/pull/3184

* Metadata Enhancement
7. https://github.com/apache/incubator-dubbo/pull/3182

Router Enhancement
8. https://github.com/apache/incubator-dubbo/pull/3173
9. https://github.com/apache/incubator-dubbo/pull/3233

Config Center
10. https://github.com/apache/incubator-dubbo/pull/3096

Jun

> On Jan 15, 2019, at 10:36 AM, jun liu  wrote:
> 
>> Hi Jun,
>> 
>> Could you summarize the current status of the 2.7-release branch?
>> I see there are still several enhancement on this branch.
> 
> The release notes draft[1] is available now (only Chinese version at 
> present). I will provide you the latest changes committed recently and the 
> TODOs left later today.
> 
> 1. https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md
> 
> Jun
> 
>> On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
>> 
>> Hi Jun,
>> 
>> Could you summarize the current status of the 2.7-release branch?
>> I see there are still several enhancement on this branch.
>> 
>> As this is the first time to prepare for a release for me, I am trying
>> to walk through the release steps[1].
>> I might try to deploy snapshot to maven repository.
>> 
>> Once we feel it is ready to do the release, I will start the formal
>> release process.
>> 
>> 
>> [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
>> 
>> 
>> -- 
>> Best Regards！
>> Huxing
>> 
>> On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
>>> 
> 
> Nice work!
> 
> I think we should let the community to participate more in the release
> process, for example,
> 1. check out a release branch called 2.7.0-release
> 2. encourage people to check it out, test it and report if there is
> any regressions, bugs or issues.
> 3. while we are doing the test, we can start going through the ASF
> release process locally, once we think it is ready to start a formal
> release note, it can be done very quickly.
> 
> By the way, we need decide the release manager of 2.7.0 release. Is
> there anyone who volunteer to do that?
>>> 
>>> Sorry, I missed this mail.
>>> * 2.7.0-release has been created
>>> * we've froze the codebase, test is underway.
>>> 
 I'd like to be the release manager if no one is claiming it.
>>> 
>>> Great, I can help you with the source/binary packaging and tagging things.
>>> 
>>> Jun
>>> 
 On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
 
 Hi,
 
 On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang  wrote:
> 
> Nice work!
> 
> I think we should let the community to participate more in the release
> process, for example,
> 1. check out a release branch called 2.7.0-release
> 2. encourage people to check it out, test it and report if there is
> any regressions, bugs or issues.
> 3. while we are doing the test, we can start going through the ASF
> release process locally, once we think it is ready to start a formal
> release note, it can be done very quickly.
> 
> By the way, we need decide the release manager of 2.7.0 release. Is
> there anyone who volunteer to do that?
 
 I'd like to be the release manager if no one is claiming it.
> 
> On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
>> 
>> Hi, All
>> 
>> I am writing this mail to
>> 
>> * Keep you refreshed of the latest status about v2.7.0.
>> * Call for efforts on code review and tests
>> * Discuss possible release schedules of v2.7.0.
>> 
>> About v2.7, it’s going to be a milestone version, in which will make 
>> some significant changes. Most importantly, we will complete all IP 
>> Clearance related works. Technically speaking, it’s from this version on 
>> that a Dubbo release starts fully follows the Apache rules (lawfully), 
>> totally independent from any other third-party organizations or 
>> companies. Secondly, this version will include many new features that 
>> have received wide attention from the community, by supporting these 
>> features, we can better resolve the community’s long accumulated 
>> demands. Last but not least, we have made some architectural changes in 
>> this version, made Dubbo closer to the micro-service architecture, take 
>> the newly introduced configuration center as an example, it can work 
>> both as the center of Externalized Configuration at startup and as the 
>> center of service management configurations at runtime.
>> 
>> To summarize, the contents already included in the CodeBase are:
>> 
>> * Config Center: 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

> Hi Jun,
> 
> Could you summarize the current status of the 2.7-release branch?
> I see there are still several enhancement on this branch.

The release notes draft[1] is available now (only Chinese version at present). 
I will provide you the latest changes committed recently and the TODOs left 
later today.

1. https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md

Jun

> On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
> 
> Hi Jun,
> 
> Could you summarize the current status of the 2.7-release branch?
> I see there are still several enhancement on this branch.
> 
> As this is the first time to prepare for a release for me, I am trying
> to walk through the release steps[1].
> I might try to deploy snapshot to maven repository.
> 
> Once we feel it is ready to do the release, I will start the formal
> release process.
> 
> 
> [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> 
> 
> -- 
> Best Regards！
> Huxing
> 
> On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
>> 
 
 Nice work!
 
 I think we should let the community to participate more in the release
 process, for example,
 1. check out a release branch called 2.7.0-release
 2. encourage people to check it out, test it and report if there is
 any regressions, bugs or issues.
 3. while we are doing the test, we can start going through the ASF
 release process locally, once we think it is ready to start a formal
 release note, it can be done very quickly.
 
 By the way, we need decide the release manager of 2.7.0 release. Is
 there anyone who volunteer to do that?
>> 
>> Sorry, I missed this mail.
>> * 2.7.0-release has been created
>> * we've froze the codebase, test is underway.
>> 
>>> I'd like to be the release manager if no one is claiming it.
>> 
>> Great, I can help you with the source/binary packaging and tagging things.
>> 
>> Jun
>> 
>>> On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
>>> 
>>> Hi,
>>> 
>>> On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang  wrote:
 
 Nice work!
 
 I think we should let the community to participate more in the release
 process, for example,
 1. check out a release branch called 2.7.0-release
 2. encourage people to check it out, test it and report if there is
 any regressions, bugs or issues.
 3. while we are doing the test, we can start going through the ASF
 release process locally, once we think it is ready to start a formal
 release note, it can be done very quickly.
 
 By the way, we need decide the release manager of 2.7.0 release. Is
 there anyone who volunteer to do that?
>>> 
>>> I'd like to be the release manager if no one is claiming it.
 
 On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
> 
> Hi, All
> 
> I am writing this mail to
> 
> * Keep you refreshed of the latest status about v2.7.0.
> * Call for efforts on code review and tests
> * Discuss possible release schedules of v2.7.0.
> 
> About v2.7, it’s going to be a milestone version, in which will make some 
> significant changes. Most importantly, we will complete all IP Clearance 
> related works. Technically speaking, it’s from this version on that a 
> Dubbo release starts fully follows the Apache rules (lawfully), totally 
> independent from any other third-party organizations or companies. 
> Secondly, this version will include many new features that have received 
> wide attention from the community, by supporting these features, we can 
> better resolve the community’s long accumulated demands. Last but not 
> least, we have made some architectural changes in this version, made 
> Dubbo closer to the micro-service architecture, take the newly introduced 
> configuration center as an example, it can work both as the center of 
> Externalized Configuration at startup and as the center of service 
> management configurations at runtime.
> 
> To summarize, the contents already included in the CodeBase are:
> 
> * Config Center: Zookeeper, Apollo, Nacos
> * Externalized Configuration
> * Service governance enhancement: dynamic configuration & routing rule
> * Repackage to 'org.apache.dubbo'
> * Java 8 support
> * Async programming support
> 
> Most of the candidates listed above are in the proposal list that we have 
> discussed in some threads before. For a more detailed description of 
> these features or how they are realized, you can refer to the draft 
> development documentations within this link[1]
> 
> Thanks to the efforts from the community (especially thank to Ian, 
> CVictory and Minxuan), most of the development work has been completed 
> and a round of code review and regression test based on some basic use 
> cases have been completed[2].
> Now I think it's time to prepare the formal release. One most 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

Thanks for the explanation.
I wait until they are settled.

What I have done til now is:

- can build locally, I've fixed several minor issues. I'll push it later.
- can deploy to snapshot repo, but the upload speed is incredibly slow (< 1k/s),
I've encountered the following error for several times:
Remote host closed connection during handshake: SSL peer shut down incorrectly
I works again after retried several times.
The deploy took me 52:42 min to finish. :(
- The gpg public keys are generated and uploaded to svn

On Mon, Jan 14, 2019 at 5:23 PM victory  wrote:
>
> Hi ,
>
>  There are still some issues about dubbo-2.7 as follow:
> 1.  In dubbo2.7 , we modify the ZookeeperTransport to make zookeeper using
> one singleton connection.
>  But when the hook is invoked after closing server, it will get
> zookeeper connection for many times for remove some data from zookeeper
> server.  But the connection may be closed by the other hook.
>  Removing the zookeeper data , it happened some error for the
> connection is closed.
>  https://github.com/apache/incubator-dubbo/issues/3218
> 2.  Http Invoke between dubbo2.6 and dubbo2.7 cannot work well.
> https://github.com/apache/incubator-dubbo/issues/3226
>
> These issue should be fixed as quickly as possible.
>
>
>
>
>
>
> Huxing Zhang  于2019年1月13日周日 下午5:58写道：
>
> > Hi Jun,
> >
> > Could you summarize the current status of the 2.7-release branch?
> > I see there are still several enhancement on this branch.
> >
> > As this is the first time to prepare for a release for me, I am trying
> > to walk through the release steps[1].
> > I might try to deploy snapshot to maven repository.
> >
> > Once we feel it is ready to do the release, I will start the formal
> > release process.
> >
> >
> > [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> >
> >
> > --
> > Best Regards！
> > Huxing
> >
> > On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> > >
> > > >>
> > > >> Nice work!
> > > >>
> > > >> I think we should let the community to participate more in the release
> > > >> process, for example,
> > > >> 1. check out a release branch called 2.7.0-release
> > > >> 2. encourage people to check it out, test it and report if there is
> > > >> any regressions, bugs or issues.
> > > >> 3. while we are doing the test, we can start going through the ASF
> > > >> release process locally, once we think it is ready to start a formal
> > > >> release note, it can be done very quickly.
> > > >>
> > > >> By the way, we need decide the release manager of 2.7.0 release. Is
> > > >> there anyone who volunteer to do that?
> > >
> > > Sorry, I missed this mail.
> > > * 2.7.0-release has been created
> > > * we've froze the codebase, test is underway.
> > >
> > > > I'd like to be the release manager if no one is claiming it.
> > >
> > > Great, I can help you with the source/binary packaging and tagging
> > things.
> > >
> > > Jun
> > >
> > > > On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
> > > >
> > > > Hi,
> > > >
> > > > On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang 
> > wrote:
> > > >>
> > > >> Nice work!
> > > >>
> > > >> I think we should let the community to participate more in the release
> > > >> process, for example,
> > > >> 1. check out a release branch called 2.7.0-release
> > > >> 2. encourage people to check it out, test it and report if there is
> > > >> any regressions, bugs or issues.
> > > >> 3. while we are doing the test, we can start going through the ASF
> > > >> release process locally, once we think it is ready to start a formal
> > > >> release note, it can be done very quickly.
> > > >>
> > > >> By the way, we need decide the release manager of 2.7.0 release. Is
> > > >> there anyone who volunteer to do that?
> > > >
> > > > I'd like to be the release manager if no one is claiming it.
> > > >>
> > > >> On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
> > > >>>
> > > >>> Hi, All
> > > >>>
> > > >>> I am writing this mail to
> > > >>>
> > > >>> * Keep you refreshed of the latest status about v2.7.0.
> > > >>> * Call for efforts on code review and tests
> > > >>> * Discuss possible release schedules of v2.7.0.
> > > >>>
> > > >>> About v2.7, it’s going to be a milestone version, in which will make
> > some significant changes. Most importantly, we will complete all IP
> > Clearance related works. Technically speaking, it’s from this version on
> > that a Dubbo release starts fully follows the Apache rules (lawfully),
> > totally independent from any other third-party organizations or companies.
> > Secondly, this version will include many new features that have received
> > wide attention from the community, by supporting these features, we can
> > better resolve the community’s long accumulated demands. Last but not
> > least, we have made some architectural changes in this version, made Dubbo
> > closer to the micro-service architecture, take the newly introduced
> > configuration center as an example, it can work both as the 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[victory]

Hi ,

 There are still some issues about dubbo-2.7 as follow:
1.  In dubbo2.7 , we modify the ZookeeperTransport to make zookeeper using
one singleton connection.
 But when the hook is invoked after closing server, it will get
zookeeper connection for many times for remove some data from zookeeper
server.  But the connection may be closed by the other hook.
 Removing the zookeeper data , it happened some error for the
connection is closed.
 https://github.com/apache/incubator-dubbo/issues/3218
2.  Http Invoke between dubbo2.6 and dubbo2.7 cannot work well.
https://github.com/apache/incubator-dubbo/issues/3226

These issue should be fixed as quickly as possible.






Huxing Zhang  于2019年1月13日周日 下午5:58写道：

> Hi Jun,
>
> Could you summarize the current status of the 2.7-release branch?
> I see there are still several enhancement on this branch.
>
> As this is the first time to prepare for a release for me, I am trying
> to walk through the release steps[1].
> I might try to deploy snapshot to maven repository.
>
> Once we feel it is ready to do the release, I will start the formal
> release process.
>
>
> [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
>
>
> --
> Best Regards！
> Huxing
>
> On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> >
> > >>
> > >> Nice work!
> > >>
> > >> I think we should let the community to participate more in the release
> > >> process, for example,
> > >> 1. check out a release branch called 2.7.0-release
> > >> 2. encourage people to check it out, test it and report if there is
> > >> any regressions, bugs or issues.
> > >> 3. while we are doing the test, we can start going through the ASF
> > >> release process locally, once we think it is ready to start a formal
> > >> release note, it can be done very quickly.
> > >>
> > >> By the way, we need decide the release manager of 2.7.0 release. Is
> > >> there anyone who volunteer to do that?
> >
> > Sorry, I missed this mail.
> > * 2.7.0-release has been created
> > * we've froze the codebase, test is underway.
> >
> > > I'd like to be the release manager if no one is claiming it.
> >
> > Great, I can help you with the source/binary packaging and tagging
> things.
> >
> > Jun
> >
> > > On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
> > >
> > > Hi,
> > >
> > > On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang 
> wrote:
> > >>
> > >> Nice work!
> > >>
> > >> I think we should let the community to participate more in the release
> > >> process, for example,
> > >> 1. check out a release branch called 2.7.0-release
> > >> 2. encourage people to check it out, test it and report if there is
> > >> any regressions, bugs or issues.
> > >> 3. while we are doing the test, we can start going through the ASF
> > >> release process locally, once we think it is ready to start a formal
> > >> release note, it can be done very quickly.
> > >>
> > >> By the way, we need decide the release manager of 2.7.0 release. Is
> > >> there anyone who volunteer to do that?
> > >
> > > I'd like to be the release manager if no one is claiming it.
> > >>
> > >> On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
> > >>>
> > >>> Hi, All
> > >>>
> > >>> I am writing this mail to
> > >>>
> > >>> * Keep you refreshed of the latest status about v2.7.0.
> > >>> * Call for efforts on code review and tests
> > >>> * Discuss possible release schedules of v2.7.0.
> > >>>
> > >>> About v2.7, it’s going to be a milestone version, in which will make
> some significant changes. Most importantly, we will complete all IP
> Clearance related works. Technically speaking, it’s from this version on
> that a Dubbo release starts fully follows the Apache rules (lawfully),
> totally independent from any other third-party organizations or companies.
> Secondly, this version will include many new features that have received
> wide attention from the community, by supporting these features, we can
> better resolve the community’s long accumulated demands. Last but not
> least, we have made some architectural changes in this version, made Dubbo
> closer to the micro-service architecture, take the newly introduced
> configuration center as an example, it can work both as the center of
> Externalized Configuration at startup and as the center of service
> management configurations at runtime.
> > >>>
> > >>> To summarize, the contents already included in the CodeBase are:
> > >>>
> > >>> * Config Center: Zookeeper, Apollo, Nacos
> > >>> * Externalized Configuration
> > >>> * Service governance enhancement: dynamic configuration & routing
> rule
> > >>> * Repackage to 'org.apache.dubbo'
> > >>> * Java 8 support
> > >>> * Async programming support
> > >>>
> > >>> Most of the candidates listed above are in the proposal list that we
> have discussed in some threads before. For a more detailed description of
> these features or how they are realized, you can refer to the draft
> development documentations within this link[1]
> > >>>
> > >>> Thanks to the efforts 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi Jun,

Could you summarize the current status of the 2.7-release branch?
I see there are still several enhancement on this branch.

As this is the first time to prepare for a release for me, I am trying
to walk through the release steps[1].
I might try to deploy snapshot to maven repository.

Once we feel it is ready to do the release, I will start the formal
release process.


[1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html


-- 
Best Regards！
Huxing

On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
>
> >>
> >> Nice work!
> >>
> >> I think we should let the community to participate more in the release
> >> process, for example,
> >> 1. check out a release branch called 2.7.0-release
> >> 2. encourage people to check it out, test it and report if there is
> >> any regressions, bugs or issues.
> >> 3. while we are doing the test, we can start going through the ASF
> >> release process locally, once we think it is ready to start a formal
> >> release note, it can be done very quickly.
> >>
> >> By the way, we need decide the release manager of 2.7.0 release. Is
> >> there anyone who volunteer to do that?
>
> Sorry, I missed this mail.
> * 2.7.0-release has been created
> * we've froze the codebase, test is underway.
>
> > I'd like to be the release manager if no one is claiming it.
>
> Great, I can help you with the source/binary packaging and tagging things.
>
> Jun
>
> > On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang  wrote:
> >>
> >> Nice work!
> >>
> >> I think we should let the community to participate more in the release
> >> process, for example,
> >> 1. check out a release branch called 2.7.0-release
> >> 2. encourage people to check it out, test it and report if there is
> >> any regressions, bugs or issues.
> >> 3. while we are doing the test, we can start going through the ASF
> >> release process locally, once we think it is ready to start a formal
> >> release note, it can be done very quickly.
> >>
> >> By the way, we need decide the release manager of 2.7.0 release. Is
> >> there anyone who volunteer to do that?
> >
> > I'd like to be the release manager if no one is claiming it.
> >>
> >> On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
> >>>
> >>> Hi, All
> >>>
> >>> I am writing this mail to
> >>>
> >>> * Keep you refreshed of the latest status about v2.7.0.
> >>> * Call for efforts on code review and tests
> >>> * Discuss possible release schedules of v2.7.0.
> >>>
> >>> About v2.7, it’s going to be a milestone version, in which will make some 
> >>> significant changes. Most importantly, we will complete all IP Clearance 
> >>> related works. Technically speaking, it’s from this version on that a 
> >>> Dubbo release starts fully follows the Apache rules (lawfully), totally 
> >>> independent from any other third-party organizations or companies. 
> >>> Secondly, this version will include many new features that have received 
> >>> wide attention from the community, by supporting these features, we can 
> >>> better resolve the community’s long accumulated demands. Last but not 
> >>> least, we have made some architectural changes in this version, made 
> >>> Dubbo closer to the micro-service architecture, take the newly introduced 
> >>> configuration center as an example, it can work both as the center of 
> >>> Externalized Configuration at startup and as the center of service 
> >>> management configurations at runtime.
> >>>
> >>> To summarize, the contents already included in the CodeBase are:
> >>>
> >>> * Config Center: Zookeeper, Apollo, Nacos
> >>> * Externalized Configuration
> >>> * Service governance enhancement: dynamic configuration & routing rule
> >>> * Repackage to 'org.apache.dubbo'
> >>> * Java 8 support
> >>> * Async programming support
> >>>
> >>> Most of the candidates listed above are in the proposal list that we have 
> >>> discussed in some threads before. For a more detailed description of 
> >>> these features or how they are realized, you can refer to the draft 
> >>> development documentations within this link[1]
> >>>
> >>> Thanks to the efforts from the community (especially thank to Ian, 
> >>> CVictory and Minxuan), most of the development work has been completed 
> >>> and a round of code review and regression test based on some basic use 
> >>> cases have been completed[2].
> >>> Now I think it's time to prepare the formal release. One most important 
> >>> thing I think we should pay attention to is stability. We should 
> >>> guarantee it's stable enough before release, so we may need to put more 
> >>> effort into code review and functional testing. Based on my understanding 
> >>> of the CodeBase, such tests may at least continue to last for about 1 
> >>> week, during this period we may need to `freeze the code`, which means 
> >>> only optimization and bugfix will be allowed. After that, we can continue 
> >>> to evaluate when to start the formal vote 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Mark Thomas]

On 07/01/2019 05:14, Ian Luo wrote:
> Imteyaz,
> 
> Fastjson is simply another third-party dependency for this project.
> Besides, it's licensed under Apache Software License v2, so it is perfectly
> fine to use it without any document work as long as we don't include its
> source code.

You may need to update the NOTICE file.

Mark


> 
> Thanks,
> -Ian.
> 
> 
> On Fri, Jan 4, 2019 at 5:38 PM Imteyaz Khan  wrote:
> 
>> Not saying wrong or unallowed. What I mean to say as part of release
>> process, do we need to provide any document if we are using
>> com.alibaba.fastjson package in our code or we have to replace it. This a
>> question from me not an any conclusion :) .
>>
>>
>> On Fri, Jan 4, 2019 at 1:54 PM LiZhenNet  wrote:
>>
>>> What's wrong about it ?  Is fastjson unallowed used in Dubbo？
>>>
>>> Imteyaz Khan  于2019年1月4日周五 下午2:04写道：
>>>
 Yes. import statement refer to package com.alibaba.fastjson, below are
>>> the
 search result

 The Search "com.alibaba.fastjson" (14 hits in 11 files)


>>>
>> dubbo\dubbo-cluster\src\test\java\org\apache\dubbo\rpc\cluster\loadbalance\LoadBalanceBaseTest.java
 (1 hit)
 Line 32: import com.alibaba.fastjson.JSON;


>>>
>> dubbo\dubbo-common\src\main\java\org\apache\dubbo\common\utils\StringUtils.java
 (1 hit)
 Line 24: import com.alibaba.fastjson.JSON;


>>>
>> dubbo\dubbo-compatible\src\test\java\org\apache\dubbo\generic\GenericServiceTest.java
 (1 hit)
 Line 36: import com.alibaba.fastjson.JSON;


>>>
>> dubbo\dubbo-metadata-report\dubbo-metadata-report-api\src\test\java\org\apache\dubbo\metadata\support\AbstractMetadataReportFactoryTest.java
 (1 hit)
 Line 25: import com.alibaba.fastjson.JSON;


>>>
>> dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\filter\AccessLogFilter.java
 (1 hit)
 Line 33: import com.alibaba.fastjson.JSON;


>>>
>> dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\support\MockInvoker.java
 (1 hit)
 Line 34: import com.alibaba.fastjson.JSON;


>>>
>> dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\filter\TraceFilter.java
 (1 hit)
 Line 32: import com.alibaba.fastjson.JSON;


>>>
>> dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\telnet\InvokeTelnetHandler.java
 (2 hits)
 Line 30: import com.alibaba.fastjson.JSON;
 Line 31: import com.alibaba.fastjson.JSONObject;


>>>
>> dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectInput.java
 (1 hit)
 Line 22: import com.alibaba.fastjson.JSON;


>>>
>> dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectOutput.java
 (3 hits)
 Line 21: import com.alibaba.fastjson.serializer.JSONSerializer;
 Line 22: import com.alibaba.fastjson.serializer.SerializeWriter;
 Line 23: import com.alibaba.fastjson.serializer.SerializerFeature;


 On Fri, Jan 4, 2019 at 8:29 AM jun liu  wrote:

> Hi,
>
> Are there any IP Clearance work that need to be done but we have
>>> missed?
>
> Jun
>
>> On Jan 4, 2019, at 10:56 AM, jun liu  wrote:
>>
>> Hi,
>>
>> I have created a new branch ‘2.7.0-release’, this branch will work
>> as
> the codebase of v2.7.0, for stability purpose, I think we should code
> freeze the codebase, so please only submit necessary bugfix or
 enhancement
> patches to this branch.
>>
>> Activity can go as normal on master branch.
>>
>> For detailed release candidates of v2.7.0 I will search the commit
> history and sort them out, will send to this thread once it’s done.
>>
>> Jun
>>
>>> On Dec 27, 2018, at 11:53 PM, jun liu >  ken.lj...@gmail.com>> wrote:
>>>
>>> Hi, All
>>>
>>> I am writing this mail to
>>>
>>> * Keep you refreshed of the latest status about v2.7.0.
>>> * Call for efforts on code review and tests
>>> * Discuss possible release schedules of v2.7.0.
>>>
>>> About v2.7, it’s going to be a milestone version, in which will
>> make
> some significant changes. Most importantly, we will complete all IP
> Clearance related works. Technically speaking, it’s from this version
>>> on
> that a Dubbo release starts fully follows the Apache rules
>> (lawfully),
> totally independent from any other third-party organizations or
 companies.
> Secondly, this version will include many new features that have
>>> received
> wide attention from the community, by supporting these features, we
>> can
> better resolve the community’s long accumulated demands. Last but not
> least, we have made some architectural changes in this version, made
 Dubbo
> closer to the micro-service architecture, 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Imteyaz Khan]

Ian,
Thanks a lot for clearing my confusion.



On Monday, January 7, 2019, jun liu  wrote:

> >>
> >> Nice work!
> >>
> >> I think we should let the community to participate more in the release
> >> process, for example,
> >> 1. check out a release branch called 2.7.0-release
> >> 2. encourage people to check it out, test it and report if there is
> >> any regressions, bugs or issues.
> >> 3. while we are doing the test, we can start going through the ASF
> >> release process locally, once we think it is ready to start a formal
> >> release note, it can be done very quickly.
> >>
> >> By the way, we need decide the release manager of 2.7.0 release. Is
> >> there anyone who volunteer to do that?
>
> Sorry, I missed this mail.
> * 2.7.0-release has been created
> * we've froze the codebase, test is underway.
>
> > I'd like to be the release manager if no one is claiming it.
>
> Great, I can help you with the source/binary packaging and tagging things.
>
> Jun
>
> > On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang  wrote:
> >>
> >> Nice work!
> >>
> >> I think we should let the community to participate more in the release
> >> process, for example,
> >> 1. check out a release branch called 2.7.0-release
> >> 2. encourage people to check it out, test it and report if there is
> >> any regressions, bugs or issues.
> >> 3. while we are doing the test, we can start going through the ASF
> >> release process locally, once we think it is ready to start a formal
> >> release note, it can be done very quickly.
> >>
> >> By the way, we need decide the release manager of 2.7.0 release. Is
> >> there anyone who volunteer to do that?
> >
> > I'd like to be the release manager if no one is claiming it.
> >>
> >> On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
> >>>
> >>> Hi, All
> >>>
> >>> I am writing this mail to
> >>>
> >>> * Keep you refreshed of the latest status about v2.7.0.
> >>> * Call for efforts on code review and tests
> >>> * Discuss possible release schedules of v2.7.0.
> >>>
> >>> About v2.7, it’s going to be a milestone version, in which will make
> some significant changes. Most importantly, we will complete all IP
> Clearance related works. Technically speaking, it’s from this version on
> that a Dubbo release starts fully follows the Apache rules (lawfully),
> totally independent from any other third-party organizations or companies.
> Secondly, this version will include many new features that have received
> wide attention from the community, by supporting these features, we can
> better resolve the community’s long accumulated demands. Last but not
> least, we have made some architectural changes in this version, made Dubbo
> closer to the micro-service architecture, take the newly introduced
> configuration center as an example, it can work both as the center of
> Externalized Configuration at startup and as the center of service
> management configurations at runtime.
> >>>
> >>> To summarize, the contents already included in the CodeBase are:
> >>>
> >>> * Config Center: Zookeeper, Apollo, Nacos
> >>> * Externalized Configuration
> >>> * Service governance enhancement: dynamic configuration & routing rule
> >>> * Repackage to 'org.apache.dubbo'
> >>> * Java 8 support
> >>> * Async programming support
> >>>
> >>> Most of the candidates listed above are in the proposal list that we
> have discussed in some threads before. For a more detailed description of
> these features or how they are realized, you can refer to the draft
> development documentations within this link[1]
> >>>
> >>> Thanks to the efforts from the community (especially thank to Ian,
> CVictory and Minxuan), most of the development work has been completed and
> a round of code review and regression test based on some basic use cases
> have been completed[2].
> >>> Now I think it's time to prepare the formal release. One most
> important thing I think we should pay attention to is stability. We should
> guarantee it's stable enough before release, so we may need to put more
> effort into code review and functional testing. Based on my understanding
> of the CodeBase, such tests may at least continue to last for about 1 week,
> during this period we may need to `freeze the code`, which means only
> optimization and bugfix will be allowed. After that, we can continue to
> evaluate when to start the formal vote process.
> >>>
> >>> 1. https://github.com/apache/incubator-dubbo/issues/2919
> >>> 2. https://github.com/apache/incubator-dubbo-samples/tree/
> samples-for-2.7.0-SNAPSHOT
> >>>
> >>> Jun
> >>>
> >>
> >>
> >> --
> >> Best Regards！
> >> Huxing
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
>
>

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

>> 
>> Nice work!
>> 
>> I think we should let the community to participate more in the release
>> process, for example,
>> 1. check out a release branch called 2.7.0-release
>> 2. encourage people to check it out, test it and report if there is
>> any regressions, bugs or issues.
>> 3. while we are doing the test, we can start going through the ASF
>> release process locally, once we think it is ready to start a formal
>> release note, it can be done very quickly.
>> 
>> By the way, we need decide the release manager of 2.7.0 release. Is
>> there anyone who volunteer to do that?

Sorry, I missed this mail. 
* 2.7.0-release has been created
* we've froze the codebase, test is underway.

> I'd like to be the release manager if no one is claiming it.

Great, I can help you with the source/binary packaging and tagging things.

Jun

> On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
> 
> Hi,
> 
> On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang  wrote:
>> 
>> Nice work!
>> 
>> I think we should let the community to participate more in the release
>> process, for example,
>> 1. check out a release branch called 2.7.0-release
>> 2. encourage people to check it out, test it and report if there is
>> any regressions, bugs or issues.
>> 3. while we are doing the test, we can start going through the ASF
>> release process locally, once we think it is ready to start a formal
>> release note, it can be done very quickly.
>> 
>> By the way, we need decide the release manager of 2.7.0 release. Is
>> there anyone who volunteer to do that?
> 
> I'd like to be the release manager if no one is claiming it.
>> 
>> On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
>>> 
>>> Hi, All
>>> 
>>> I am writing this mail to
>>> 
>>> * Keep you refreshed of the latest status about v2.7.0.
>>> * Call for efforts on code review and tests
>>> * Discuss possible release schedules of v2.7.0.
>>> 
>>> About v2.7, it’s going to be a milestone version, in which will make some 
>>> significant changes. Most importantly, we will complete all IP Clearance 
>>> related works. Technically speaking, it’s from this version on that a Dubbo 
>>> release starts fully follows the Apache rules (lawfully), totally 
>>> independent from any other third-party organizations or companies. 
>>> Secondly, this version will include many new features that have received 
>>> wide attention from the community, by supporting these features, we can 
>>> better resolve the community’s long accumulated demands. Last but not 
>>> least, we have made some architectural changes in this version, made Dubbo 
>>> closer to the micro-service architecture, take the newly introduced 
>>> configuration center as an example, it can work both as the center of 
>>> Externalized Configuration at startup and as the center of service 
>>> management configurations at runtime.
>>> 
>>> To summarize, the contents already included in the CodeBase are:
>>> 
>>> * Config Center: Zookeeper, Apollo, Nacos
>>> * Externalized Configuration
>>> * Service governance enhancement: dynamic configuration & routing rule
>>> * Repackage to 'org.apache.dubbo'
>>> * Java 8 support
>>> * Async programming support
>>> 
>>> Most of the candidates listed above are in the proposal list that we have 
>>> discussed in some threads before. For a more detailed description of these 
>>> features or how they are realized, you can refer to the draft development 
>>> documentations within this link[1]
>>> 
>>> Thanks to the efforts from the community (especially thank to Ian, CVictory 
>>> and Minxuan), most of the development work has been completed and a round 
>>> of code review and regression test based on some basic use cases have been 
>>> completed[2].
>>> Now I think it's time to prepare the formal release. One most important 
>>> thing I think we should pay attention to is stability. We should guarantee 
>>> it's stable enough before release, so we may need to put more effort into 
>>> code review and functional testing. Based on my understanding of the 
>>> CodeBase, such tests may at least continue to last for about 1 week, during 
>>> this period we may need to `freeze the code`, which means only optimization 
>>> and bugfix will be allowed. After that, we can continue to evaluate when to 
>>> start the formal vote process.
>>> 
>>> 1. https://github.com/apache/incubator-dubbo/issues/2919
>>> 2. 
>>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT
>>> 
>>> Jun
>>> 
>> 
>> 
>> --
>> Best Regards！
>> Huxing
> 
> 
> 
> -- 
> Best Regards！
> Huxing

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Ian Luo]

Imteyaz,

Fastjson is simply another third-party dependency for this project.
Besides, it's licensed under Apache Software License v2, so it is perfectly
fine to use it without any document work as long as we don't include its
source code.

Thanks,
-Ian.


On Fri, Jan 4, 2019 at 5:38 PM Imteyaz Khan  wrote:

> Not saying wrong or unallowed. What I mean to say as part of release
> process, do we need to provide any document if we are using
> com.alibaba.fastjson package in our code or we have to replace it. This a
> question from me not an any conclusion :) .
>
>
> On Fri, Jan 4, 2019 at 1:54 PM LiZhenNet  wrote:
>
> > What's wrong about it ?  Is fastjson unallowed used in Dubbo？
> >
> > Imteyaz Khan  于2019年1月4日周五 下午2:04写道：
> >
> > > Yes. import statement refer to package com.alibaba.fastjson, below are
> > the
> > > search result
> > >
> > > The Search "com.alibaba.fastjson" (14 hits in 11 files)
> > >
> > >
> >
> dubbo\dubbo-cluster\src\test\java\org\apache\dubbo\rpc\cluster\loadbalance\LoadBalanceBaseTest.java
> > > (1 hit)
> > > Line 32: import com.alibaba.fastjson.JSON;
> > >
> > >
> >
> dubbo\dubbo-common\src\main\java\org\apache\dubbo\common\utils\StringUtils.java
> > > (1 hit)
> > > Line 24: import com.alibaba.fastjson.JSON;
> > >
> > >
> >
> dubbo\dubbo-compatible\src\test\java\org\apache\dubbo\generic\GenericServiceTest.java
> > > (1 hit)
> > > Line 36: import com.alibaba.fastjson.JSON;
> > >
> > >
> >
> dubbo\dubbo-metadata-report\dubbo-metadata-report-api\src\test\java\org\apache\dubbo\metadata\support\AbstractMetadataReportFactoryTest.java
> > > (1 hit)
> > > Line 25: import com.alibaba.fastjson.JSON;
> > >
> > >
> >
> dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\filter\AccessLogFilter.java
> > > (1 hit)
> > > Line 33: import com.alibaba.fastjson.JSON;
> > >
> > >
> >
> dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\support\MockInvoker.java
> > > (1 hit)
> > > Line 34: import com.alibaba.fastjson.JSON;
> > >
> > >
> >
> dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\filter\TraceFilter.java
> > > (1 hit)
> > > Line 32: import com.alibaba.fastjson.JSON;
> > >
> > >
> >
> dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\telnet\InvokeTelnetHandler.java
> > > (2 hits)
> > > Line 30: import com.alibaba.fastjson.JSON;
> > > Line 31: import com.alibaba.fastjson.JSONObject;
> > >
> > >
> >
> dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectInput.java
> > > (1 hit)
> > > Line 22: import com.alibaba.fastjson.JSON;
> > >
> > >
> >
> dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectOutput.java
> > > (3 hits)
> > > Line 21: import com.alibaba.fastjson.serializer.JSONSerializer;
> > > Line 22: import com.alibaba.fastjson.serializer.SerializeWriter;
> > > Line 23: import com.alibaba.fastjson.serializer.SerializerFeature;
> > >
> > >
> > > On Fri, Jan 4, 2019 at 8:29 AM jun liu  wrote:
> > >
> > > > Hi,
> > > >
> > > > Are there any IP Clearance work that need to be done but we have
> > missed?
> > > >
> > > > Jun
> > > >
> > > > > On Jan 4, 2019, at 10:56 AM, jun liu  wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I have created a new branch ‘2.7.0-release’, this branch will work
> as
> > > > the codebase of v2.7.0, for stability purpose, I think we should code
> > > > freeze the codebase, so please only submit necessary bugfix or
> > > enhancement
> > > > patches to this branch.
> > > > >
> > > > > Activity can go as normal on master branch.
> > > > >
> > > > > For detailed release candidates of v2.7.0 I will search the commit
> > > > history and sort them out, will send to this thread once it’s done.
> > > > >
> > > > > Jun
> > > > >
> > > > >> On Dec 27, 2018, at 11:53 PM, jun liu   > > > ken.lj...@gmail.com>> wrote:
> > > > >>
> > > > >> Hi, All
> > > > >>
> > > > >> I am writing this mail to
> > > > >>
> > > > >> * Keep you refreshed of the latest status about v2.7.0.
> > > > >> * Call for efforts on code review and tests
> > > > >> * Discuss possible release schedules of v2.7.0.
> > > > >>
> > > > >> About v2.7, it’s going to be a milestone version, in which will
> make
> > > > some significant changes. Most importantly, we will complete all IP
> > > > Clearance related works. Technically speaking, it’s from this version
> > on
> > > > that a Dubbo release starts fully follows the Apache rules
> (lawfully),
> > > > totally independent from any other third-party organizations or
> > > companies.
> > > > Secondly, this version will include many new features that have
> > received
> > > > wide attention from the community, by supporting these features, we
> can
> > > > better resolve the community’s long accumulated demands. Last but not
> > > > least, we have made some architectural changes in this version, made
> > > Dubbo
> > > > closer to the 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

On Fri, Jan 4, 2019 at 10:59 AM jun liu  wrote:
>
> Hi,
>
> Are there any IP Clearance work that need to be done but we have missed?

Is there any source code imported to the repository?
I think we need to check the NOTICE and LICENSE file to make sure it
reflects latest status of the branch.
Let's double check it during the release process.

>
> Jun
>
> > On Jan 4, 2019, at 10:56 AM, jun liu  wrote:
> >
> > Hi,
> >
> > I have created a new branch ‘2.7.0-release’, this branch will work as the 
> > codebase of v2.7.0, for stability purpose, I think we should code freeze 
> > the codebase, so please only submit necessary bugfix or enhancement patches 
> > to this branch.
> >
> > Activity can go as normal on master branch.
> >
> > For detailed release candidates of v2.7.0 I will search the commit history 
> > and sort them out, will send to this thread once it’s done.
> >
> > Jun
> >
> >> On Dec 27, 2018, at 11:53 PM, jun liu  >> > wrote:
> >>
> >> Hi, All
> >>
> >> I am writing this mail to
> >>
> >> * Keep you refreshed of the latest status about v2.7.0.
> >> * Call for efforts on code review and tests
> >> * Discuss possible release schedules of v2.7.0.
> >>
> >> About v2.7, it’s going to be a milestone version, in which will make some 
> >> significant changes. Most importantly, we will complete all IP Clearance 
> >> related works. Technically speaking, it’s from this version on that a 
> >> Dubbo release starts fully follows the Apache rules (lawfully), totally 
> >> independent from any other third-party organizations or companies. 
> >> Secondly, this version will include many new features that have received 
> >> wide attention from the community, by supporting these features, we can 
> >> better resolve the community’s long accumulated demands. Last but not 
> >> least, we have made some architectural changes in this version, made Dubbo 
> >> closer to the micro-service architecture, take the newly introduced 
> >> configuration center as an example, it can work both as the center of 
> >> Externalized Configuration at startup and as the center of service 
> >> management configurations at runtime.
> >>
> >> To summarize, the contents already included in the CodeBase are:
> >>
> >> * Config Center: Zookeeper, Apollo, Nacos
> >> * Externalized Configuration
> >> * Service governance enhancement: dynamic configuration & routing rule
> >> * Repackage to 'org.apache.dubbo'
> >> * Java 8 support
> >> * Async programming support
> >>
> >> Most of the candidates listed above are in the proposal list that we have 
> >> discussed in some threads before. For a more detailed description of these 
> >> features or how they are realized, you can refer to the draft development 
> >> documentations within this link[1]
> >>
> >> Thanks to the efforts from the community (especially thank to Ian, 
> >> CVictory and Minxuan), most of the development work has been completed and 
> >> a round of code review and regression test based on some basic use cases 
> >> have been completed[2].
> >> Now I think it's time to prepare the formal release. One most important 
> >> thing I think we should pay attention to is stability. We should guarantee 
> >> it's stable enough before release, so we may need to put more effort into 
> >> code review and functional testing. Based on my understanding of the 
> >> CodeBase, such tests may at least continue to last for about 1 week, 
> >> during this period we may need to `freeze the code`, which means only 
> >> optimization and bugfix will be allowed. After that, we can continue to 
> >> evaluate when to start the formal vote process.
> >>
> >> 1. https://github.com/apache/incubator-dubbo/issues/2919 
> >> 
> >> 2. 
> >> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT
> >>  
> >> 
> >>
> >> Jun
> >>
> >
>


-- 
Best Regards！
Huxing

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang  wrote:
>
> Nice work!
>
> I think we should let the community to participate more in the release
> process, for example,
> 1. check out a release branch called 2.7.0-release
> 2. encourage people to check it out, test it and report if there is
> any regressions, bugs or issues.
> 3. while we are doing the test, we can start going through the ASF
> release process locally, once we think it is ready to start a formal
> release note, it can be done very quickly.
>
> By the way, we need decide the release manager of 2.7.0 release. Is
> there anyone who volunteer to do that?

I'd like to be the release manager if no one is claiming it.
>
> On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
> >
> > Hi, All
> >
> > I am writing this mail to
> >
> >  * Keep you refreshed of the latest status about v2.7.0.
> >  * Call for efforts on code review and tests
> >  * Discuss possible release schedules of v2.7.0.
> >
> > About v2.7, it’s going to be a milestone version, in which will make some 
> > significant changes. Most importantly, we will complete all IP Clearance 
> > related works. Technically speaking, it’s from this version on that a Dubbo 
> > release starts fully follows the Apache rules (lawfully), totally 
> > independent from any other third-party organizations or companies. 
> > Secondly, this version will include many new features that have received 
> > wide attention from the community, by supporting these features, we can 
> > better resolve the community’s long accumulated demands. Last but not 
> > least, we have made some architectural changes in this version, made Dubbo 
> > closer to the micro-service architecture, take the newly introduced 
> > configuration center as an example, it can work both as the center of 
> > Externalized Configuration at startup and as the center of service 
> > management configurations at runtime.
> >
> > To summarize, the contents already included in the CodeBase are:
> >
> > * Config Center: Zookeeper, Apollo, Nacos
> > * Externalized Configuration
> > * Service governance enhancement: dynamic configuration & routing rule
> > * Repackage to 'org.apache.dubbo'
> > * Java 8 support
> > * Async programming support
> >
> > Most of the candidates listed above are in the proposal list that we have 
> > discussed in some threads before. For a more detailed description of these 
> > features or how they are realized, you can refer to the draft development 
> > documentations within this link[1]
> >
> > Thanks to the efforts from the community (especially thank to Ian, CVictory 
> > and Minxuan), most of the development work has been completed and a round 
> > of code review and regression test based on some basic use cases have been 
> > completed[2].
> > Now I think it's time to prepare the formal release. One most important 
> > thing I think we should pay attention to is stability. We should guarantee 
> > it's stable enough before release, so we may need to put more effort into 
> > code review and functional testing. Based on my understanding of the 
> > CodeBase, such tests may at least continue to last for about 1 week, during 
> > this period we may need to `freeze the code`, which means only optimization 
> > and bugfix will be allowed. After that, we can continue to evaluate when to 
> > start the formal vote process.
> >
> > 1. https://github.com/apache/incubator-dubbo/issues/2919
> > 2. 
> > https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT
> >
> > Jun
> >
>
>
> --
> Best Regards！
> Huxing



-- 
Best Regards！
Huxing

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Huxing Zhang]

Hi,

On Fri, Jan 4, 2019 at 5:38 PM Imteyaz Khan  wrote:
>
> Not saying wrong or unallowed. What I mean to say as part of release
> process, do we need to provide any document if we are using
> com.alibaba.fastjson package in our code or we have to replace it. This a
> question from me not an any conclusion :) .

fastjson is a json serialization library. I checked the code, all the
appearance of "com.alibaba.fastjson" are from import statements.
There is no difference with import other libraries. So there is
nothing to do with it.

>
>
> On Fri, Jan 4, 2019 at 1:54 PM LiZhenNet  wrote:
>
> > What's wrong about it ?  Is fastjson unallowed used in Dubbo？
> >
> > Imteyaz Khan  于2019年1月4日周五 下午2:04写道：
> >
> > > Yes. import statement refer to package com.alibaba.fastjson, below are
> > the
> > > search result
> > >
> > > The Search "com.alibaba.fastjson" (14 hits in 11 files)
> > >
> > >
> > dubbo\dubbo-cluster\src\test\java\org\apache\dubbo\rpc\cluster\loadbalance\LoadBalanceBaseTest.java
> > > (1 hit)
> > > Line 32: import com.alibaba.fastjson.JSON;
> > >
> > >
> > dubbo\dubbo-common\src\main\java\org\apache\dubbo\common\utils\StringUtils.java
> > > (1 hit)
> > > Line 24: import com.alibaba.fastjson.JSON;
> > >
> > >
> > dubbo\dubbo-compatible\src\test\java\org\apache\dubbo\generic\GenericServiceTest.java
> > > (1 hit)
> > > Line 36: import com.alibaba.fastjson.JSON;
> > >
> > >
> > dubbo\dubbo-metadata-report\dubbo-metadata-report-api\src\test\java\org\apache\dubbo\metadata\support\AbstractMetadataReportFactoryTest.java
> > > (1 hit)
> > > Line 25: import com.alibaba.fastjson.JSON;
> > >
> > >
> > dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\filter\AccessLogFilter.java
> > > (1 hit)
> > > Line 33: import com.alibaba.fastjson.JSON;
> > >
> > >
> > dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\support\MockInvoker.java
> > > (1 hit)
> > > Line 34: import com.alibaba.fastjson.JSON;
> > >
> > >
> > dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\filter\TraceFilter.java
> > > (1 hit)
> > > Line 32: import com.alibaba.fastjson.JSON;
> > >
> > >
> > dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\telnet\InvokeTelnetHandler.java
> > > (2 hits)
> > > Line 30: import com.alibaba.fastjson.JSON;
> > > Line 31: import com.alibaba.fastjson.JSONObject;
> > >
> > >
> > dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectInput.java
> > > (1 hit)
> > > Line 22: import com.alibaba.fastjson.JSON;
> > >
> > >
> > dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectOutput.java
> > > (3 hits)
> > > Line 21: import com.alibaba.fastjson.serializer.JSONSerializer;
> > > Line 22: import com.alibaba.fastjson.serializer.SerializeWriter;
> > > Line 23: import com.alibaba.fastjson.serializer.SerializerFeature;
> > >
> > >
> > > On Fri, Jan 4, 2019 at 8:29 AM jun liu  wrote:
> > >
> > > > Hi,
> > > >
> > > > Are there any IP Clearance work that need to be done but we have
> > missed?
> > > >
> > > > Jun
> > > >
> > > > > On Jan 4, 2019, at 10:56 AM, jun liu  wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I have created a new branch ‘2.7.0-release’, this branch will work as
> > > > the codebase of v2.7.0, for stability purpose, I think we should code
> > > > freeze the codebase, so please only submit necessary bugfix or
> > > enhancement
> > > > patches to this branch.
> > > > >
> > > > > Activity can go as normal on master branch.
> > > > >
> > > > > For detailed release candidates of v2.7.0 I will search the commit
> > > > history and sort them out, will send to this thread once it’s done.
> > > > >
> > > > > Jun
> > > > >
> > > > >> On Dec 27, 2018, at 11:53 PM, jun liu  > > > ken.lj...@gmail.com>> wrote:
> > > > >>
> > > > >> Hi, All
> > > > >>
> > > > >> I am writing this mail to
> > > > >>
> > > > >> * Keep you refreshed of the latest status about v2.7.0.
> > > > >> * Call for efforts on code review and tests
> > > > >> * Discuss possible release schedules of v2.7.0.
> > > > >>
> > > > >> About v2.7, it’s going to be a milestone version, in which will make
> > > > some significant changes. Most importantly, we will complete all IP
> > > > Clearance related works. Technically speaking, it’s from this version
> > on
> > > > that a Dubbo release starts fully follows the Apache rules (lawfully),
> > > > totally independent from any other third-party organizations or
> > > companies.
> > > > Secondly, this version will include many new features that have
> > received
> > > > wide attention from the community, by supporting these features, we can
> > > > better resolve the community’s long accumulated demands. Last but not
> > > > least, we have made some architectural changes in this version, made
> > > Dubbo
> > > > closer to the micro-service architecture, take the newly introduced
> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Imteyaz Khan]

Not saying wrong or unallowed. What I mean to say as part of release
process, do we need to provide any document if we are using
com.alibaba.fastjson package in our code or we have to replace it. This a
question from me not an any conclusion :) .


On Fri, Jan 4, 2019 at 1:54 PM LiZhenNet  wrote:

> What's wrong about it ?  Is fastjson unallowed used in Dubbo？
>
> Imteyaz Khan  于2019年1月4日周五 下午2:04写道：
>
> > Yes. import statement refer to package com.alibaba.fastjson, below are
> the
> > search result
> >
> > The Search "com.alibaba.fastjson" (14 hits in 11 files)
> >
> >
> dubbo\dubbo-cluster\src\test\java\org\apache\dubbo\rpc\cluster\loadbalance\LoadBalanceBaseTest.java
> > (1 hit)
> > Line 32: import com.alibaba.fastjson.JSON;
> >
> >
> dubbo\dubbo-common\src\main\java\org\apache\dubbo\common\utils\StringUtils.java
> > (1 hit)
> > Line 24: import com.alibaba.fastjson.JSON;
> >
> >
> dubbo\dubbo-compatible\src\test\java\org\apache\dubbo\generic\GenericServiceTest.java
> > (1 hit)
> > Line 36: import com.alibaba.fastjson.JSON;
> >
> >
> dubbo\dubbo-metadata-report\dubbo-metadata-report-api\src\test\java\org\apache\dubbo\metadata\support\AbstractMetadataReportFactoryTest.java
> > (1 hit)
> > Line 25: import com.alibaba.fastjson.JSON;
> >
> >
> dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\filter\AccessLogFilter.java
> > (1 hit)
> > Line 33: import com.alibaba.fastjson.JSON;
> >
> >
> dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\support\MockInvoker.java
> > (1 hit)
> > Line 34: import com.alibaba.fastjson.JSON;
> >
> >
> dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\filter\TraceFilter.java
> > (1 hit)
> > Line 32: import com.alibaba.fastjson.JSON;
> >
> >
> dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\telnet\InvokeTelnetHandler.java
> > (2 hits)
> > Line 30: import com.alibaba.fastjson.JSON;
> > Line 31: import com.alibaba.fastjson.JSONObject;
> >
> >
> dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectInput.java
> > (1 hit)
> > Line 22: import com.alibaba.fastjson.JSON;
> >
> >
> dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectOutput.java
> > (3 hits)
> > Line 21: import com.alibaba.fastjson.serializer.JSONSerializer;
> > Line 22: import com.alibaba.fastjson.serializer.SerializeWriter;
> > Line 23: import com.alibaba.fastjson.serializer.SerializerFeature;
> >
> >
> > On Fri, Jan 4, 2019 at 8:29 AM jun liu  wrote:
> >
> > > Hi,
> > >
> > > Are there any IP Clearance work that need to be done but we have
> missed?
> > >
> > > Jun
> > >
> > > > On Jan 4, 2019, at 10:56 AM, jun liu  wrote:
> > > >
> > > > Hi,
> > > >
> > > > I have created a new branch ‘2.7.0-release’, this branch will work as
> > > the codebase of v2.7.0, for stability purpose, I think we should code
> > > freeze the codebase, so please only submit necessary bugfix or
> > enhancement
> > > patches to this branch.
> > > >
> > > > Activity can go as normal on master branch.
> > > >
> > > > For detailed release candidates of v2.7.0 I will search the commit
> > > history and sort them out, will send to this thread once it’s done.
> > > >
> > > > Jun
> > > >
> > > >> On Dec 27, 2018, at 11:53 PM, jun liu  > > ken.lj...@gmail.com>> wrote:
> > > >>
> > > >> Hi, All
> > > >>
> > > >> I am writing this mail to
> > > >>
> > > >> * Keep you refreshed of the latest status about v2.7.0.
> > > >> * Call for efforts on code review and tests
> > > >> * Discuss possible release schedules of v2.7.0.
> > > >>
> > > >> About v2.7, it’s going to be a milestone version, in which will make
> > > some significant changes. Most importantly, we will complete all IP
> > > Clearance related works. Technically speaking, it’s from this version
> on
> > > that a Dubbo release starts fully follows the Apache rules (lawfully),
> > > totally independent from any other third-party organizations or
> > companies.
> > > Secondly, this version will include many new features that have
> received
> > > wide attention from the community, by supporting these features, we can
> > > better resolve the community’s long accumulated demands. Last but not
> > > least, we have made some architectural changes in this version, made
> > Dubbo
> > > closer to the micro-service architecture, take the newly introduced
> > > configuration center as an example, it can work both as the center of
> > > Externalized Configuration at startup and as the center of service
> > > management configurations at runtime.
> > > >>
> > > >> To summarize, the contents already included in the CodeBase are:
> > > >>
> > > >> * Config Center: Zookeeper, Apollo, Nacos
> > > >> * Externalized Configuration
> > > >> * Service governance enhancement: dynamic configuration & routing
> rule
> > > >> * Repackage to 'org.apache.dubbo'
> > > >> * Java 8 support
> > 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[LiZhenNet]

What's wrong about it ?  Is fastjson unallowed used in Dubbo？

Imteyaz Khan  于2019年1月4日周五 下午2:04写道：

> Yes. import statement refer to package com.alibaba.fastjson, below are the
> search result
>
> The Search "com.alibaba.fastjson" (14 hits in 11 files)
>
>  
> dubbo\dubbo-cluster\src\test\java\org\apache\dubbo\rpc\cluster\loadbalance\LoadBalanceBaseTest.java
> (1 hit)
> Line 32: import com.alibaba.fastjson.JSON;
>
>  
> dubbo\dubbo-common\src\main\java\org\apache\dubbo\common\utils\StringUtils.java
> (1 hit)
> Line 24: import com.alibaba.fastjson.JSON;
>
>  
> dubbo\dubbo-compatible\src\test\java\org\apache\dubbo\generic\GenericServiceTest.java
> (1 hit)
> Line 36: import com.alibaba.fastjson.JSON;
>
>  
> dubbo\dubbo-metadata-report\dubbo-metadata-report-api\src\test\java\org\apache\dubbo\metadata\support\AbstractMetadataReportFactoryTest.java
> (1 hit)
> Line 25: import com.alibaba.fastjson.JSON;
>
>  
> dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\filter\AccessLogFilter.java
> (1 hit)
> Line 33: import com.alibaba.fastjson.JSON;
>
>  
> dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\support\MockInvoker.java
> (1 hit)
> Line 34: import com.alibaba.fastjson.JSON;
>
>  
> dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\filter\TraceFilter.java
> (1 hit)
> Line 32: import com.alibaba.fastjson.JSON;
>
>  
> dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\telnet\InvokeTelnetHandler.java
> (2 hits)
> Line 30: import com.alibaba.fastjson.JSON;
> Line 31: import com.alibaba.fastjson.JSONObject;
>
>  
> dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectInput.java
> (1 hit)
> Line 22: import com.alibaba.fastjson.JSON;
>
>  
> dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectOutput.java
> (3 hits)
> Line 21: import com.alibaba.fastjson.serializer.JSONSerializer;
> Line 22: import com.alibaba.fastjson.serializer.SerializeWriter;
> Line 23: import com.alibaba.fastjson.serializer.SerializerFeature;
>
>
> On Fri, Jan 4, 2019 at 8:29 AM jun liu  wrote:
>
> > Hi,
> >
> > Are there any IP Clearance work that need to be done but we have missed?
> >
> > Jun
> >
> > > On Jan 4, 2019, at 10:56 AM, jun liu  wrote:
> > >
> > > Hi,
> > >
> > > I have created a new branch ‘2.7.0-release’, this branch will work as
> > the codebase of v2.7.0, for stability purpose, I think we should code
> > freeze the codebase, so please only submit necessary bugfix or
> enhancement
> > patches to this branch.
> > >
> > > Activity can go as normal on master branch.
> > >
> > > For detailed release candidates of v2.7.0 I will search the commit
> > history and sort them out, will send to this thread once it’s done.
> > >
> > > Jun
> > >
> > >> On Dec 27, 2018, at 11:53 PM, jun liu  > ken.lj...@gmail.com>> wrote:
> > >>
> > >> Hi, All
> > >>
> > >> I am writing this mail to
> > >>
> > >> * Keep you refreshed of the latest status about v2.7.0.
> > >> * Call for efforts on code review and tests
> > >> * Discuss possible release schedules of v2.7.0.
> > >>
> > >> About v2.7, it’s going to be a milestone version, in which will make
> > some significant changes. Most importantly, we will complete all IP
> > Clearance related works. Technically speaking, it’s from this version on
> > that a Dubbo release starts fully follows the Apache rules (lawfully),
> > totally independent from any other third-party organizations or
> companies.
> > Secondly, this version will include many new features that have received
> > wide attention from the community, by supporting these features, we can
> > better resolve the community’s long accumulated demands. Last but not
> > least, we have made some architectural changes in this version, made
> Dubbo
> > closer to the micro-service architecture, take the newly introduced
> > configuration center as an example, it can work both as the center of
> > Externalized Configuration at startup and as the center of service
> > management configurations at runtime.
> > >>
> > >> To summarize, the contents already included in the CodeBase are:
> > >>
> > >> * Config Center: Zookeeper, Apollo, Nacos
> > >> * Externalized Configuration
> > >> * Service governance enhancement: dynamic configuration & routing rule
> > >> * Repackage to 'org.apache.dubbo'
> > >> * Java 8 support
> > >> * Async programming support
> > >>
> > >> Most of the candidates listed above are in the proposal list that we
> > have discussed in some threads before. For a more detailed description of
> > these features or how they are realized, you can refer to the draft
> > development documentations within this link[1]
> > >>
> > >> Thanks to the efforts from the community (especially thank to Ian,
> > CVictory and Minxuan), most of the development work has been completed
> and
> > a round of code review and 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Imteyaz Khan]

Yes. import statement refer to package com.alibaba.fastjson, below are the
search result

The Search "com.alibaba.fastjson" (14 hits in 11 files)
 
dubbo\dubbo-cluster\src\test\java\org\apache\dubbo\rpc\cluster\loadbalance\LoadBalanceBaseTest.java
(1 hit)
Line 32: import com.alibaba.fastjson.JSON;
 dubbo\dubbo-common\src\main\java\org\apache\dubbo\common\utils\StringUtils.java
(1 hit)
Line 24: import com.alibaba.fastjson.JSON;
 
dubbo\dubbo-compatible\src\test\java\org\apache\dubbo\generic\GenericServiceTest.java
(1 hit)
Line 36: import com.alibaba.fastjson.JSON;
 
dubbo\dubbo-metadata-report\dubbo-metadata-report-api\src\test\java\org\apache\dubbo\metadata\support\AbstractMetadataReportFactoryTest.java
(1 hit)
Line 25: import com.alibaba.fastjson.JSON;
 
dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\filter\AccessLogFilter.java
(1 hit)
Line 33: import com.alibaba.fastjson.JSON;
 
dubbo\dubbo-rpc\dubbo-rpc-api\src\main\java\org\apache\dubbo\rpc\support\MockInvoker.java
(1 hit)
Line 34: import com.alibaba.fastjson.JSON;
 
dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\filter\TraceFilter.java
(1 hit)
Line 32: import com.alibaba.fastjson.JSON;
 
dubbo\dubbo-rpc\dubbo-rpc-dubbo\src\main\java\org\apache\dubbo\rpc\protocol\dubbo\telnet\InvokeTelnetHandler.java
(2 hits)
Line 30: import com.alibaba.fastjson.JSON;
Line 31: import com.alibaba.fastjson.JSONObject;
 
dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectInput.java
(1 hit)
Line 22: import com.alibaba.fastjson.JSON;
 
dubbo\dubbo-serialization\dubbo-serialization-fastjson\src\main\java\org\apache\dubbo\common\serialize\fastjson\FastJsonObjectOutput.java
(3 hits)
Line 21: import com.alibaba.fastjson.serializer.JSONSerializer;
Line 22: import com.alibaba.fastjson.serializer.SerializeWriter;
Line 23: import com.alibaba.fastjson.serializer.SerializerFeature;


On Fri, Jan 4, 2019 at 8:29 AM jun liu  wrote:

> Hi,
>
> Are there any IP Clearance work that need to be done but we have missed?
>
> Jun
>
> > On Jan 4, 2019, at 10:56 AM, jun liu  wrote:
> >
> > Hi,
> >
> > I have created a new branch ‘2.7.0-release’, this branch will work as
> the codebase of v2.7.0, for stability purpose, I think we should code
> freeze the codebase, so please only submit necessary bugfix or enhancement
> patches to this branch.
> >
> > Activity can go as normal on master branch.
> >
> > For detailed release candidates of v2.7.0 I will search the commit
> history and sort them out, will send to this thread once it’s done.
> >
> > Jun
> >
> >> On Dec 27, 2018, at 11:53 PM, jun liu  ken.lj...@gmail.com>> wrote:
> >>
> >> Hi, All
> >>
> >> I am writing this mail to
> >>
> >> * Keep you refreshed of the latest status about v2.7.0.
> >> * Call for efforts on code review and tests
> >> * Discuss possible release schedules of v2.7.0.
> >>
> >> About v2.7, it’s going to be a milestone version, in which will make
> some significant changes. Most importantly, we will complete all IP
> Clearance related works. Technically speaking, it’s from this version on
> that a Dubbo release starts fully follows the Apache rules (lawfully),
> totally independent from any other third-party organizations or companies.
> Secondly, this version will include many new features that have received
> wide attention from the community, by supporting these features, we can
> better resolve the community’s long accumulated demands. Last but not
> least, we have made some architectural changes in this version, made Dubbo
> closer to the micro-service architecture, take the newly introduced
> configuration center as an example, it can work both as the center of
> Externalized Configuration at startup and as the center of service
> management configurations at runtime.
> >>
> >> To summarize, the contents already included in the CodeBase are:
> >>
> >> * Config Center: Zookeeper, Apollo, Nacos
> >> * Externalized Configuration
> >> * Service governance enhancement: dynamic configuration & routing rule
> >> * Repackage to 'org.apache.dubbo'
> >> * Java 8 support
> >> * Async programming support
> >>
> >> Most of the candidates listed above are in the proposal list that we
> have discussed in some threads before. For a more detailed description of
> these features or how they are realized, you can refer to the draft
> development documentations within this link[1]
> >>
> >> Thanks to the efforts from the community (especially thank to Ian,
> CVictory and Minxuan), most of the development work has been completed and
> a round of code review and regression test based on some basic use cases
> have been completed[2].
> >> Now I think it's time to prepare the formal release. One most important
> thing I think we should pay attention to is stability. We should guarantee
> it's stable enough before release, so we may need to put more effort into
> code review and functional testing. Based on my 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

Hi,

Are there any IP Clearance work that need to be done but we have missed?

Jun

> On Jan 4, 2019, at 10:56 AM, jun liu  wrote:
> 
> Hi,
> 
> I have created a new branch ‘2.7.0-release’, this branch will work as the 
> codebase of v2.7.0, for stability purpose, I think we should code freeze the 
> codebase, so please only submit necessary bugfix or enhancement patches to 
> this branch.
> 
> Activity can go as normal on master branch.
> 
> For detailed release candidates of v2.7.0 I will search the commit history 
> and sort them out, will send to this thread once it’s done.
> 
> Jun
> 
>> On Dec 27, 2018, at 11:53 PM, jun liu > > wrote:
>> 
>> Hi, All
>> 
>> I am writing this mail to
>> 
>> * Keep you refreshed of the latest status about v2.7.0.
>> * Call for efforts on code review and tests
>> * Discuss possible release schedules of v2.7.0.
>> 
>> About v2.7, it’s going to be a milestone version, in which will make some 
>> significant changes. Most importantly, we will complete all IP Clearance 
>> related works. Technically speaking, it’s from this version on that a Dubbo 
>> release starts fully follows the Apache rules (lawfully), totally 
>> independent from any other third-party organizations or companies. Secondly, 
>> this version will include many new features that have received wide 
>> attention from the community, by supporting these features, we can better 
>> resolve the community’s long accumulated demands. Last but not least, we 
>> have made some architectural changes in this version, made Dubbo closer to 
>> the micro-service architecture, take the newly introduced configuration 
>> center as an example, it can work both as the center of Externalized 
>> Configuration at startup and as the center of service management 
>> configurations at runtime.
>> 
>> To summarize, the contents already included in the CodeBase are:
>> 
>> * Config Center: Zookeeper, Apollo, Nacos
>> * Externalized Configuration
>> * Service governance enhancement: dynamic configuration & routing rule
>> * Repackage to 'org.apache.dubbo'
>> * Java 8 support
>> * Async programming support
>> 
>> Most of the candidates listed above are in the proposal list that we have 
>> discussed in some threads before. For a more detailed description of these 
>> features or how they are realized, you can refer to the draft development 
>> documentations within this link[1]
>> 
>> Thanks to the efforts from the community (especially thank to Ian, CVictory 
>> and Minxuan), most of the development work has been completed and a round of 
>> code review and regression test based on some basic use cases have been 
>> completed[2].
>> Now I think it's time to prepare the formal release. One most important 
>> thing I think we should pay attention to is stability. We should guarantee 
>> it's stable enough before release, so we may need to put more effort into 
>> code review and functional testing. Based on my understanding of the 
>> CodeBase, such tests may at least continue to last for about 1 week, during 
>> this period we may need to `freeze the code`, which means only optimization 
>> and bugfix will be allowed. After that, we can continue to evaluate when to 
>> start the formal vote process.
>> 
>> 1. https://github.com/apache/incubator-dubbo/issues/2919 
>> 
>> 2. 
>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT
>>  
>> 
>> 
>> Jun
>> 
> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

Hi,

I have created a new branch ‘2.7.0-release’, this branch will work as the 
codebase of v2.7.0, for stability purpose, I think we should code freeze the 
codebase, so please only submit necessary bugfix or enhancement patches to this 
branch.

Activity can go as normal on master branch.

For detailed release candidates of v2.7.0 I will search the commit history and 
sort them out, will send to this thread once it’s done.

Jun

> On Dec 27, 2018, at 11:53 PM, jun liu  wrote:
> 
> Hi, All
> 
> I am writing this mail to
> 
> * Keep you refreshed of the latest status about v2.7.0.
> * Call for efforts on code review and tests
> * Discuss possible release schedules of v2.7.0.
> 
> About v2.7, it’s going to be a milestone version, in which will make some 
> significant changes. Most importantly, we will complete all IP Clearance 
> related works. Technically speaking, it’s from this version on that a Dubbo 
> release starts fully follows the Apache rules (lawfully), totally independent 
> from any other third-party organizations or companies. Secondly, this version 
> will include many new features that have received wide attention from the 
> community, by supporting these features, we can better resolve the 
> community’s long accumulated demands. Last but not least, we have made some 
> architectural changes in this version, made Dubbo closer to the micro-service 
> architecture, take the newly introduced configuration center as an example, 
> it can work both as the center of Externalized Configuration at startup and 
> as the center of service management configurations at runtime.
> 
> To summarize, the contents already included in the CodeBase are:
> 
> * Config Center: Zookeeper, Apollo, Nacos
> * Externalized Configuration
> * Service governance enhancement: dynamic configuration & routing rule
> * Repackage to 'org.apache.dubbo'
> * Java 8 support
> * Async programming support
> 
> Most of the candidates listed above are in the proposal list that we have 
> discussed in some threads before. For a more detailed description of these 
> features or how they are realized, you can refer to the draft development 
> documentations within this link[1]
> 
> Thanks to the efforts from the community (especially thank to Ian, CVictory 
> and Minxuan), most of the development work has been completed and a round of 
> code review and regression test based on some basic use cases have been 
> completed[2].
> Now I think it's time to prepare the formal release. One most important thing 
> I think we should pay attention to is stability. We should guarantee it's 
> stable enough before release, so we may need to put more effort into code 
> review and functional testing. Based on my understanding of the CodeBase, 
> such tests may at least continue to last for about 1 week, during this period 
> we may need to `freeze the code`, which means only optimization and bugfix 
> will be allowed. After that, we can continue to evaluate when to start the 
> formal vote process.
> 
> 1. https://github.com/apache/incubator-dubbo/issues/2919
> 2. 
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT
> 
> Jun
> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

> In some places I see there are reference of code which is under
> *com.alibaba.fastjson,
> *as part of release process should we also consider rewriting them or
> providing license from the owner org?

I remember fastjson is a thirt-party dependency of Dubbo, do you mean you saw 
some source codes directly under ‘com.alibaba.fastjson’?

Jun

> On Dec 28, 2018, at 2:42 PM, Imteyaz Khan  wrote:
> 
> In some places I see there are reference of code which is under
> *com.alibaba.fastjson,
> *as part of release process should we also consider rewriting them or
> providing license from the owner org?
> 
> 
> 
> On Fri, Dec 28, 2018 at 8:15 AM Huxing Zhang  wrote:
> 
>> Nice work!
>> 
>> I think we should let the community to participate more in the release
>> process, for example,
>> 1. check out a release branch called 2.7.0-release
>> 2. encourage people to check it out, test it and report if there is
>> any regressions, bugs or issues.
>> 3. while we are doing the test, we can start going through the ASF
>> release process locally, once we think it is ready to start a formal
>> release note, it can be done very quickly.
>> 
>> By the way, we need decide the release manager of 2.7.0 release. Is
>> there anyone who volunteer to do that?
>> 
>> On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
>>> 
>>> Hi, All
>>> 
>>> I am writing this mail to
>>> 
>>> * Keep you refreshed of the latest status about v2.7.0.
>>> * Call for efforts on code review and tests
>>> * Discuss possible release schedules of v2.7.0.
>>> 
>>> About v2.7, it’s going to be a milestone version, in which will make
>> some significant changes. Most importantly, we will complete all IP
>> Clearance related works. Technically speaking, it’s from this version on
>> that a Dubbo release starts fully follows the Apache rules (lawfully),
>> totally independent from any other third-party organizations or companies.
>> Secondly, this version will include many new features that have received
>> wide attention from the community, by supporting these features, we can
>> better resolve the community’s long accumulated demands. Last but not
>> least, we have made some architectural changes in this version, made Dubbo
>> closer to the micro-service architecture, take the newly introduced
>> configuration center as an example, it can work both as the center of
>> Externalized Configuration at startup and as the center of service
>> management configurations at runtime.
>>> 
>>> To summarize, the contents already included in the CodeBase are:
>>> 
>>> * Config Center: Zookeeper, Apollo, Nacos
>>> * Externalized Configuration
>>> * Service governance enhancement: dynamic configuration & routing rule
>>> * Repackage to 'org.apache.dubbo'
>>> * Java 8 support
>>> * Async programming support
>>> 
>>> Most of the candidates listed above are in the proposal list that we
>> have discussed in some threads before. For a more detailed description of
>> these features or how they are realized, you can refer to the draft
>> development documentations within this link[1]
>>> 
>>> Thanks to the efforts from the community (especially thank to Ian,
>> CVictory and Minxuan), most of the development work has been completed and
>> a round of code review and regression test based on some basic use cases
>> have been completed[2].
>>> Now I think it's time to prepare the formal release. One most important
>> thing I think we should pay attention to is stability. We should guarantee
>> it's stable enough before release, so we may need to put more effort into
>> code review and functional testing. Based on my understanding of the
>> CodeBase, such tests may at least continue to last for about 1 week, during
>> this period we may need to `freeze the code`, which means only optimization
>> and bugfix will be allowed. After that, we can continue to evaluate when to
>> start the formal vote process.
>>> 
>>> 1. https://github.com/apache/incubator-dubbo/issues/2919
>>> 2.
>> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT
>>> 
>>> Jun
>>> 
>> 
>> 
>> --
>> Best Regards！
>> Huxing
>> 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Imteyaz Khan]

In some places I see there are reference of code which is under
*com.alibaba.fastjson,
*as part of release process should we also consider rewriting them or
providing license from the owner org?



On Fri, Dec 28, 2018 at 8:15 AM Huxing Zhang  wrote:

> Nice work!
>
> I think we should let the community to participate more in the release
> process, for example,
> 1. check out a release branch called 2.7.0-release
> 2. encourage people to check it out, test it and report if there is
> any regressions, bugs or issues.
> 3. while we are doing the test, we can start going through the ASF
> release process locally, once we think it is ready to start a formal
> release note, it can be done very quickly.
>
> By the way, we need decide the release manager of 2.7.0 release. Is
> there anyone who volunteer to do that?
>
> On Thu, Dec 27, 2018 at 11:53 PM jun liu  wrote:
> >
> > Hi, All
> >
> > I am writing this mail to
> >
> >  * Keep you refreshed of the latest status about v2.7.0.
> >  * Call for efforts on code review and tests
> >  * Discuss possible release schedules of v2.7.0.
> >
> > About v2.7, it’s going to be a milestone version, in which will make
> some significant changes. Most importantly, we will complete all IP
> Clearance related works. Technically speaking, it’s from this version on
> that a Dubbo release starts fully follows the Apache rules (lawfully),
> totally independent from any other third-party organizations or companies.
> Secondly, this version will include many new features that have received
> wide attention from the community, by supporting these features, we can
> better resolve the community’s long accumulated demands. Last but not
> least, we have made some architectural changes in this version, made Dubbo
> closer to the micro-service architecture, take the newly introduced
> configuration center as an example, it can work both as the center of
> Externalized Configuration at startup and as the center of service
> management configurations at runtime.
> >
> > To summarize, the contents already included in the CodeBase are:
> >
> > * Config Center: Zookeeper, Apollo, Nacos
> > * Externalized Configuration
> > * Service governance enhancement: dynamic configuration & routing rule
> > * Repackage to 'org.apache.dubbo'
> > * Java 8 support
> > * Async programming support
> >
> > Most of the candidates listed above are in the proposal list that we
> have discussed in some threads before. For a more detailed description of
> these features or how they are realized, you can refer to the draft
> development documentations within this link[1]
> >
> > Thanks to the efforts from the community (especially thank to Ian,
> CVictory and Minxuan), most of the development work has been completed and
> a round of code review and regression test based on some basic use cases
> have been completed[2].
> > Now I think it's time to prepare the formal release. One most important
> thing I think we should pay attention to is stability. We should guarantee
> it's stable enough before release, so we may need to put more effort into
> code review and functional testing. Based on my understanding of the
> CodeBase, such tests may at least continue to last for about 1 week, during
> this period we may need to `freeze the code`, which means only optimization
> and bugfix will be allowed. After that, we can continue to evaluate when to
> start the formal vote process.
> >
> > 1. https://github.com/apache/incubator-dubbo/issues/2919
> > 2.
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT
> >
> > Jun
> >
>
>
> --
> Best Regards！
> Huxing
>

[Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[jun liu]

Hi, All

I am writing this mail to

 * Keep you refreshed of the latest status about v2.7.0.
 * Call for efforts on code review and tests
 * Discuss possible release schedules of v2.7.0.

About v2.7, it’s going to be a milestone version, in which will make some 
significant changes. Most importantly, we will complete all IP Clearance 
related works. Technically speaking, it’s from this version on that a Dubbo 
release starts fully follows the Apache rules (lawfully), totally independent 
from any other third-party organizations or companies. Secondly, this version 
will include many new features that have received wide attention from the 
community, by supporting these features, we can better resolve the community’s 
long accumulated demands. Last but not least, we have made some architectural 
changes in this version, made Dubbo closer to the micro-service architecture, 
take the newly introduced configuration center as an example, it can work both 
as the center of Externalized Configuration at startup and as the center of 
service management configurations at runtime.

To summarize, the contents already included in the CodeBase are:

* Config Center: Zookeeper, Apollo, Nacos
* Externalized Configuration
* Service governance enhancement: dynamic configuration & routing rule
* Repackage to 'org.apache.dubbo'
* Java 8 support
* Async programming support

Most of the candidates listed above are in the proposal list that we have 
discussed in some threads before. For a more detailed description of these 
features or how they are realized, you can refer to the draft development 
documentations within this link[1]

Thanks to the efforts from the community (especially thank to Ian, CVictory and 
Minxuan), most of the development work has been completed and a round of code 
review and regression test based on some basic use cases have been completed[2].
Now I think it's time to prepare the formal release. One most important thing I 
think we should pay attention to is stability. We should guarantee it's stable 
enough before release, so we may need to put more effort into code review and 
functional testing. Based on my understanding of the CodeBase, such tests may 
at least continue to last for about 1 week, during this period we may need to 
`freeze the code`, which means only optimization and bugfix will be allowed. 
After that, we can continue to evaluate when to start the formal vote process.

1. https://github.com/apache/incubator-dubbo/issues/2919
2. 
https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT

Jun