Re: Discussion about java chassis roadmap

[wjm wjm]

 adjust roadmap, remove SCB-759, add SCB-770:

[SCB-748 ] ServiceComb
engine resource optimize
[SCB-756 ] improve
development phase flexibility

[SCB-719 ] automated
integration testing support complex processes

[SCB-757 ] provide common
governance match mechanism

[SCB-749 ] mybatis for
reactive mode
[SCB-758 ] extract core
engine not depend on springremove

[SCB-770 ] invoke 3rd
RESTful service

2018-07-20 11:21 GMT+08:00 bismy :

> Agree with this order. And SCB-748 SCB-756 is related, should take most
> priority.
>
>
>
>
> -- 原始邮件 --
> 发件人: "wjm wjm";
> 发送时间: 2018年7月19日(星期四) 下午4:29
> 收件人: "dev";
>
> 主题: Re: Discussion about java chassis roadmap
>
>
>
> Sort by importance:
>
> [SCB-748 ] ServiceComb
> engine resource optimize
> [SCB-756 ] improve
> development phase flexibility
>
> [SCB-719 ] automated
> integration testing support complex processes
>
> [SCB-757 ] provide common
> governance match mechanism
>
> [SCB-749 ] mybatis for
> reactive mode
> [SCB-758 ] extract core
> engine not depend on spring
>
> 2018-07-19 16:20 GMT+08:00 wjm wjm :
>
> > infact all of them are very very big task
> > once we decided to start them, we must create subtasks.
> >
> > now, we just need to decide what tasks will be start?
> >
> > 2018-07-19 15:44 GMT+08:00 Willem Jiang :
> >
> >> Yeah, as we are heading to ServiceComb 1.0.0. It's the time for us to
> make
> >> some plan for the new release.
> >> Jimin,  I think 719 and 758 are very big task,  I think we may need to
> >> create some small tasks to break down them a bit.
> >>
> >>
> >> Willem Jiang
> >>
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >>
> >> On Thu, Jul 19, 2018 at 10:34 AM, wjm wjm  wrote:
> >>
> >> > we need to plan roadmap for the next stage
> >> > i create below issues to trace what i think is important.
> >> > please feel free to add your opinions/new isses/ and so on
> >> >
> >> > [SCB-719 ] automated
> >> > integration testing support complex processes
> >> >
> >> >
> >> > [SCB-748 ] ServiceComb
> >> > engine resource optimize
> >> >
> >> > [SCB-756 ] improve
> >> > development phase flexibility
> >> >
> >> > [SCB-757 ] provide
> >> common
> >> > governance match mechanism
> >> >
> >> > [SCB-749 ] mybatis for
> >> > reactive mode
> >> >
> >> > [SCB-758 ] extract
> core
> >> > engine not depend on spring
> >> >
> >>
> >
> >
>

Re: Re: [DISCUSS]Shall we upgrade Java-chassis to support Spring Boot2

[Zen Lin]

+1 to Willem's suggestion.
Could someone ask yaohaishi to create a issue track for this, upgrade to
support Spring Boot2.
And when he find an actual issue on testing it, can create a  sub issue
under the issue of "upgrade to support Spring Boot2".

Thus,  Mabin and the users can know the detail progress or report what
issue they meet through the issue.

Best Regards,
---
Zen Lin
zenlintechnofr...@gmail.com
Focused on Micro Service and Apache ServiceComb


Willem Jiang  于2018年7月20日周五 下午4:40写道：

> SCB-758 is a big task.  I don't think we need to wait for it done to
> support Spring Boot 2.x.
> Yaohaishi already did some test on it,  we just need to keep fix the actual
> issue we find
>
> my suggestion is we support Spring Boot 1.x by default, and add a Spring
> Boot 2.x profile to the user who want to use Spring Boot 2.x.
>
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Jul 20, 2018 at 4:25 PM, Bin Ma  wrote:
>
> > Currently I have recommended user like Chuanzhi Boke to develop based on
> > the spring boot1.x version to ensure that user development is not
> blocked.
> >
> > I agree with bimsy's idea,users' demands and scenes are clear,an task
> > should be created to trace.
> >
> > As I know, SCB-758(https://issues.apache.org/jira/browse/SCB-758) is a
> > task
> > to remove the dependency of java-chassis on spring, I'm not sure if this
> > task is completed first, and it is more helpful to support the
> springboot2
> > ?
> >
> > 2018-07-20 11:24 GMT+08:00 Willem Jiang :
> >
> > > From the Spring Boot2 migration guide[1], the class package and name
> was
> > > changed.
> > >
> > > We may need to create different module to handle the class package
> change
> > > issue.
> > >
> > > [1]
> > > https://github.com/spring-projects/spring-boot/wiki/
> > > Spring-Boot-2.0-Migration-Guide#embedded-containers-package-structure
> > >
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Fri, Jul 20, 2018 at 10:29 AM, yhs0092  wrote:
> > >
> > > > I tried to upgrade Java-Chassis to support SpringBoot2 before, but
> > > failed.
> > > >
> > > >
> > > > There are two problems. The first one is in our bean.xml file， the
> xsd
> > > > file is imported like below:
> > > > ```
> > > > classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
> > > > ```
> > > > but 3.0 version xsd file does not exist anymore.
> > > >
> > > > This is still resolvable, but for the second problem, I still haven't
> > > > found a way to resolve it.
> > > >
> > > >
> > > > When my service demo is started, an error occurs:
> > > > ```
> > > > 2018-03-13 22:57:18.396  WARN 6 --- [   main]
> > > > ConfigServletWebServerApplicationContext : Exception encountered
> > during
> > > > context initialization - cancelling refresh attempt:
> > > > org.springframework.beans.factory.BeanDefinitionStoreException:
> Failed
> > > to
> > > > parse configuration class [org.apache.servicecomb.
> > > > springboot.starter.transport.RestServletInitializer]; nested
> exception
> > > is
> > > > java.io.FileNotFoundException: class path resource
> > > > [org/springframework/boot/context/embedded/
> > > AbstractConfigurableEmbeddedServletContainer.class]
> > > > cannot be opened because it does not exist
> > > > ```
> > > > Because AbstractConfigurableEmbeddedServletContainer is removed in
> > > > SpringBoot2, and our RestServletInitializer is extended from this
> > class,
> > > > maybe we cannot upgrade to SpringBoot2 by simply change the maven
> > > > dependency.
> > > > And once we refactor our RestServletInitializer, the java-chassis may
> > not
> > > > be compatible with SpringBoot1.
> > > >
> > > >
> > > >
> > > > 在 2018-07-20 08:57:05，"wjm wjm"  写道：
> > > > >not enough, must exclude old spring also
> > > > >
> > > > >2018-07-20 6:44 GMT+08:00 Willem Jiang :
> > > > >
> > > > >> How about let user override the version of Spring Boot in their
> > > > application
> > > > >> and give it a try.
> > > > >> Just like what we do with JDK9 here[1]
> > > > >> If there is any issue comes out, we can keep digging it.
> > > > >>
> > > > >> [1]https://github.com/apache/incubator-servicecomb-saga/issues/76
> > > > >>
> > > > >>
> > > > >> Willem Jiang
> > > > >>
> > > > >> Twitter: willemjiang
> > > > >> Weibo: 姜宁willem
> > > > >>
> > > > >> On Thu, Jul 19, 2018 at 8:26 PM, Bin Ma 
> > wrote:
> > > > >>
> > > > >> > Hi,
> > > > >> >   Java-chassis currently supports Spirng Boot 1.5.12 version.
> > > > >> >
> > > > >> >   In fact, some enterprise users develop their coursewares based
> > on
> > > > >> Spring
> > > > >> > Boot2, so hopefully Java-chassis can support Spring Boot2, such
> as
> > > > >> Chuanzhi
> > > > >> > Boke.
> > > > >> >
> > > > >> >   I think it's neccessary to discuss the plan about  upgrading
> > > > >> > Java-Chasssis to support  Spring Boot2 to satisfy users'
> scenario.
> > > > >> >
> > > > >> >   Any thoughts and any troubles to upgrading, please feel free
> to
> 

Re: Re: [DISCUSS]Shall we upgrade Java-chassis to support Spring Boot2

[Kirin Wang]

I think we also have a sub-task of support Spring Boot 2 ,  which  is  add
Spring Boot 2.X option in start.servicecomb.io .

Zen Lin  于2018年7月23日周一 上午9:15写道：

> +1 to Willem's suggestion.
> Could someone ask yaohaishi to create a issue track for this, upgrade to
> support Spring Boot2.
> And when he find an actual issue on testing it, can create a  sub issue
> under the issue of "upgrade to support Spring Boot2".
>
> Thus,  Mabin and the users can know the detail progress or report what
> issue they meet through the issue.
>
> Best Regards,
> ---
> Zen Lin
> zenlintechnofr...@gmail.com
> Focused on Micro Service and Apache ServiceComb
>
>
> Willem Jiang  于2018年7月20日周五 下午4:40写道：
>
> > SCB-758 is a big task.  I don't think we need to wait for it done to
> > support Spring Boot 2.x.
> > Yaohaishi already did some test on it,  we just need to keep fix the
> actual
> > issue we find
> >
> > my suggestion is we support Spring Boot 1.x by default, and add a Spring
> > Boot 2.x profile to the user who want to use Spring Boot 2.x.
> >
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Fri, Jul 20, 2018 at 4:25 PM, Bin Ma  wrote:
> >
> > > Currently I have recommended user like Chuanzhi Boke to develop based
> on
> > > the spring boot1.x version to ensure that user development is not
> > blocked.
> > >
> > > I agree with bimsy's idea,users' demands and scenes are clear,an task
> > > should be created to trace.
> > >
> > > As I know, SCB-758(https://issues.apache.org/jira/browse/SCB-758) is a
> > > task
> > > to remove the dependency of java-chassis on spring, I'm not sure if
> this
> > > task is completed first, and it is more helpful to support the
> > springboot2
> > > ?
> > >
> > > 2018-07-20 11:24 GMT+08:00 Willem Jiang :
> > >
> > > > From the Spring Boot2 migration guide[1], the class package and name
> > was
> > > > changed.
> > > >
> > > > We may need to create different module to handle the class package
> > change
> > > > issue.
> > > >
> > > > [1]
> > > > https://github.com/spring-projects/spring-boot/wiki/
> > > > Spring-Boot-2.0-Migration-Guide#embedded-containers-package-structure
> > > >
> > > >
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Fri, Jul 20, 2018 at 10:29 AM, yhs0092  wrote:
> > > >
> > > > > I tried to upgrade Java-Chassis to support SpringBoot2 before, but
> > > > failed.
> > > > >
> > > > >
> > > > > There are two problems. The first one is in our bean.xml file， the
> > xsd
> > > > > file is imported like below:
> > > > > ```
> > > > >
> classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
> > > > > ```
> > > > > but 3.0 version xsd file does not exist anymore.
> > > > >
> > > > > This is still resolvable, but for the second problem, I still
> haven't
> > > > > found a way to resolve it.
> > > > >
> > > > >
> > > > > When my service demo is started, an error occurs:
> > > > > ```
> > > > > 2018-03-13 22:57:18.396  WARN 6 --- [   main]
> > > > > ConfigServletWebServerApplicationContext : Exception encountered
> > > during
> > > > > context initialization - cancelling refresh attempt:
> > > > > org.springframework.beans.factory.BeanDefinitionStoreException:
> > Failed
> > > > to
> > > > > parse configuration class [org.apache.servicecomb.
> > > > > springboot.starter.transport.RestServletInitializer]; nested
> > exception
> > > > is
> > > > > java.io.FileNotFoundException: class path resource
> > > > > [org/springframework/boot/context/embedded/
> > > > AbstractConfigurableEmbeddedServletContainer.class]
> > > > > cannot be opened because it does not exist
> > > > > ```
> > > > > Because AbstractConfigurableEmbeddedServletContainer is removed in
> > > > > SpringBoot2, and our RestServletInitializer is extended from this
> > > class,
> > > > > maybe we cannot upgrade to SpringBoot2 by simply change the maven
> > > > > dependency.
> > > > > And once we refactor our RestServletInitializer, the java-chassis
> may
> > > not
> > > > > be compatible with SpringBoot1.
> > > > >
> > > > >
> > > > >
> > > > > 在 2018-07-20 08:57:05，"wjm wjm"  写道：
> > > > > >not enough, must exclude old spring also
> > > > > >
> > > > > >2018-07-20 6:44 GMT+08:00 Willem Jiang :
> > > > > >
> > > > > >> How about let user override the version of Spring Boot in their
> > > > > application
> > > > > >> and give it a try.
> > > > > >> Just like what we do with JDK9 here[1]
> > > > > >> If there is any issue comes out, we can keep digging it.
> > > > > >>
> > > > > >> [1]
> https://github.com/apache/incubator-servicecomb-saga/issues/76
> > > > > >>
> > > > > >>
> > > > > >> Willem Jiang
> > > > > >>
> > > > > >> Twitter: willemjiang
> > > > > >> Weibo: 姜宁willem
> > > > > >>
> > > > > >> On Thu, Jul 19, 2018 at 8:26 PM, Bin Ma 
> > > wrote:
> > > > > >>
> > > > > >> > Hi,
> > > > > >> >   Java-chassis currently supports Spirng Boot 1.5.12 version.
> > > > > >> >
> > > > > >> >   In fact, some enterpr

Re: Discussion about java chassis roadmap

[Zen Lin]

I am sorry I can not get the information about which version will  fix
these issues.
Shall we fix all these  epic issues in release 1.0.0, or other later
release.
Or we will break these epic issues into smaller one ,and then mark which
part of the issues will be fixed in release 1.0.0?

Best Regards,
---
Zen Lin
zenlintechnofr...@gmail.com
Focused on Micro Service and Apache ServiceComb


wjm wjm  于2018年7月23日周一 上午8:45写道：

>  adjust roadmap, remove SCB-759, add SCB-770:
>
> [SCB-748 ] ServiceComb
> engine resource optimize
> [SCB-756 ] improve
> development phase flexibility
>
> [SCB-719 ] automated
> integration testing support complex processes
>
> [SCB-757 ] provide common
> governance match mechanism
>
> [SCB-749 ] mybatis for
> reactive mode
> [SCB-758 ] extract core
> engine not depend on springremove
>
> [SCB-770 ] invoke 3rd
> RESTful service
>
> 2018-07-20 11:21 GMT+08:00 bismy :
>
> > Agree with this order. And SCB-748 SCB-756 is related, should take most
> > priority.
> >
> >
> >
> >
> > -- 原始邮件 --
> > 发件人: "wjm wjm";
> > 发送时间: 2018年7月19日(星期四) 下午4:29
> > 收件人: "dev";
> >
> > 主题: Re: Discussion about java chassis roadmap
> >
> >
> >
> > Sort by importance:
> >
> > [SCB-748 ] ServiceComb
> > engine resource optimize
> > [SCB-756 ] improve
> > development phase flexibility
> >
> > [SCB-719 ] automated
> > integration testing support complex processes
> >
> > [SCB-757 ] provide common
> > governance match mechanism
> >
> > [SCB-749 ] mybatis for
> > reactive mode
> > [SCB-758 ] extract core
> > engine not depend on spring
> >
> > 2018-07-19 16:20 GMT+08:00 wjm wjm :
> >
> > > infact all of them are very very big task
> > > once we decided to start them, we must create subtasks.
> > >
> > > now, we just need to decide what tasks will be start?
> > >
> > > 2018-07-19 15:44 GMT+08:00 Willem Jiang :
> > >
> > >> Yeah, as we are heading to ServiceComb 1.0.0. It's the time for us to
> > make
> > >> some plan for the new release.
> > >> Jimin,  I think 719 and 758 are very big task,  I think we may need to
> > >> create some small tasks to break down them a bit.
> > >>
> > >>
> > >> Willem Jiang
> > >>
> > >> Twitter: willemjiang
> > >> Weibo: 姜宁willem
> > >>
> > >> On Thu, Jul 19, 2018 at 10:34 AM, wjm wjm  wrote:
> > >>
> > >> > we need to plan roadmap for the next stage
> > >> > i create below issues to trace what i think is important.
> > >> > please feel free to add your opinions/new isses/ and so on
> > >> >
> > >> > [SCB-719 ] automated
> > >> > integration testing support complex processes
> > >> >
> > >> >
> > >> > [SCB-748 ]
> ServiceComb
> > >> > engine resource optimize
> > >> >
> > >> > [SCB-756 ] improve
> > >> > development phase flexibility
> > >> >
> > >> > [SCB-757 ] provide
> > >> common
> > >> > governance match mechanism
> > >> >
> > >> > [SCB-749 ] mybatis
> for
> > >> > reactive mode
> > >> >
> > >> > [SCB-758 ] extract
> > core
> > >> > engine not depend on spring
> > >> >
> > >>
> > >
> > >
> >
>

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0

[Yang Bo]

-1

Several third-party libraries were added but not included in LICENSE file.

github.com/karlseguin/ccache
github.com/gorilla/websocket
css-percentage-circle
vis


On Sat, Jul 21, 2018 at 10:16 AM bismy  wrote:

> +1
> Check the release notes and run some test to binaries.
>
>
> One small improvement, for API Changes in release notes, can you give
> detail description about the changes?
>
>
>
>
> -- 原始邮件 --
> 发件人: "Mohammad Asif Siddiqui";
> 发送时间: 2018年7月21日(星期六) 凌晨4:29
> 收件人: "dev";
>
> 主题: [VOTE] Release Apache ServiceComb Service-Center (incubating) version
> 1.0.0
>
>
>
> Hi All,
>
> This is a call for a Vote to release Apache ServiceComb Service-Center
> (Incubating) version 1.0.0
>
> Release Notes :
> https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes-1.0.0.md
>
>
> Release Candidate :
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0/rc-01/
>
>
> Release Tag :
> https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0
>
>
> Release CommitID : 7590fec4e4447fdd3b2977970d544e88ae3762cf
>
> Keys to verify the Release Candidate :
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS
>
> Guide to build the release from source :
> https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release
>
>
> Voting will start now ( Saturday, 21st July, 2018) and will remain open
> for next 72 hours, Request all PPMC members to give their vote
>
> [ ] +1 Release this package as 1.0.0
> [ ] +0 No Opinion
> [ ] -1 Do not release this package because
>
> On the behalf of ServiceComb Team
> Mohammad Asif Siddiqui



-- 
Best Regards,
Yang.

Re: [DISCUSS] Proposal for Re-Design of Service-Center Frontend

[Bin Ma]

About the new Service-Center UI, some ideas from the user's point of view,
1. The function of the old UI is stable at 1.0.0-m2, including featrures
and configuration files. The new UI should provide stable and usable
features, and do not displayed test phase featrures in the UI interface to
avoid misleading users, such as SCHEMA Test in 1.0.0-m1.
2. If there is no user appeal in the old UI, it is recommended to maintain
compatibility, including the original usage methods, functions, and
back-end interfaces,it is not excluded that the user may develop the UI by
himself. If there are changes, it is recommended to provide detailed
instructions.
3. I have seen some new features are added in the new UI. It is recommended
that each function provide detailed instructions for users to understand
and use quickly.
4. Need to provide Chinese version UI and manual  : )

Best Wishes & Regards
---
Mabin



Zen Lin  于2018年7月17日周二 下午3:36写道：

> +1
>
> Best Regards,
> ---
> Zen Lin
> zenlintechnofr...@gmail.com
> Focused on Micro Service and Apache ServiceComb
>
>
> Willem Jiang  于2018年7月17日周二 下午3:33写道：
>
> > I cannot agree with you more about it.
> > We need to avoid this kind of situation in our further development.
> > Before we start writing the code, it's quite important that we need to
> send
> > a heads up or proposal to let others know about it.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Jul 17, 2018 at 3:22 PM, wjm wjm  wrote:
> >
> > > ok
> > >
> > > but i think it's better raise proposal before start work on it.
> > >
> > > 2018-07-17 15:04 GMT+08:00 Willem Jiang :
> > >
> > > > It‘s no harm if the development is down.  We just need to get more
> feed
> > > > back from the community and consider to merge the UI to the new UI.
> > > > For the UI, there are some License stuff of java script library we
> need
> > > to
> > > > care about. We may need to address this issue before CSE UI is open
> > > > sourced.
> > > >
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Tue, Jul 17, 2018 at 1:36 PM, Mohammad Asif Siddiqui <
> > > > asifdxtr...@apache.org> wrote:
> > > >
> > > > > Hi Guyz,
> > > > >
> > > > > The development of these design was already done before and that's
> > the
> > > > > reason we were able to show the snapshots of the new UI. The code
> is
> > > > ready
> > > > > to be merged but before merging we decided to come here and discuss
> > > about
> > > > > this UI for people opinion. Since most of the people are concerned
> > > about
> > > > > the effort needed to re-design this UI, so I would like to tell
> that
> > > > > development is already done.
> > > > >
> > > > > So in my opinion we can merge this change to make the UI better and
> > > > > whenever ServiceComb-UI gets opensourced then we can plan to merge
> > some
> > > > of
> > > > > these designs to the ServiceComb-UI.
> > > > >
> > > > > Any thoughts?
> > > > >
> > > > > Regrds
> > > > > Asif
> > > > >
> > > > > On 2018/07/16 10:57:00, Zen Lin 
> wrote:
> > > > > > Hi all,
> > > > > > As we known,  CSE is a initial commercial product of servicecomb
> > and
> > > we
> > > > > > have tried our best to ask CSE to open source ServiceComb-UI to
> > > > stronger
> > > > > > servicecomb and let servicecomb service users better.
> > > > > > But I think the discuss should focused on what's  difference
> > between
> > > > > > servicecenter UI positioning and servicecomb UI positioning.
> > > > > >
> > > > > > If we sure the functionality of servicecenter UI is a subset of
> of
> > > > > > servicecomb UI which will be opensourceed future, and Asif have
> > > willing
> > > > > to
> > > > > > keep on developing and maintaining a servicenter UI, will will
> have
> > > two
> > > > > UI
> > > > > > in future, I think that is allowed with a opensource project
> also.
> > > > > >
> > > > > > Therefore, to my opinion, I think we can focused on discussing
> > > > > > servicecenter-UI's position, something like, what functionality
> for
> > > > > > service-center UI is reasonable?
> > > > > >
> > > > > >
> > > > > > Best Regards,
> > > > > > ---
> > > > > > Zen Lin
> > > > > > zenlintechnofr...@gmail.com
> > > > > > Focused on Micro Service and Apache ServiceComb
> > > > > >
> > > > > >
> > > > > > wjm wjm  于2018年7月16日周一 下午12:43写道：
> > > > > >
> > > > > > > maybe we can change our mind to: make sure new feathers all in
> > > > > > > ServiceComb-UI, not design a new one.
> > > > > > >
> > > > > > > 2018-07-16 12:41 GMT+08:00 wjm wjm :
> > > > > > >
> > > > > > > > as i said that, Proposal of new SC frontend seems to be a
> > subset
> > > of
> > > > > > > > ServiceComb-UI
> > > > > > > > if that's true, i think we no need to spend time to do one
> > thing
> > > > > with two
> > > > > > > > way.
> > > > > > > >
> > > > > > > > 2018-07-16 11:58 GMT+08:00 Mohammad Asif Siddiqui <
> > > > > > > asifdxtr...@apache.org>
> > > > > > > > :
>

Re: Discussion about java chassis roadmap

[wjm wjm]

currently, just discuss what will be done in next stage

when will the issues will be implemented discussed after "what" is clear?

2018-07-23 9:35 GMT+08:00 Zen Lin :

> I am sorry I can not get the information about which version will  fix
> these issues.
> Shall we fix all these  epic issues in release 1.0.0, or other later
> release.
> Or we will break these epic issues into smaller one ,and then mark which
> part of the issues will be fixed in release 1.0.0?
>
> Best Regards,
> ---
> Zen Lin
> zenlintechnofr...@gmail.com
> Focused on Micro Service and Apache ServiceComb
>
>
> wjm wjm  于2018年7月23日周一 上午8:45写道：
>
> >  adjust roadmap, remove SCB-759, add SCB-770:
> >
> > [SCB-748 ] ServiceComb
> > engine resource optimize
> > [SCB-756 ] improve
> > development phase flexibility
> >
> > [SCB-719 ] automated
> > integration testing support complex processes
> >
> > [SCB-757 ] provide common
> > governance match mechanism
> >
> > [SCB-749 ] mybatis for
> > reactive mode
> > [SCB-758 ] extract core
> > engine not depend on springremove
> >
> > [SCB-770 ] invoke 3rd
> > RESTful service
> >
> > 2018-07-20 11:21 GMT+08:00 bismy :
> >
> > > Agree with this order. And SCB-748 SCB-756 is related, should take most
> > > priority.
> > >
> > >
> > >
> > >
> > > -- 原始邮件 --
> > > 发件人: "wjm wjm";
> > > 发送时间: 2018年7月19日(星期四) 下午4:29
> > > 收件人: "dev";
> > >
> > > 主题: Re: Discussion about java chassis roadmap
> > >
> > >
> > >
> > > Sort by importance:
> > >
> > > [SCB-748 ] ServiceComb
> > > engine resource optimize
> > > [SCB-756 ] improve
> > > development phase flexibility
> > >
> > > [SCB-719 ] automated
> > > integration testing support complex processes
> > >
> > > [SCB-757 ] provide
> common
> > > governance match mechanism
> > >
> > > [SCB-749 ] mybatis for
> > > reactive mode
> > > [SCB-758 ] extract core
> > > engine not depend on spring
> > >
> > > 2018-07-19 16:20 GMT+08:00 wjm wjm :
> > >
> > > > infact all of them are very very big task
> > > > once we decided to start them, we must create subtasks.
> > > >
> > > > now, we just need to decide what tasks will be start?
> > > >
> > > > 2018-07-19 15:44 GMT+08:00 Willem Jiang :
> > > >
> > > >> Yeah, as we are heading to ServiceComb 1.0.0. It's the time for us
> to
> > > make
> > > >> some plan for the new release.
> > > >> Jimin,  I think 719 and 758 are very big task,  I think we may need
> to
> > > >> create some small tasks to break down them a bit.
> > > >>
> > > >>
> > > >> Willem Jiang
> > > >>
> > > >> Twitter: willemjiang
> > > >> Weibo: 姜宁willem
> > > >>
> > > >> On Thu, Jul 19, 2018 at 10:34 AM, wjm wjm  wrote:
> > > >>
> > > >> > we need to plan roadmap for the next stage
> > > >> > i create below issues to trace what i think is important.
> > > >> > please feel free to add your opinions/new isses/ and so on
> > > >> >
> > > >> > [SCB-719 ]
> automated
> > > >> > integration testing support complex processes
> > > >> >
> > > >> >
> > > >> > [SCB-748 ]
> > ServiceComb
> > > >> > engine resource optimize
> > > >> >
> > > >> > [SCB-756 ] improve
> > > >> > development phase flexibility
> > > >> >
> > > >> > [SCB-757 ] provide
> > > >> common
> > > >> > governance match mechanism
> > > >> >
> > > >> > [SCB-749 ] mybatis
> > for
> > > >> > reactive mode
> > > >> >
> > > >> > [SCB-758 ] extract
> > > core
> > > >> > engine not depend on spring
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Proposal for Re-Design of Service-Center Frontend

[Willem Jiang]

There is a vote of Service-Center 1.0.0,  please spend some time play with
it.
Now we just need to make sure the UI is work as we expected.



Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Jul 23, 2018 at 11:35 AM, Bin Ma  wrote:

> About the new Service-Center UI, some ideas from the user's point of view,
> 1. The function of the old UI is stable at 1.0.0-m2, including featrures
> and configuration files. The new UI should provide stable and usable
> features, and do not displayed test phase featrures in the UI interface to
> avoid misleading users, such as SCHEMA Test in 1.0.0-m1.
> 2. If there is no user appeal in the old UI, it is recommended to maintain
> compatibility, including the original usage methods, functions, and
> back-end interfaces,it is not excluded that the user may develop the UI by
> himself. If there are changes, it is recommended to provide detailed
> instructions.
> 3. I have seen some new features are added in the new UI. It is recommended
> that each function provide detailed instructions for users to understand
> and use quickly.
> 4. Need to provide Chinese version UI and manual  : )
>
> Best Wishes & Regards
> ---
> Mabin
>
>
>
> Zen Lin  于2018年7月17日周二 下午3:36写道：
>
> > +1
> >
> > Best Regards,
> > ---
> > Zen Lin
> > zenlintechnofr...@gmail.com
> > Focused on Micro Service and Apache ServiceComb
> >
> >
> > Willem Jiang  于2018年7月17日周二 下午3:33写道：
> >
> > > I cannot agree with you more about it.
> > > We need to avoid this kind of situation in our further development.
> > > Before we start writing the code, it's quite important that we need to
> > send
> > > a heads up or proposal to let others know about it.
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Tue, Jul 17, 2018 at 3:22 PM, wjm wjm  wrote:
> > >
> > > > ok
> > > >
> > > > but i think it's better raise proposal before start work on it.
> > > >
> > > > 2018-07-17 15:04 GMT+08:00 Willem Jiang :
> > > >
> > > > > It‘s no harm if the development is down.  We just need to get more
> > feed
> > > > > back from the community and consider to merge the UI to the new UI.
> > > > > For the UI, there are some License stuff of java script library we
> > need
> > > > to
> > > > > care about. We may need to address this issue before CSE UI is open
> > > > > sourced.
> > > > >
> > > > >
> > > > > Willem Jiang
> > > > >
> > > > > Twitter: willemjiang
> > > > > Weibo: 姜宁willem
> > > > >
> > > > > On Tue, Jul 17, 2018 at 1:36 PM, Mohammad Asif Siddiqui <
> > > > > asifdxtr...@apache.org> wrote:
> > > > >
> > > > > > Hi Guyz,
> > > > > >
> > > > > > The development of these design was already done before and
> that's
> > > the
> > > > > > reason we were able to show the snapshots of the new UI. The code
> > is
> > > > > ready
> > > > > > to be merged but before merging we decided to come here and
> discuss
> > > > about
> > > > > > this UI for people opinion. Since most of the people are
> concerned
> > > > about
> > > > > > the effort needed to re-design this UI, so I would like to tell
> > that
> > > > > > development is already done.
> > > > > >
> > > > > > So in my opinion we can merge this change to make the UI better
> and
> > > > > > whenever ServiceComb-UI gets opensourced then we can plan to
> merge
> > > some
> > > > > of
> > > > > > these designs to the ServiceComb-UI.
> > > > > >
> > > > > > Any thoughts?
> > > > > >
> > > > > > Regrds
> > > > > > Asif
> > > > > >
> > > > > > On 2018/07/16 10:57:00, Zen Lin 
> > wrote:
> > > > > > > Hi all,
> > > > > > > As we known,  CSE is a initial commercial product of
> servicecomb
> > > and
> > > > we
> > > > > > > have tried our best to ask CSE to open source ServiceComb-UI to
> > > > > stronger
> > > > > > > servicecomb and let servicecomb service users better.
> > > > > > > But I think the discuss should focused on what's  difference
> > > between
> > > > > > > servicecenter UI positioning and servicecomb UI positioning.
> > > > > > >
> > > > > > > If we sure the functionality of servicecenter UI is a subset of
> > of
> > > > > > > servicecomb UI which will be opensourceed future, and Asif have
> > > > willing
> > > > > > to
> > > > > > > keep on developing and maintaining a servicenter UI, will will
> > have
> > > > two
> > > > > > UI
> > > > > > > in future, I think that is allowed with a opensource project
> > also.
> > > > > > >
> > > > > > > Therefore, to my opinion, I think we can focused on discussing
> > > > > > > servicecenter-UI's position, something like, what functionality
> > for
> > > > > > > service-center UI is reasonable?
> > > > > > >
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > ---
> > > > > > > Zen Lin
> > > > > > > zenlintechnofr...@gmail.com
> > > > > > > Focused on Micro Service and Apache ServiceComb
> > > > > > >
> > > > > > >
> > > > > > > wjm wjm  于2018年7月16日周一 下午12:43写道：
> > > > > > >
> > > > > > > > maybe we can change our mind to: make sure new feathers

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0

[Jean-Baptiste Onofré]

I guess you mean NOTICE file, right ?

Regards
JB

Le 23 juil. 2018 à 03:53, à 03:53, Yang Bo  a écrit:
>-1
>
>Several third-party libraries were added but not included in LICENSE
>file.
>
>github.com/karlseguin/ccache
>github.com/gorilla/websocket
>css-percentage-circle
>vis
>
>
>On Sat, Jul 21, 2018 at 10:16 AM bismy  wrote:
>
>> +1
>> Check the release notes and run some test to binaries.
>>
>>
>> One small improvement, for API Changes in release notes, can you give
>> detail description about the changes?
>>
>>
>>
>>
>> -- 原始邮件 --
>> 发件人: "Mohammad Asif Siddiqui";
>> 发送时间: 2018年7月21日(星期六) 凌晨4:29
>> 收件人: "dev";
>>
>> 主题: [VOTE] Release Apache ServiceComb Service-Center (incubating)
>version
>> 1.0.0
>>
>>
>>
>> Hi All,
>>
>> This is a call for a Vote to release Apache ServiceComb
>Service-Center
>> (Incubating) version 1.0.0
>>
>> Release Notes :
>>
>https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes-1.0.0.md
>>
>>
>> Release Candidate :
>>
>https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0/rc-01/
>>
>>
>> Release Tag :
>>
>https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0
>>
>>
>> Release CommitID : 7590fec4e4447fdd3b2977970d544e88ae3762cf
>>
>> Keys to verify the Release Candidate :
>> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS
>>
>> Guide to build the release from source :
>>
>https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release
>>
>>
>> Voting will start now ( Saturday, 21st July, 2018) and will remain
>open
>> for next 72 hours, Request all PPMC members to give their vote
>>
>> [ ] +1 Release this package as 1.0.0
>> [ ] +0 No Opinion
>> [ ] -1 Do not release this package because
>>
>> On the behalf of ServiceComb Team
>> Mohammad Asif Siddiqui
>
>
>
>--
>Best Regards,
>Yang.

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0

[Bin Ma]

I did some tests with 1.0.0 version, base functions is OK and the features
are forward compatible, but the link of user guide in Service Center
Dashboard seems be wrong.

Best Wishes & Regards
---
Mabin



Jean-Baptiste Onofré  于2018年7月23日周一 下午1:17写道：

> I guess you mean NOTICE file, right ?
>
> Regards
> JB
>
> Le 23 juil. 2018 à 03:53, à 03:53, Yang Bo  a écrit:
> >-1
> >
> >Several third-party libraries were added but not included in LICENSE
> >file.
> >
> >github.com/karlseguin/ccache
> >github.com/gorilla/websocket
> >css-percentage-circle
> >vis
> >
> >
> >On Sat, Jul 21, 2018 at 10:16 AM bismy  wrote:
> >
> >> +1
> >> Check the release notes and run some test to binaries.
> >>
> >>
> >> One small improvement, for API Changes in release notes, can you give
> >> detail description about the changes?
> >>
> >>
> >>
> >>
> >> -- 原始邮件 --
> >> 发件人: "Mohammad Asif Siddiqui";
> >> 发送时间: 2018年7月21日(星期六) 凌晨4:29
> >> 收件人: "dev";
> >>
> >> 主题: [VOTE] Release Apache ServiceComb Service-Center (incubating)
> >version
> >> 1.0.0
> >>
> >>
> >>
> >> Hi All,
> >>
> >> This is a call for a Vote to release Apache ServiceComb
> >Service-Center
> >> (Incubating) version 1.0.0
> >>
> >> Release Notes :
> >>
> >
> https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes-1.0.0.md
> >>
> >>
> >> Release Candidate :
> >>
> >
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0/rc-01/
> >>
> >>
> >> Release Tag :
> >>
> >
> https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0
> >>
> >>
> >> Release CommitID : 7590fec4e4447fdd3b2977970d544e88ae3762cf
> >>
> >> Keys to verify the Release Candidate :
> >> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS
> >>
> >> Guide to build the release from source :
> >>
> >
> https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release
> >>
> >>
> >> Voting will start now ( Saturday, 21st July, 2018) and will remain
> >open
> >> for next 72 hours, Request all PPMC members to give their vote
> >>
> >> [ ] +1 Release this package as 1.0.0
> >> [ ] +0 No Opinion
> >> [ ] -1 Do not release this package because
> >>
> >> On the behalf of ServiceComb Team
> >> Mohammad Asif Siddiqui
> >
> >
> >
> >--
> >Best Regards,
> >Yang.
>