For the go artifacts(source and binary) we can put them into [1]. Current ServiceComb service-center is using [2] as the staging repo. I found camel-k already use publish the dock image here[3], but according to [4], we cannot use this repo to distribute SNAPSHOT version.
So I think the missing parts of current camel-k release are 1. We need to stage go artifacts and vote of them. 2. Publish the artifacts if the vote is passed. 3. Updating the Apache Camel website for the downloading of the artifacts. 4. Push the convicen binary docker image which is based on the official release. FYI, there are some discussion[5] in the Zipkin about the release which we take as a reference. [1]https://dist.apache.org/repos/dist/dev/camel/camel-k [2]https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-service-center/ [3]https://hub.docker.com/r/apache/camel-k [4]https://issues.apache.org/jira/browse/INFRA-12659 [5]https://github.com/apache/incubator-zipkin/issues/2597 Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, May 4, 2019 at 3:46 PM Nicola Ferraro <ni.ferr...@gmail.com> wrote: > > Yes, released go binaries are still unofficial dev builds. We should find a > way to complete the release process. > There are many points that we need to cover, including signing and > distributing binaries but also the docker images. Iirc docker hub is not an > officially recognized system for distributing resources. > > But I agree we should standardize the process, otherwise we cannot even do > official announcements and people won't know about them. > > Nicola > > > > Il sab 4 mag 2019, 09:07 Andrea Cosentino <anco...@gmail.com> ha scritto: > > > Ok. Lets synch with others and we can write up a release process for that > > > > Il sab 4 mag 2019, 08:56 Willem Jiang <willem.ji...@gmail.com> ha scritto: > > > > > We could use the https://dist.apache.org/repos/dist/dev as a staging > > > repo to host the artifacts which need to be voted. > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Sat, May 4, 2019 at 2:11 PM Andrea Cosentino <anco...@gmail.com> > > wrote: > > > > > > > > We can add a goal to push the binary generated on dist. But all the > > stuff > > > > generated is just go binaries and docker images. It's not like a normal > > > > Java project. > > > > > > > > Lets wait for Nicola and Luca about this. > > > > > > > > Il sab 4 mag 2019, 03:41 Willem Jiang <willem.ji...@gmail.com> ha > > > scritto: > > > > > > > > > Hi, > > > > > > > > > > I just found there are release in the github of camel-k 0.3.3 > > > > > recently. I can only find the vote of camel-k runtime 0.3.3. From my > > > > > understanding camel-k is dependent on camel-k runtime, but they are > > > > > two different projects. As the official Apache release, we need the > > > > > vote of PMC[1] > > > > > According to the release distribution guild of ASF[2]. > > > > > "The Apache infrastructure must be the primary source for all > > > > > artifacts officially released by the ASF." We need to put the > > > > > artifacts of camel-k into the https://dist.apache.org/repos/dist/. > > > > > > > > > > Please let me know if I missed something. > > > > > > > > > > [1]http://www.apache.org/dev/release-publishing.html#goal > > > > > [2]http://www.apache.org/dev/release-publishing.html#distribution > > > > > > > > > > Willem Jiang > > > > > > > > > > Twitter: willemjiang > > > > > Weibo: 姜宁willem > > > > > > > > > >
