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 <[email protected]> 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
