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: <etPan.55aa6498.643c9869.222@JiangNingMacBookPro>
References: 
 <CAGB5yNkhiKOe2H2Y+viZwrrFZs39gikL2QMne9D8=RptApscyA@mail.gmail.com>
 <1095045157.110859.1437211565433.JavaMail.yahoo@mail.yahoo.com>
 <CAGB5yNnCvxMcAYC8OFc=rcXkUYs3ypq+EBOFQH5Wn-SMAW39zA@mail.gmail.com>
 <etPan.55aa6498.643c9869.222@JiangNingMacBookPro>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Sun, 19 Jul 2015 09:58:35 +0200
Message-ID: 
 <CAGB5yNkwgqitpFUErcRuJWbb=m9cuaW_XC7LCgjpZhGs6JV44A@mail.gmail.com>
Subject: Re: Apache Camel 2.15.3 release
To: dev <dev@camel.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Jul 18, 2015 at 4:37 PM, Willem Jiang <willem.jiang@gmail.com> wrot=
e:
> There are some private setting of maven setting.xml and pgp private key f=
or the releasing.
>
> If we can keep them out side of docker image, it should be OK to push the=
 docker image into a public place.
>
> But for my experience, having a building box outside of China (without th=
e protection of GFW) is more convince for me to do the release.
>

Yeah I really think ASF should have an infrastructure that does the
build and releases of the ASF projects - not peoples personal laptops.

For example it could do pre-build RC release each week and if one of
those seems good fit for a release it could be a simple way of
promoting that to the staging repos and then have our voting period
etc. This could really help speed up the number of patch releases, eg
if it was dead-easy to do a 2.14.x release etc. Instead of Willem or
someone have to take out many many hours to do the release manually.

Of course doing a RC should also be possible on-demand. So lets say we
wanted a 2.5.3 release today, we can trigger this to the job queue and
next morning or maybe a bit earlier the RC is in the staging repos.


> --
> Willem Jiang
>
>
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: =E5=A7=9C=E5=AE=81willem
>
>
>
> On July 18, 2015 at 6:05:16 PM, Claus Ibsen (claus.ibsen@gmail.com) wrote=
:
>> Hi
>>
>> Yeah a docker image makes sense - it can be setup to include the
>> needed tools such as java / maven / pgp / bash / and other scripts and
>> whatelse may be needed.
>>
>>
>>
>>
>>
>> On Sat, Jul 18, 2015 at 11:26 AM, Andrea Cosentino
>> wrote:
>> > From point of view a release base Docker image can be very useful, esp=
ecially to get an
>> aseptic environment.
>> > We can do some tests and maybe open a new repository to push Dockerfil=
e and all the related
>> code. What do you think about?
>> >
>> > --
>> > Andrea Cosentino
>> > ----------------------------------
>> > Apache Camel Committer
>> > Email: ancosen1985@yahoo.com
>> > Twitter: @oscerd2
>> > Github: oscerd
>> >
>> >
>> > On Thursday, July 16, 2015 11:12 AM, Claus Ibsen wrote:
>> >
>> >
>> > Hi
>> >
>> > A while back Henryk talked about building some kind of docker image we
>> > could use for doing releases. I like that idea so its pre-setup and
>> > would be easier for other people to do releases.
>> >
>> > I have been contacted by a person on email who wanted to help with
>> > releases. However has he is not a committer on Camel - I realized that
>> > this is not possible.
>> >
>> > A bit shame as other more modern projects have a much easier way of
>> > doing releases - with even a CI server setup that makes this possible
>> > with a few clicks. And the benefit is that the release is build from a
>> > trusted source and not on different peoples computers. We are not
>> > there at ASF so have to settle for the old school we got. But a docker
>> > image would be a step forward.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Jul 14, 2015 at 5:32 PM, Claus Ibsen wrote:
>> >> Hi
>> >>
>> >> We are getting towards 2 months since last release and we have a grea=
t
>> >> bunch of fixes. Wonder if there is anyone who are bored in the summer
>> >> vacation and wanna help cut a release?
>> >>
>> >>
>> >>
>> >> --
>> >> Claus Ibsen
>> >> -----------------
>> >> Red Hat, Inc.
>> >> Email: cibsen@redhat.com
>> >> Twitter: davsclaus
>> >> Blog: http://davsclaus.com
>> >> Author of Camel in Action: http://www.manning.com/ibsen
>> >> hawtio: http://hawt.io/
>> >> fabric8: http://fabric8.io/
>> >
>> >
>> >
>> > --
>> > Claus Ibsen
>> > -----------------
>> > http://davsclaus.com @davsclaus
>> > Camel in Action 2nd edition: http://www.manning.com/ibsen2
>> >
>> >
>> >
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2nd edition: http://www.manning.com/ibsen2
>>
>


--=20
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2nd edition: http://www.manning.com/ibsen2