Please note: my initial message was not to question the release process. Merely that Infra was asked to enable provision of artifacts within Maven Central under a groupId that is not "org.apache". At the moment, we cannot / will-not work on making that possible. Infra doesn't involve itself in community (release) processes, so please go about your business :-)
On Wed, May 9, 2018 at 3:34 AM, Huxing Zhang <hux...@apache.org> wrote: > On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz > <bdelacre...@codeconsult.ch> wrote: > > On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hux...@apache.org> wrote: > >> ...The maven artifact is the most significant for most of the Dubbo > >> users, so we want to include a maven artifact in the release.... > > > > Binaries are NOT part of Apache Releases, as mentioned earlier in this > thread. > > Yes, we fully understood that. > > Here what I mean "release" does not mean an Apache release, it is > actually a "hybrid" release, which includes: > > * source (following Apache release policy) > * binary (it is optional but still following Apache release policy) > * Maven artifacts under third-party coordinates (Non Apache release) > > > > > Dubbo mentors, I think we need a clear description of how these > > "hybrid" releases are done, to avoid any misunderstandings. > > > > Justin mentioned in this thread that that's been discussed on your dev > > list, so you probably just need to summarize that and include the URL > > in your next Incubator report. > > > > -Bertrand > > -- > Best Regards！ > Huxing > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
