+1 (non-binding)
Thanks!
regards,
François Papon
fpa...@apache.org
Le 08/04/2019 à 09:34, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.22.4, the fourth patch
> release for the camel-2.22.x branch with 26 improvements and bug
> fixes.
>
> Release notes:
+1 (binding)
Thanks Gregor
Il lun 8 apr 2019, 22:25 Alex Dettinger ha scritto:
> +1 (binding)
>
> Thanks Gregor,
> Alex
>
> On Mon, Apr 8, 2019 at 8:48 AM Claus Ibsen wrote:
>
> > +1 (binding)
> >
> > On Mon, Apr 8, 2019 at 7:34 AM Gregor Zurowski >
> > wrote:
> > >
> > > Hi Everyone:
> > >
+1 (binding)
Well done,
Alex
On Mon, Apr 8, 2019 at 5:56 PM Andrea Cosentino wrote:
> +1 (binding)
>
> Thanks
>
> Il lun 8 apr 2019, 17:47 Nicola Ferraro ha scritto:
>
> > +1 (binding)
> >
> > Thanks,
> > Nicola
> >
> > On Mon, Apr 8, 2019 at 8:42 AM Willem Jiang
> > wrote:
> >
> > > +1
+1 (binding)
Thanks Gregor,
Alex
On Mon, Apr 8, 2019 at 8:48 AM Claus Ibsen wrote:
> +1 (binding)
>
> On Mon, Apr 8, 2019 at 7:34 AM Gregor Zurowski
> wrote:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 2.22.4, the fourth patch
> > release for the camel-2.22.x branch
+1 (binding)
Thanks
Il lun 8 apr 2019, 17:47 Nicola Ferraro ha scritto:
> +1 (binding)
>
> Thanks,
> Nicola
>
> On Mon, Apr 8, 2019 at 8:42 AM Willem Jiang
> wrote:
>
> > +1 binding.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sun, Apr 7, 2019 at 2:47 PM
+1 (binding)
Thanks,
Nicola
On Mon, Apr 8, 2019 at 8:42 AM Willem Jiang wrote:
> +1 binding.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Apr 7, 2019 at 2:47 PM Gregor Zurowski
> wrote:
> >
> > Hi Everyone:
> >
> > This is a vote to release Apache Camel 2.23.2, the
astefanutti opened a new pull request #596: Upgrade Operator SDK to version
0.7.0
URL: https://github.com/apache/camel-k/pull/596
This is an automated message from the Apache Git Service.
To respond to the message, please
astefanutti commented on issue #595: Set platform as integration contexts owner
URL: https://github.com/apache/camel-k/pull/595#issuecomment-480863468
There is a `Controller` field in the `OwnerReference` API that can be set to
indicate that _control_ behaviour
nicolaferraro commented on issue #595: Set platform as integration contexts
owner
URL: https://github.com/apache/camel-k/pull/595#issuecomment-480853258
Well... I'm not sure, but give my two cents..
Technically the owner relationship seems to matter to the [garbage
astefanutti commented on issue #595: Set platform as integration contexts owner
URL: https://github.com/apache/camel-k/pull/595#issuecomment-480846612
I realise having the platform _owning_ the integration contexts has larger
implications in the code. In multiple places the _active_
astefanutti commented on a change in pull request #595: Set platform as
integration contexts owner
URL: https://github.com/apache/camel-k/pull/595#discussion_r273006893
##
File path: pkg/controller/integrationcontext/initialize.go
##
@@ -45,19 +47,24 @@ func (action
stevef1uk commented on issue #537: camel-k-operator pod CrashLoopBackOff on
minikube on restart
URL: https://github.com/apache/camel-k/issues/537#issuecomment-480791580
Resolves itself if left (tried on Camel K Client 0.3.2).
stevef1uk closed issue #537: camel-k-operator pod CrashLoopBackOff on minikube
on restart
URL: https://github.com/apache/camel-k/issues/537
This is an automated message from the Apache Git Service.
To respond to the
lburgazzoli commented on a change in pull request #595: Set platform as
integration contexts owner
URL: https://github.com/apache/camel-k/pull/595#discussion_r272983820
##
File path: pkg/controller/integrationcontext/initialize.go
##
@@ -45,19 +47,24 @@ func (action
lburgazzoli commented on issue #591: trait: move replicas from integration to
deployment trait
URL: https://github.com/apache/camel-k/pull/591#issuecomment-480756310
We should investigate a little bit more about kamel cli ux to define scaling
lburgazzoli opened a new issue #594: Add conditions to camel-k CRs
URL: https://github.com/apache/camel-k/issues/594
In order to improve visibility of what happened to camel-k CRs, we should
add conditions to CRs, like:
lburgazzoli opened a new issue #593: Improve container image layering
URL: https://github.com/apache/camel-k/issues/593
We should improve container image layering so instead of throwing blobs to
s2i or just add folders to kaninko docker file, we should create dockerfiles
with individual
lburgazzoli opened a new issue #592: build order strategy
URL: https://github.com/apache/camel-k/issues/592
The builder state machine does not define an order in which queue build are
executed so we can provide a number of strategies like:
- fifo: execute the requests in the order
lburgazzoli commented on issue #591: trait: move replicas from integration to
deployment trait
URL: https://github.com/apache/camel-k/pull/591#issuecomment-480707808
The mai reason to move it was to be symmetric with the knative serving
stuffs but it can be ignored :)
On Mon, 8
+1 (binding)
On Mon, Apr 8, 2019 at 7:34 AM Gregor Zurowski wrote:
>
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.22.4, the fourth patch
> release for the camel-2.22.x branch with 26 improvements and bug
> fixes.
>
> Release notes:
>
astefanutti merged pull request #590: cleanup
URL: https://github.com/apache/camel-k/pull/590
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
+1 binding.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Sun, Apr 7, 2019 at 2:47 PM Gregor Zurowski wrote:
>
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.23.2, the second patch
> release for the camel-2.23.x branch with 64 improvements and bug
> fixes.
>
> Release
22 matches
Mail list logo
