>> Taking one at random [1] I see: >> >> 2.6.1 2018-03-15 >> 2.6.2 2018-06-05 >> 2.6.3 2018-08-05 >> 2.6.4 2018-10-08 >> 2.6.5 2018-11-13 >> >> 2.6.2 was released 2018-06-07, 2.6.3 was 2018-09-11, 2.6.4 was 2018-10-08 >> and 2.6.5 was 2018-11-23. Why do the dates above in most cases pre-date the >> actual release date? Now I could be mistaken I but I would expect [1] to >> show publish dates and those should occur after the release has been voted >> on. > > Regarding 2.6.2, the release vote has been completed on 2018-06-05 > 06:21:24 GMT according to [1], and the maven repo has been updated > 2018-06-05 09:53 (supposing the same timezone here). The release > notification has been sent at 2018-06-07[2] (GMT +8), and the official > website has been updated at the same date. > > Regarding 2.6.3, it is due to some tricky issues described here[3]. > > Regarding 2.6.5, I am not quite sure but I suspect the same reason as 2.6.3.
For the reason that 2.6.5 was released to central repo before vote passed, I doubt the same thing happened to 2.6.3 happened again. Sadly, there’re no logs to inspect the reason, Since it’s less likely to be a problem from the official sonatype team, I tend to believe that it's someone from other projects that has mistakenly released the Dubbo package manually or using an automated script. This keeps happening, against the Apache release rule, so we should definitely keep an eye on it, I would suggest the following two steps for the next release: 1. Does not push staging jar into the maven central repo before vote passed. 2. Ask the sonatype team for the possibility of applying a new account for 'com.alibaba:dubbo’. One thing I am worrying is if it’s allowed to have more than one account for the same groupId. Jun > On Dec 19, 2018, at 10:03 AM, Huxing Zhang <[email protected]> wrote: > > Hi, > > On Wed, Dec 19, 2018 at 4:56 AM Justin Mclean <[email protected] > <mailto:[email protected]>> wrote: >> >> Hi, >> >>> First, all the artifacts, except dubbo-registry-nacos, are only >>> updated when there is an official release. I didn't see any unexpected >>> behavior there. >> >> Taking one at random [1] I see: >> >> 2.6.1 2018-03-15 >> 2.6.2 2018-06-05 >> 2.6.3 2018-08-05 >> 2.6.4 2018-10-08 >> 2.6.5 2018-11-13 >> >> 2.6.2 was released 2018-06-07, 2.6.3 was 2018-09-11, 2.6.4 was 2018-10-08 >> and 2.6.5 was 2018-11-23. Why do the dates above in most cases pre-date the >> actual release date? Now I could be mistaken I but I would expect [1] to >> show publish dates and those should occur after the release has been voted >> on. > > Regarding 2.6.2, the release vote has been completed on 2018-06-05 > 06:21:24 GMT according to [1], and the maven repo has been updated > 2018-06-05 09:53 (supposing the same timezone here). The release > notification has been sent at 2018-06-07[2] (GMT +8), and the official > website has been updated at the same date. > > Regarding 2.6.3, it is due to some tricky issues described here[3]. > > Regarding 2.6.5, I am not quite sure but I suspect the same reason as 2.6.3. > > This is an issue that we should address before the next release. > > > [1] > http://mail-archives.apache.org/mod_mbox/incubator-general/201806.mbox/%[email protected]%3E > > <http://mail-archives.apache.org/mod_mbox/incubator-general/201806.mbox/%[email protected]%3E> > [2] https://www.mail-archive.com/[email protected]/msg63836.html > <https://www.mail-archive.com/[email protected]/msg63836.html> > [3] > https://lists.apache.org/thread.html/3ee79fbad9b9038665d8d5e00ebf393eca0287ccaf9760c70f8374ed@%3Cdev.dubbo.apache.org%3E > > <https://lists.apache.org/thread.html/3ee79fbad9b9038665d8d5e00ebf393eca0287ccaf9760c70f8374ed@%3Cdev.dubbo.apache.org%3E> > >> >> Also why are these still being released under com.alibaba and not >> org.apache.dubbo? Or is that to come in the 3.x branch? > > Yes. 2.6.5 is a maintenance branch. 2.7.x branch will be released > under org.apache.dubbo. > > >> >>> When you say something doesn't seem right, are you saying about >>> dubbo-registry-nacos? If the community agrees to transfer it to ASF, would >>> that solve this issue? >> >> That’s would fix that issue yes. >> >> Thanks, >> Justin >> >> 1. http://central.maven.org/maven2/com/alibaba/dubbo-filter/ >> <http://central.maven.org/maven2/com/alibaba/dubbo-filter/> >> 2. https://github.com/apache/incubator-dubbo/tree/2.6.x/dubbo-filter >> <https://github.com/apache/incubator-dubbo/tree/2.6.x/dubbo-filter> > > > > -- > Best Regards！ > > > Huxing
