Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BAAAE200C6A for ; Wed, 19 Apr 2017 14:22:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B9345160B94; Wed, 19 Apr 2017 12:22:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B285C160B86 for ; Wed, 19 Apr 2017 14:22:06 +0200 (CEST) Received: (qmail 10802 invoked by uid 500); 19 Apr 2017 12:22:05 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 10788 invoked by uid 99); 19 Apr 2017 12:22:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Apr 2017 12:22:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D9CAD1A7A4D for ; Wed, 19 Apr 2017 12:22:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.396 X-Spam-Level: X-Spam-Status: No, score=-2.396 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id C2dyjApIFhhl for ; Wed, 19 Apr 2017 12:22:00 +0000 (UTC) Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C81075F4EE for ; Wed, 19 Apr 2017 12:21:59 +0000 (UTC) Received: by mail-io0-f178.google.com with SMTP id a103so20126522ioj.1 for ; Wed, 19 Apr 2017 05:21:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=EFRu4vAiX7vknuQCn0jpX55Z+mcIgcKLV8tMuo2Cl9A=; b=GMtVWmflc6+AqxKbpDq0ixratyWz5kRWrz3csPP7ZiYYHREhXpo217Yq42yh2m9U5v MIJ3gAb1wILx+IRq3CBauEDh4iuoTGITlNYzGLt/JShGYpk2+oxzUgbvEGq0OxA/wIsS xmDt67XI01ZPiVZ+CAFe9/fnwMNaY88lbaX5g8eCWj02OQK+8bTwpK6UaEPwpUgwzSdt bqd6TsLbUTMLHvRZT/jtvix/2ye90W8NXnVf/RHtXcY0LNSKivrZnblgxYx1+iJA9sKJ Fqu5NLAN6znCinG/i9GHIjItUkarle+j1LXGyAU0WKAfQ7XqACXF+9UDIV98lmO2hP8v eaHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=EFRu4vAiX7vknuQCn0jpX55Z+mcIgcKLV8tMuo2Cl9A=; b=n+YK+GLMxQYL4d+ZFNkmbNBpvDwkpHm+/LCIzNMiA6HueuQrxwkp2oqnPAMYR7FCWc CNnjiuGnsf4VhdChPaTw8MmeZ5R7DXckLxKxqojYz9xAxCz7aQcS2izGdbmL5SPHEDIG 322FZsqtc/DX+agwK+M89Z75hsX6EX2i7ZWOqPrjjiiXfM9M8fnDhL1YGUcQsw98s1W+ mHPrYHccyCYvJypUCTAC8UtYQa4pnsJe1tYHmmFDIIH2Ymazwt5Rd9fLkeTv9KOqNOk5 SkK4TivlTtIney3D8F3u4x5mnC1Oy4DknsnqWCu3qNiqiEukEPMQdH5mb2LODro2r8va GS1Q== X-Gm-Message-State: AN3rC/6H7Lc5yHy6/4NZ6sOdrTMzu9ZWlLkpo46gm1BJDXTvcAeBHldD 25mRNTqHvBocwjyjL+98w8QEEhusbBty X-Received: by 10.107.189.68 with SMTP id n65mr2618139iof.154.1492604518259; Wed, 19 Apr 2017 05:21:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.103.131 with HTTP; Wed, 19 Apr 2017 05:21:57 -0700 (PDT) In-Reply-To: References: <054035E8-B6D6-4636-B52D-D85A7B9F9C85@stefanutti.fr> From: Luca Burgazzoli Date: Wed, 19 Apr 2017 14:21:57 +0200 Message-ID: Subject: Re: Camel 2.19 Roadmap To: dev@camel.apache.org Content-Type: text/plain; charset=UTF-8 archived-at: Wed, 19 Apr 2017 12:22:07 -0000 Hi, I have one little refactoring (rename LoadBalancer in camel cloud package to avoid confusion with LoadBalancer processor) and a little doc update that I'm trying to make by end of day. --- Luca Burgazzoli On Wed, Apr 19, 2017 at 1:39 PM, Claus Ibsen wrote: > Hi > > So the @Generated and Java 9 ought to be fixed now. > > There is a new version of Spring Boot 1.5.3 on the way. It may be > beneficial to wait for that to be released so we are running on > latest. > > On Wed, Apr 19, 2017 at 9:54 AM, Claus Ibsen wrote: >> Hi >> >> Okay so there is some last minute issues with the @Generated >> annotations we need to look into >> https://issues.apache.org/jira/browse/CAMEL-11165 >> >> And an unforseen effect on java 9 builds >> https://issues.apache.org/jira/browse/CAMEL-11166 >> >> The full test is passing now. And the Spring Boot and Karaf tests has >> also passed but failed recently due some maven download error or some >> other weird error. So lets kick new builds when we get the 2 tickets >> resolved above. >> >> >> >> >> On Tue, Apr 18, 2017 at 9:45 AM, Claus Ibsen wrote: >>> Hi >>> >>> Things start to look good. There is a itest that fails with spring >>> boot which we need to look at and get fixed >>> https://issues.apache.org/jira/browse/CAMEL-11154 >>> >>> The other tests was all passing recently and they ought to become blue >>> again. But lets keep an eye on them: >>> https://builds.apache.org/view/A-D/view/Camel/ >>> >>> >>> On Thu, Apr 13, 2017 at 1:50 PM, Claus Ibsen wrote: >>>> Hi >>>> >>>> Thanks Antonin that sounds great. >>>> >>>> The JIRA tickets are down to 3 >>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved >>>> >>>> We have recently fixed up the missing component docs and fixed broken >>>> links from browsing on github. >>>> >>>> We should keep an eye on the CI servers and output from the >>>> camel-catalog report, to see if it reports more missing stuff. >>>> It currently has a false positive on some missing docs for some of the >>>> test components. I will try to fix this later today. >>>> >>>> However thats not all. At all time feel free to have fun and work on >>>> anything you like on Camel. There is still time for small improvements >>>> etc. But bigger stuff we should really defer to the next release. >>>> >>>> >>>> On Wed, Apr 12, 2017 at 3:35 PM, Antonin Stefanutti >>>> wrote: >>>>> >>>>>> On 12 Apr 2017, at 15:22, Claus Ibsen wrote: >>>>>> >>>>>> Hi >>>>>> >>>>>> Just a heads up that we plan to cut the RC for Camel 2.19 next week. >>>>>> >>>>>> So we are closing down on the last tickets, bugs, features etc to get >>>>>> the code base in shape. >>>>>> >>>>>> The JIRA has 9 tickets >>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved >>>>>> >>>>>> But you are of course welcome to work on other tickets etc but just >>>>>> mind any big functionality is likely better to wait for next release. >>>>>> >>>>>> There is however the expected transaction stuff for CDI as a PR in the >>>>>> works, and also a new iot component >>>>>> https://github.com/apache/camel/pulls >>>>> >>>>> The CDI transaction support PR should be merged by end of week. >>>>> >>>>> https://github.com/apache/camel/pull/1390 >>>>> >>>>>> We should keep an eye on the CI servers to see how they are and fix >>>>>> any test failures etc. Recently we got them to build and test the OSGi >>>>>> and spring-boot specific tests so we should be able to better keep an >>>>>> eye on this now and in the future. >>>>>> https://builds.apache.org/view/A-D/view/Camel/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski >>>>>> wrote: >>>>>>> Hi Claus, >>>>>>> >>>>>>> Week 16 works for me. I will send out another email shortly before >>>>>>> starting to build the RC. >>>>>>> >>>>>>> Thanks, >>>>>>> Gregor >>>>>>> >>>>>>> >>>>>>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen wrote: >>>>>>>> Hi Gregor >>>>>>>> >>>>>>>> Yeah its April so we should get the 2.19.0 release out the door. >>>>>>>> >>>>>>>> We have just setup a 2.20.0 version in JIRA and folks should start >>>>>>>> moving their tickets to that version if its something that they cannot >>>>>>>> finish in time. Also we should refrain from doing bigger work at this >>>>>>>> time as we should close down on last tickets, bug fixes, and get the >>>>>>>> CI tests in good order, etc. >>>>>>>> >>>>>>>> I will look at the JIRAs later this week and cleanup a bit so we have >>>>>>>> a better overview of what work is yet to be done. >>>>>>>> >>>>>>>> As April has the easter holidays. I wonder what you time schedule looks like? >>>>>>>> >>>>>>>> Maybe if you have time to help with the release after the holidays? >>>>>>>> >>>>>>>> Week 16 and 17 are the last 2 weeks in April after the holidays. >>>>>>>> If we could maybe cut the RC in week 16 then that would be good. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski >>>>>>>> wrote: >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> Are we getting closer to build a 2.19.0 release? I would volunteer >>>>>>>>> for creating the release, just wanted to check when would be a good >>>>>>>>> time to do so. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Gregor >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen wrote: >>>>>>>>>> Hi >>>>>>>>>> >>>>>>>>>> Just wanted to bring up that we are closing in on a good time for >>>>>>>>>> doing a new release. >>>>>>>>>> >>>>>>>>>> For example in mid April it would be around 6 months since the last >>>>>>>>>> 2.18.0 release. >>>>>>>>>> >>>>>>>>>> Therefore we should start closing down and fixing bugs, and make sure >>>>>>>>>> the CI servers and tests are in good shape. >>>>>>>>>> This morning we have fixed a number of recent test failures and are >>>>>>>>>> down to only 1 test failure now. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen wrote: >>>>>>>>>>> Hi >>>>>>>>>>> >>>>>>>>>>> There is a bunch of stuff which we can/should have on the roadmap to >>>>>>>>>>> complete for the Camel 2.19 release. >>>>>>>>>>> >>>>>>>>>>> Here is on top of my head >>>>>>>>>>> >>>>>>>>>>> 1) >>>>>>>>>>> Finish migrating the wiki documentation to adoc files. I think its >>>>>>>>>>> most of the EIP patterns that are missing. There is a basic list of >>>>>>>>>>> EIPs here: https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc >>>>>>>>>>> >>>>>>>>>>> 2) >>>>>>>>>>> Generate documentation and website. Maybe documentation first and then >>>>>>>>>>> we come up with a modern website later - when we have a new logo as >>>>>>>>>>> well. >>>>>>>>>>> >>>>>>>>>>> 3) >>>>>>>>>>> Mark more stuff to @deprecate so we dont drag them into Camel 3.0. >>>>>>>>>>> This is both components / and other artifacts. >>>>>>>>>>> And as well the camel-core APIs where there is maybe more we can deprecate. >>>>>>>>>>> For example the old stuff that was created prior to the component docs >>>>>>>>>>> we do now with the apt plugin at build time instead of this old code >>>>>>>>>>> with runtime that dont really pan out anyway. >>>>>>>>>>> >>>>>>>>>>> 4) >>>>>>>>>>> Move spring-boot starters into the platforms folder. There is a ticket >>>>>>>>>>> about this. >>>>>>>>>>> >>>>>>>>>>> 5) >>>>>>>>>>> More improvements to spring boot auto configuration. We have a bunch >>>>>>>>>>> of tickets on that. >>>>>>>>>>> >>>>>>>>>>> 6) >>>>>>>>>>> Look at the health check API and see if there is something we can get >>>>>>>>>>> started on. >>>>>>>>>>> Possible some API to integrate with spring boot actuators (when using >>>>>>>>>>> SB) and allow each component to provide their own checks so they can >>>>>>>>>>> be implemented ad-hoc. There is a ticket about this. >>>>>>>>>>> >>>>>>>>>>> 7) >>>>>>>>>>> Possible some more teaks to camel-catalog based on feedback from IDEA >>>>>>>>>>> plugin and the maven validate goal. >>>>>>>>>>> >>>>>>>>>>> 8) >>>>>>>>>>> That CDI JEE transaction PR on github. >>>>>>>>>>> Ideally we would have had a transaction API in camel-core and then one >>>>>>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that >>>>>>>>>>> may require too much work. >>>>>>>>>>> >>>>>>>>>>> 9) >>>>>>>>>>> Work on the Java 8 DSL such as get more community feedback, and then >>>>>>>>>>> resolve the TODOs with the documentation updates and look into other >>>>>>>>>>> areas where the API can benefit from Java 8 lambdas and whatnot. I >>>>>>>>>>> dont think we have a ticket about this. >>>>>>>>>>> >>>>>>>>>>> 10) >>>>>>>>>>> Karaf users may want to improve/finish up the camel-test-karaf module >>>>>>>>>>> so its more usable and end users can use it to test integration tests >>>>>>>>>>> with Camel and Karaf. >>>>>>>>>>> >>>>>>>>>>> 11) >>>>>>>>>>> Introduce Camel Connectors (more about this later) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Anything else? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Claus Ibsen >>>>>>>>>>> ----------------- >>>>>>>>>>> http://davsclaus.com @davsclaus >>>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Claus Ibsen >>>>>>>>>> ----------------- >>>>>>>>>> http://davsclaus.com @davsclaus >>>>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Claus Ibsen >>>>>>>> ----------------- >>>>>>>> http://davsclaus.com @davsclaus >>>>>>>> Camel in Action 2: https://www.manning.com/ibsen2 >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Claus Ibsen >>>>>> ----------------- >>>>>> http://davsclaus.com @davsclaus >>>>>> Camel in Action 2: https://www.manning.com/ibsen2 >>>>> >>>> >>>> >>>> >>>> -- >>>> Claus Ibsen >>>> ----------------- >>>> http://davsclaus.com @davsclaus >>>> Camel in Action 2: https://www.manning.com/ibsen2 >>> >>> >>> >>> -- >>> Claus Ibsen >>> ----------------- >>> http://davsclaus.com @davsclaus >>> Camel in Action 2: https://www.manning.com/ibsen2 >> >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2