Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CALhQg-YDTRSb2WMEEMjj39RtCf-Kat6xMEYjec68A72zLHttmg@mail.gmail.com>
References: 
 <CAGB5yNkaZn4tM=g53_f+xWbYMJ6f-QNtGppPw7CacOauuNtEPQ@mail.gmail.com>
	<555A00BA.5030901@nanthrax.net>
	<CALhQg-ZAF=erUr=7iWwT0xEFHHMRi1N773WSgVsfaOE7Sdb6dg@mail.gmail.com>
	<CALvzYd_uK4SK310rrUQKmfqL9a+t+SuSDxSZUHS+xN4VWFy5uA@mail.gmail.com>
	<CALhQg-YDTRSb2WMEEMjj39RtCf-Kat6xMEYjec68A72zLHttmg@mail.gmail.com>
Date: Tue, 19 May 2015 23:34:59 +0200
Message-ID: 
 <CALvzYd90ahPTNv0HNUC=OrX456fs6=J7y7T=gN6iY89duRwnRA@mail.gmail.com>
Subject: Re: Apache Camel 2.14.3 release
From: =?UTF-8?Q?Christian_M=C3=BCller?= <christian.mueller@gmail.com>
To: "dev@camel.apache.org" <dev@camel.apache.org>
Content-Type: multipart/alternative; boundary=001a114414f01d91b90516761586

--001a114414f01d91b90516761586
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Fine, good luck! ;-)
It would be good, if you could also update [1] with the missing pieces. It
should be easier for the next RM...

[1] http://camel.apache.org/building.html

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 Tue, May 19, 2015 at 10:42 PM, Henryk Konsek <hekonsek@gmail.com> wrote:

> Thanks Christian. I will add my key to 2.14.x branch as well.
>
> I should cut the first release candidate tomorrow.
>
> Cheers.
>
> wt., 19.05.2015 o 21:50 u=C5=BCytkownik Christian M=C3=BCller <
> christian.mueller@gmail.com> napisa=C5=82:
>
> > 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 upda=
te
> > the file first (MASTER, camel-2.15.x, camel-2.14.x).
> >
> > [1]
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=3Dcamel.git;a=3Dblob;f=3DKEYS;h=
=3Dcf65015d2ae4e2c9b29a9b92e60c6047ccefafe8;hb=3Drefs/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 <hekonsek@gmail.com>
> wrote:
> >
> > > > Your public key must also be cross-signed by other Apache committer=
s
> > > > (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 mayb=
e
> > > somebody can sign my key? How does it work?
> > >
> > > pon., 18.05.2015 o 17:10 u=C5=BCytkownik Jean-Baptiste Onofr=C3=A9 <
> > jb@nanthrax.net>
> > > napisa=C5=82:
> > >
> > > > +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 patc=
h
> > > > > release of this branch.
> > > > >
> > > > > Any thoughts?
> > > > >
> > > >
> > > > --
> > > > Jean-Baptiste Onofr=C3=A9
> > > > jbonofre@apache.org
> > > > http://blog.nanthrax.net
> > > > Talend - http://www.talend.com
> > > >
> > >
> >
>

--001a114414f01d91b90516761586--