[GitHub] [camel-website] zregvart commented on a change in pull request #45: some errors fixed

zregvart commented on a change in pull request #45: some errors fixed URL: https://github.com/apache/camel-website/pull/45#discussion_r294503880 ## File path: config.toml ## @@ -59,7 +59,7 @@ disablePathToLower = true parent = "docs" weight = 4 identifier =

[GitHub] [camel-k-runtime] lburgazzoli closed issue #82: Support full yaml dsl

lburgazzoli closed issue #82: Support full yaml dsl URL: https://github.com/apache/camel-k-runtime/issues/82 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [camel-website] Nayananga opened a new pull request #45: some errors fixed

Nayananga opened a new pull request #45: some errors fixed URL: https://github.com/apache/camel-website/pull/45 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [camel-k] nicolaferraro opened a new issue #751: Make sure global and local operators can cohexist

nicolaferraro opened a new issue #751: Make sure global and local operators can cohexist URL: https://github.com/apache/camel-k/issues/751 Don't know if this is needed or can be manager completely within OLM, but if installed manually, two operators (a global and a local one) in a cluster

[GitHub] [camel-k] nicolaferraro commented on issue #745: Add a --global install option

nicolaferraro commented on issue #745: Add a --global install option URL: https://github.com/apache/camel-k/issues/745#issuecomment-502617440 Yes, sounds good. I think we need also a way to make sure global operator and local operator don't conflict if both are installed, but I'll open

Re: GSoc 2019 Projects announced

Hi Nayananga, and, right now, I'm having 1442 link errors when running against remote. We have a very high number of commits per day, so the bits in the remote git are changing quite frequently, perhaps you waren't updated to the latest version locally. So perhaps try a `git pull` and check then.

Re: Cleaning up branches on git

Hi Gregor, +1 sound good to me zoran On Mon, Jun 17, 2019 at 8:49 AM Gregor Zurowski wrote: > > Hi Claus, > > Regarding 1: All release branches can be removed. We can also make it > a practice to remove them once a new release is published and merged > back into the corresponding parent branch

[GitHub] [camel-k] jamesnetherton commented on issue #745: Add a --global install option

jamesnetherton commented on issue #745: Add a --global install option URL: https://github.com/apache/camel-k/issues/745#issuecomment-502561367 Just want to check that my understanding of what the workflow would look like for this is correct. I was thinking something like: 1. Install

Re: Cleaning up branches on git

+1 Thanks Gregor Il giorno lun 17 giu 2019 alle ore 08:54 Gregor Zurowski < gre...@list.zurowski.org> ha scritto: > If everyone agrees, I will clean up the existing release branches > mentioned before. > > Thanks, > Gregor > > On Mon, Jun 17, 2019 at 8:48 AM Gregor Zurowski > wrote: > > > > Hi

Re: Release Candidate for Camel 2.24.1

Hi No you are welcome to begin the RC for this release. On Mon, Jun 17, 2019 at 8:53 AM Gregor Zurowski wrote: > > Hi Everyone, > > We've released Camel 2.24.0 on May 12. I guess it's time to start > thinking about a release candidate for Camel 2.24.1. Do you have any > outstanding changes

Re: Cleaning up branches on git

On Mon, Jun 17, 2019 at 8:54 AM Gregor Zurowski wrote: > > If everyone agrees, I will clean up the existing release branches > mentioned before. > +1 > Thanks, > Gregor > > On Mon, Jun 17, 2019 at 8:48 AM Gregor Zurowski > wrote: > > > > Hi Claus, > > > > Regarding 1: All release branches can

Re: Release Candidate for Camel 2.24.1

We should be ok with a new 2.24.x release. No outstanding changes from my side. Thanks Gregor. Il giorno lun 17 giu 2019 alle ore 08:53 Gregor Zurowski < gre...@list.zurowski.org> ha scritto: > Hi Everyone, > > We've released Camel 2.24.0 on May 12. I guess it's time to start > thinking about

Re: Cleaning up branches on git

If everyone agrees, I will clean up the existing release branches mentioned before. Thanks, Gregor On Mon, Jun 17, 2019 at 8:48 AM Gregor Zurowski wrote: > > Hi Claus, > > Regarding 1: All release branches can be removed. We can also make it > a practice to remove them once a new release is

Release Candidate for Camel 2.24.1

Hi Everyone, We've released Camel 2.24.0 on May 12. I guess it's time to start thinking about a release candidate for Camel 2.24.1. Do you have any outstanding changes for the camel-2.24.x branch? Thanks in advance, Gregor

Re: Cleaning up branches on git

Hi Claus, Regarding 1: All release branches can be removed. We can also make it a practice to remove them once a new release is published and merged back into the corresponding parent branch (master or minor release). Thanks, Gregor On Fri, May 31, 2019 at 6:42 AM Claus Ibsen wrote: > > Hi > >

[ANNOUNCEMENT] Apache Camel 2.23.3 Released

The Camel community announces the immediate availability of the Camel 2.23.3 patch release. This release contains 32 fixes and improvements applied in the past weeks on the 2.23.x branch. The artifacts are published and ready for you to download [1] either from the Apache mirrors or from the

Re: GSoc 2019 Projects announced

Hello everyone, one more question, in site.yml, when I use camel as remote repository it gives me 1468 errors. but if I use camel as local repository it gives me 2023 errors, and there are some specific additional errors. (Screenshots attached - 1). But I want to use camel as local repository.