Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
From: Antonin Stefanutti <antonin@stefanutti.fr>
To: "dev@camel.apache.org" <dev@camel.apache.org>
Subject: Re: Camel 2.19 Roadmap
Thread-Topic: Camel 2.19 Roadmap
Thread-Index: AQHSb9sBvkq8KaXEzkSG7DlUesjtDqGV2/sAgB4KhYCAAzPKgIACuasAgAhKdoCAAAO6gA==
Date: Wed, 12 Apr 2017 13:35:48 +0000
Message-ID: <054035E8-B6D6-4636-B52D-D85A7B9F9C85@stefanutti.fr>
References: <CAGB5yNnndh24TLPL-rs4Vb1-foxXmXHdkRa3C=KHW_r9kPdNEw@mail.gmail.com>
 <CAGB5yNkt-+7cTfSRW3wrhgJRJw+BPKRmRjL0vsjspr=QpntRgw@mail.gmail.com>
 <CADL1oArZDm8_8Gyy-e15NeUQajdota+iUcsRSiiOTV65oi_VLg@mail.gmail.com>
 <CAGB5yN=2bgLei+g6uQEMBp9UpmrNyR1CmT-GO7e-Vamrc+4bRg@mail.gmail.com>
 <CADL1oAq3UFMbOZkofhgrqd6B8rhxpr3UUz_dks5+Btm_S2A6zw@mail.gmail.com>
 <CAGB5yN=z-4v=jO04NDfCCubi8+wgZeRVFJJhQVsfe9f5ZQovhw@mail.gmail.com>
In-Reply-To: <CAGB5yN=z-4v=jO04NDfCCubi8+wgZeRVFJJhQVsfe9f5ZQovhw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [81.57.228.108]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FE3A9C8C0CC49A40AB7B419DB908E295@indiv.local>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Ovh-Tracer-Id: 3262294981173814279
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: 0
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeeliedrudeigdeiiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemuceftddtnecu
archived-at: Wed, 12 Apr 2017 13:36:24 -0000


> On 12 Apr 2017, at 15:22, Claus Ibsen <claus.ibsen@gmail.com> wrote:
>=20
> Hi
>=20
> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
>=20
> So we are closing down on the last tickets, bugs, features etc to get
> the code base in shape.
>=20
> The JIRA has 9 tickets
> https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20CAMEL%20AND%=
20fixVersion%20%3D%202.19.0%20AND%20resolution%20%3D%20Unresolved
>=20
> 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.
>=20
> 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/
>=20
>=20
>=20
>=20
>=20
> On Fri, Apr 7, 2017 at 8:45 AM, Gregor Zurowski
> <gregor@list.zurowski.org> wrote:
>> Hi Claus,
>>=20
>> Week 16 works for me.  I will send out another email shortly before
>> starting to build the RC.
>>=20
>> Thanks,
>> Gregor
>>=20
>>=20
>> On Wed, Apr 5, 2017 at 3:08 PM, Claus Ibsen <claus.ibsen@gmail.com> wrot=
e:
>>> Hi Gregor
>>>=20
>>> Yeah its April so we should get the 2.19.0 release out the door.
>>>=20
>>> 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.
>>>=20
>>> 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.
>>>=20
>>> As April has the easter holidays. I wonder what you time schedule looks=
 like?
>>>=20
>>> Maybe if you have time to help with the release after the holidays?
>>>=20
>>> 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.
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> On Mon, Apr 3, 2017 at 2:14 PM, Gregor Zurowski
>>> <gregor@list.zurowski.org> wrote:
>>>> Hi,
>>>>=20
>>>> 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.
>>>>=20
>>>> Thanks,
>>>> Gregor
>>>>=20
>>>>=20
>>>> On Wed, Mar 15, 2017 at 9:29 AM, Claus Ibsen <claus.ibsen@gmail.com> w=
rote:
>>>>> Hi
>>>>>=20
>>>>> Just wanted to bring up that we are closing in on a good time for
>>>>> doing a new release.
>>>>>=20
>>>>> For example in mid April it would be around 6 months since the last
>>>>> 2.18.0 release.
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> On Mon, Jan 16, 2017 at 10:28 AM, Claus Ibsen <claus.ibsen@gmail.com>=
 wrote:
>>>>>> Hi
>>>>>>=20
>>>>>> There is a bunch of stuff which we can/should have on the roadmap to
>>>>>> complete for the Camel 2.19 release.
>>>>>>=20
>>>>>> Here is on top of my head
>>>>>>=20
>>>>>> 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/re=
adme-eip.adoc
>>>>>>=20
>>>>>> 2)
>>>>>> Generate documentation and website. Maybe documentation first and th=
en
>>>>>> we come up with a modern website later - when we have a new logo as
>>>>>> well.
>>>>>>=20
>>>>>> 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 dep=
recate.
>>>>>> For example the old stuff that was created prior to the component do=
cs
>>>>>> we do now with the apt plugin at build time instead of this old code
>>>>>> with runtime that dont really pan out anyway.
>>>>>>=20
>>>>>> 4)
>>>>>> Move spring-boot starters into the platforms folder. There is a tick=
et
>>>>>> about this.
>>>>>>=20
>>>>>> 5)
>>>>>> More improvements to spring boot auto configuration. We have a bunch
>>>>>> of tickets on that.
>>>>>>=20
>>>>>> 6)
>>>>>> Look at the health check API and see if there is something we can ge=
t
>>>>>> started on.
>>>>>> Possible some API to integrate with spring boot actuators (when usin=
g
>>>>>> SB) and allow each component to provide their own checks so they can
>>>>>> be implemented ad-hoc. There is a ticket about this.
>>>>>>=20
>>>>>> 7)
>>>>>> Possible some more teaks to camel-catalog based on feedback from IDE=
A
>>>>>> plugin and the maven validate goal.
>>>>>>=20
>>>>>> 8)
>>>>>> That CDI JEE transaction PR on github.
>>>>>> Ideally we would have had a transaction API in camel-core and then o=
ne
>>>>>> impl for camel-spring, and then another for camel-cdi-jee. But that
>>>>>> may require too much work.
>>>>>>=20
>>>>>> 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.
>>>>>>=20
>>>>>> 10)
>>>>>> Karaf users may want to improve/finish up the camel-test-karaf modul=
e
>>>>>> so its more usable and end users can use it to test integration test=
s
>>>>>> with Camel and Karaf.
>>>>>>=20
>>>>>> 11)
>>>>>> Introduce Camel Connectors (more about this later)
>>>>>>=20
>>>>>>=20
>>>>>> Anything else?
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> http://davsclaus.com @davsclaus
>>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2
>>>=20
>>>=20
>>>=20
>>> --
>>> Claus Ibsen
>>> -----------------
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>=20
>=20
>=20
> --=20
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2