+1 for separate thread.
Inviato da Yahoo Mail su Android
Da:"Andrew Block"
Data:lun, 20 lug, 2015 alle 18:59
Oggetto:Re: Apache Camel 2.15.3 release
Mark. +1 lets create a separate thread to get everyone who is interested
involved and to determine the work that will be necessar
Mark. +1 lets create a separate thread to get everyone who is interested
involved and to determine the work that will be necessary. We will certainly
need input from those who have done the release on the steps involved and any
of the requirements
- Andy
--
Andrew Block
On July 20, 2015 at 1
If you need help, I'm here.
I'm interested in using Docker images to make releases. Thank you.
--
Andrea Cosentino
--
Apache Camel Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Monday, July 20, 2015 5:31 PM, Mark Webb wro
Great to hear Claus. It would be an honor to work on a project that I've
been using for years. I have some ideas on setting up docker images for
different Java versions as well as different systems/versions that Camel
can integrate with.
We should start a separate thread to discuss our approach
Hi Mark
Thanks a lot for helping out.
You are very much welcome to help here. And hopefully this could
potential help other Apache projects as well to release more often.
Also CI/CD software is going to be able to do build pipelines using
docker images, so you are more flexible and can use an im
I'd be very interested in this. While I'm not a committer on Apache Camel,
I am on the PMC for Apache MINA so I have all the right Apache credentials
to jump in and help.
Let me know if you'd be interested in having me take the lead on this.
Thanks,
Mark
On Sun, Jul 19, 2015 at 3:02 PM, Chris
Anyone who wants to take the lead here?
Best,
Christian
Am 19.07.2015 10:03 schrieb "Claus Ibsen" :
> 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
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
On Sat, Jul 18, 2015 at 4:37 PM, Willem Jiang 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
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) i
Hi,
wouldn't a vagrant box be much better environment for this? Cause in the
end you would want an interactive shell and not a single "process" to call.
Just my 2 cents.
Regards, Achim
sent from mobile device
Am 18.07.2015 12:05 nachm. schrieb "Claus Ibsen" :
> Hi
>
> Yeah a docker image makes
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, es
>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
--
Apac
On Thu, Jul 16, 2015 at 4:55 PM, Daniel Kulp wrote:
> Out of curiosity, what would the docker image buy us?
>
> Really “mvn release:prepare; mvn release:perform” is not that hard. I think
> the only complexity would be the gpg setup, but that’s likely really just an
> issue for Windows folks, a
On 16/07/15 16:55, Daniel Kulp wrote:
> Out of curiosity, what would the docker image buy us?
>
> Really “mvn release:prepare; mvn release:perform” is not that hard. I think
> the only complexity would be the gpg setup, but that’s likely really just an
> issue for Windows folks, and I’m not
I think a Docker image to perform releases is a good idea to pilot. It allows
for a repeatable solution that could be used to be easily spun up/down to
create the releases with all of the necessary tooling already in place (which
has been a challenge from what I can ascertain in the past). Depen
Out of curiosity, what would the docker image buy us?
Really “mvn release:prepare; mvn release:perform” is not that hard. I think
the only complexity would be the gpg setup, but that’s likely really just an
issue for Windows folks, and I’m not sure how that would work with a docker
image eit
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 commi
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://davscla
19 matches
Mail list logo
