Hi

Also as we have similar projects at ASF such as ActiveMQ, Karaf, CXF,
ServiceMix etc I wonder if there can be some base docker images we can
extend from or even use the same?

Also we could have a pre-setup vagrant image as well, as those are
also easy to use.

And if the docker image / vagrant etc is reused in more projects then
I would hope that the documentation how to use it  / what you may need
to do personally to setup pgp / m2 settings is detailed in an easy to
follow step by step guide, so a lot more people can get started doing
releases.

We have been too dependent on a small group of people to cut releases.
I really would like to see this done more frequently and more
automated. Its 2015 and not 2008 anymore. People are releasing more
often today ;)




On Sat, Jul 18, 2015 at 4:37 PM, Willem Jiang <willem.ji...@gmail.com> wrote:
> There are some private setting of maven setting.xml and pgp private key for 
> 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 the 
> protection of GFW) is more convince for me to do the release.
>
> --
> Willem Jiang
>
>
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On July 18, 2015 at 6:05:16 PM, Claus Ibsen (claus.ib...@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, 
>> > especially to get an
>> aseptic environment.
>> > We can do some tests and maybe open a new repository to push Dockerfile 
>> > and all the related
>> code. What do you think about?
>> >
>> > --
>> > Andrea Cosentino
>> > ----------------------------------
>> > Apache Camel Committer
>> > Email: ancosen1...@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 great
>> >> 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: cib...@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
>>
>



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

Reply via email to