It's not really a MUST, it's a good practice. The user can still check the KEYS [1] file in our repo whether the key which was used to sign the release is your key. Unfortunately, the KEYS file doesn't contain your key. You have to update the file first (MASTER, camel-2.15.x, camel-2.14.x).
[1] https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=KEYS;h=cf65015d2ae4e2c9b29a9b92e60c6047ccefafe8;hb=refs/heads/camel-2.14.x Best, Christian ----------------- Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Mon, May 18, 2015 at 9:32 PM, Henryk Konsek <hekon...@gmail.com> wrote: > > Your public key must also be cross-signed by other Apache committers > > (this can be done at key signing parties at ApacheCon for instance) > > I don't recall any signing party at the last ApacheCon :) . > > My key is not signed by other committers. Can I still release? I maybe > somebody can sign my key? How does it work? > > pon., 18.05.2015 o 17:10 użytkownik Jean-Baptiste Onofré <j...@nanthrax.net> > napisał: > > > +1 > > > > Regards > > JB > > > > On 05/11/2015 05:43 PM, Claus Ibsen wrote: > > > Hi > > > > > > I think we should if possible later this month release a new patch > > > release of this branch. > > > > > > Any thoughts? > > > > > > > -- > > Jean-Baptiste Onofré > > jbono...@apache.org > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > >
