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 > > > >
