Hi, We got a tricky problem when preparing for v2.6.3 release RC4, and we need more inputs for what to do next. The problem is: While we are preparing for the RC4 Apache release vote, we found that the binary maven release has been deployed to the central repository at http://central.maven.org/maven2/com/alibaba/dubbo/2.6.3/ <http://central.maven.org/maven2/com/alibaba/dubbo/2.6.3/>. However, we expect the maven binary only to be released after the Apache vote, we are still looking for the reasons why this happened. I’ve checked that the signature of the binary maven release is correct and the code in jar are exactly the same with the RC4, which means it can work properly.
In this case, can we continue with the v2.6.3 Apache vote? Best regards, Jun
