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 <ken.lj...@gmail.com> 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 <ken.lj...@gmail.com> 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 <mailto: > 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 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 < > https://github.com/apache/incubator-dubbo/issues/2919> > >> 2. > https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT > < > https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT > > > >> > >> Jun > >> > > > >
