we can start release process between 11.19~11.23 for java chassis Bin Ma <mabin1...@gmail.com> 于2018年11月4日周日 上午12:13写道：
> OK,I will try to check the ServiceComb website first > > > Best Wishes & Regards > ------------------------------- > Mabin > > > > Willem Jiang <willem.ji...@gmail.com> 于2018年11月2日周五 上午8:30写道： > > > I already submit a JIRA and wait for infra's response. > > But the document it's OK for us do the modification, please send a PR > > if you have time to work on it. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Nov 1, 2018 at 8:24 PM Bin Ma <mabin1...@gmail.com> wrote: > > > > > > Hi all, > > > > > > Some community users plan to make courses based on ServiceComb in the > > near > > > future, like Itcast,University and so on. > > > So I think it may be speed up the process of renaming the git repo name > > and > > > updating the documentation. > > > > > > > > > Best Wishes & Regards > > > ------------------------------- > > > Mabin > > > > > > > > > > > > Willem Jiang <willem.ji...@gmail.com> 于2018年10月29日周一 下午12:54写道： > > > > > > > FYI， I fill a JIRA[1] for renaming the git repo. > > > > > > > > [1]https://issues.apache.org/jira/browse/INFRA-17185 > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > On Sat, Oct 27, 2018 at 10:09 PM Willem Jiang < > willem.ji...@gmail.com> > > > > wrote: > > > > > > > > > > Oh, I just forgot the github name issue which we faced when moving > > > > > the servicecomb to apache incubator. > > > > > I will fill a JIRA this weekend, it may take few days to do the > > > > > transfer. Once we changed the github name, we could consider the > > > > > release of ServiceCenter. > > > > > > > > > > Willem Jiang > > > > > > > > > > Twitter: willemjiang > > > > > Weibo: 姜宁willem > > > > > > > > > > On Sat, Oct 27, 2018 at 2:25 PM Mohammad Asif Siddiqui > > > > > <asifdxtr...@apache.org> wrote: > > > > > > > > > > > > Hi Willem, > > > > > > > > > > > > In my opinion since ServiceComb has already graduated so we can > > change > > > > the repository names first and migrate the SVN for the releases and > > then > > > > plan for the ServiceComb 1.1.0 release. In Service-Center after the > > change > > > > in the repository name we need to change the import statements of > each > > file > > > > and also we need to update the Travis settings for each project and > > make > > > > new encryption keys for automatic snapshot deployment, for all these > > > > activities it might take 2-3 days so we can plan this first in coming > > week > > > > and then we can go ahead with the Service-Center 1.1.0 release. > > > > > > > > > > > > Just my 2 cents.. > > > > > > > > > > > > Regards > > > > > > Asif > > > > > > > > > > > > On 2018/10/22 03:39:02, Willem Jiang <willem.ji...@gmail.com> > > wrote: > > > > > > > Hi, > > > > > > > > > > > > > > The last ServiceComb java-chassis，service-center 1.0.0 release > is > > > > > > > three month ago. It's time to discuss the release of > ServiceComb > > > > > > > 1.1.0. > > > > > > > > > > > > > > As we add the TCC implementation in the Saga 0.3.0, we may need > > to > > > > > > > create a separate git repo to support the Saga and TCC at the > > same > > > > > > > time. It may take sometime to do these change. We may do the > > Saga > > > > > > > release after the release of java-chassis and service-center. > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > > > Twitter: willemjiang > > > > > > > Weibo: 姜宁willem > > > > > > > > > > > > > >
