For the convince binary release, we just need to keep signed signature outside of the tar.gz. So we just need to verify the tar.gz files and don't need to verify all the exec files one by one.
Could you add those files for the tar.gz files? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Jun 10, 2019 at 4:03 PM Nicola Ferraro <[email protected]> wrote: > > Yeah, those are in the tar.gz for the binary files. I've added them now > also for sources and examples. > Don't know which strategy is best. > > Nicola > > On Mon, Jun 10, 2019 at 12:52 AM Willem Jiang <[email protected]> > wrote: > > > Hi Nicola, > > > > I cannot find the signed signature[1] and sha512 files in the staging > > directory. > > Could you add them into the release directory? > > > > [1]http://www.apache.org/legal/release-policy.html#release-signing > > > > Regards, > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Fri, Jun 7, 2019 at 10:09 PM Nicola Ferraro <[email protected]> > > wrote: > > > > > > Hello all: > > > > > > This is a vote to release Apache Camel K 0.3.4, the first official > > release > > > of Apache Camel K. > > > > > > Staging repository: > > > https://dist.apache.org/repos/dist/dev/camel/camel-k/0.3.4/ > > > > > > Tag: > > > > > https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/0.3.4 > > > > > > Staging container image repository: > > > https://hub.docker.com/r/camelk/camel-k/tags > > > > > > Command to install staging artifacts: > > > kamel install --operator-image=camelk/camel-k:0.3.4 > > > > > > Please test this release candidate and cast your vote. > > > > > > [ ] +1 Release the binary as Apache Camel-K 0.3.4 > > > [ ] -1 Veto the release (provide specific comments) > > > > > > The vote is open for at least 72 hours. > > > > > > Thanks, > > > Nicola Ferraro > >
