Congratulations : )
Best Wishes & Regards
---
Mabin
Zheng Feng 于2018年11月13日周二 下午5:53写道：
> welcome on board !
>
> Willem Jiang 于2018年11月13日周二 上午11:54写道：
>
> > Please join me and the rest of the ServiceComb PPMC members in welcoming
> > our
> > new ServiceComb comm
If java-chassis and Service Center are ready, it is recommended to publish
first.
Some issues submitted by users have been resolved in the new release.
Best Wishes & Regards
---
Mabin
Willem Jiang 于2018年11月13日周二 下午5:32写道：
> We are thinking rename the saga project
Congratulations!
Best Wishes & Regards
---
Mabin
Zheng Feng 于2018年11月13日周二 下午5:53写道：
> welcome on board !
>
> Willem Jiang 于2018年11月13日周二 上午10:47写道：
>
> > Please join me and the rest of the ServiceComb PPMC members in welcoming
> > our
> > new ServiceComb committ
of course.
These two days are busy with supporting ServiceComb community activities...
Currently, I have already completed the modification and submitted it.
If there is a problem with the follow-up, I will submit the PR and fix it
in time.
Best Wishes & Regards
---
Ma
OK, that makes sense.
Willem Jiang 于2018年11月14日周三 下午5:32写道：
> Agree we need the migration document for it.
>
> There are lots change in the 0.3.0-SNAPSHOT, if we want the user use
> the new added transports, we may need to back port those patch to
> 0.2.0 branch.
>
> Willem Jiang
>
> Twitter: wi
Agree we need the migration document for it.
There are lots change in the 0.3.0-SNAPSHOT, if we want the user use
the new added transports, we may need to back port those patch to
0.2.0 branch.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Nov 14, 2018 at 5:29 PM Zheng Feng wrote:
Willem Jiang 于2018年11月14日周三 下午5:13写道：
> I think we can keep the annotation there , but mark it as deprecated
> and add the new annotation there. So there could be a very big change
> on the customer project.
>
I agree that could be a problem with upgrading from the old version and
should be very
I think we can keep the annotation there , but mark it as deprecated
and add the new annotation there. So there could be a very big change
on the customer project.
We could consider to remove the old implementation in the Pack 0.4.0
release. Beside the the package rename, we also need to rename the
