You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2017/10/12 11:04:31 UTC
[DISCUSS] - Plan for rest of 2017 and bigger goals for Apache Camel 2.21
Hi
Now that Camel 2.20 is released, then I think it would be good to put
out some overall goal of what we among others can/should work on for
the remainder of 2017 in terms of Apache Camel and the next release.
The next release is Apache Camel 2.21 which IMHO should provide these
bigger goals
1)
Official Java 9 support.
We have already done great work in the 2.20 release to have it Java 9
as technical preview. But we should continue this work. For example we
should include the Java 9 automatic module names. See PR:
https://github.com/apache/camel/pull/2007. However we should agree on
the naming convention to be used.
2)
Spring Boot 2 support
We prepared for this in 2.20. Spring Boot 2 is expected to go GA later
this fall, and we should then be able to offer support for running
Camel on Spring Boot 2, and ideally also on Spring Boot 1 (for a
period of time). We did some experiment with this in the spring-boot2
branch. Its based on that work we should migrate over some commits and
ideally make the starter components work with both spring boot v1 and
v2.
3)
Migrate all wiki documentation to ascii docs
We should finish migrating all the remainder documentation. As first
priority is the migrate the EIPs and then afterwards the rest of the
documentation. We may skip some documentation that has become
outdated, or if we find out its better to write some new documentation
from scratch - for example the error handler documentation could use a
re-write.
4)
Build new documentation.
Based on #3 we should be able to build a new documentation in html
which we can publish on the website. Build documentation in other
formats such as pdf, ebook is 2nd priority. The top priority is on our
own website as html.
5)
Build new website.
In extension of #4 we should build up a new website. We could start
with maybe what the karaf team did, by creating a few fresh modern
looking pages for the front page and a few other pages. As ideally 98%
of the website should be the documentation (#4).
As part of this we should also use the new logo.
6)
Continue on the new experimental APIs that was introduced in 2.20 for
health check, clustering and route controller.
7)
The route-coverage tooling that I started, should be finished up and
include in the next release
http://camel.465427.n5.nabble.com/HEADS-UP-Apache-Camel-route-coverage-tooling-on-the-way-tp5814300.html
8)
Improve the spring boot auto configuration generated source code. We
have some tickets to make the -starter components better support some
more complex nested configuration classes and whatnot.
9)
Usual stuff with new components, community contributions, bug fixes,
and what else people feel like.
10)
Deprecate more components and other artifact when they are using EOL
or very old libraries. We have a bunch of components that are outdated
and in preparation for Camel 3.x we should start to deprecate some
more of them, so its easier to remove them in the future.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: [DISCUSS] - Plan for rest of 2017 and bigger goals for Apache
Camel 2.21
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Camel 2.21 is intended for start of 2018, hopefully January.
On Thu, Oct 12, 2017 at 5:21 PM, Quinn Stevenson
<qu...@pronoia-solutions.com> wrote:
> Do you have a timeframe in mind for 2.21? I already missed 2.20, and I have a bunch of updates and enhancements for camel-mllp that I’ve developed on a private for while working with a customer. I’d like to get the updates/enhancements included with the next release, but I’m not sure if I’ll be able to do much until after we go-live next month.
>
>> On Oct 12, 2017, at 5:04 AM, Claus Ibsen <cl...@gmail.com> wrote:
>>
>> Hi
>>
>> Now that Camel 2.20 is released, then I think it would be good to put
>> out some overall goal of what we among others can/should work on for
>> the remainder of 2017 in terms of Apache Camel and the next release.
>>
>> The next release is Apache Camel 2.21 which IMHO should provide these
>> bigger goals
>>
>> 1)
>> Official Java 9 support.
>>
>> We have already done great work in the 2.20 release to have it Java 9
>> as technical preview. But we should continue this work. For example we
>> should include the Java 9 automatic module names. See PR:
>> https://github.com/apache/camel/pull/2007. However we should agree on
>> the naming convention to be used.
>>
>>
>> 2)
>> Spring Boot 2 support
>>
>> We prepared for this in 2.20. Spring Boot 2 is expected to go GA later
>> this fall, and we should then be able to offer support for running
>> Camel on Spring Boot 2, and ideally also on Spring Boot 1 (for a
>> period of time). We did some experiment with this in the spring-boot2
>> branch. Its based on that work we should migrate over some commits and
>> ideally make the starter components work with both spring boot v1 and
>> v2.
>>
>>
>> 3)
>> Migrate all wiki documentation to ascii docs
>>
>> We should finish migrating all the remainder documentation. As first
>> priority is the migrate the EIPs and then afterwards the rest of the
>> documentation. We may skip some documentation that has become
>> outdated, or if we find out its better to write some new documentation
>> from scratch - for example the error handler documentation could use a
>> re-write.
>>
>>
>> 4)
>> Build new documentation.
>>
>> Based on #3 we should be able to build a new documentation in html
>> which we can publish on the website. Build documentation in other
>> formats such as pdf, ebook is 2nd priority. The top priority is on our
>> own website as html.
>>
>>
>> 5)
>> Build new website.
>>
>> In extension of #4 we should build up a new website. We could start
>> with maybe what the karaf team did, by creating a few fresh modern
>> looking pages for the front page and a few other pages. As ideally 98%
>> of the website should be the documentation (#4).
>>
>> As part of this we should also use the new logo.
>>
>>
>> 6)
>> Continue on the new experimental APIs that was introduced in 2.20 for
>> health check, clustering and route controller.
>>
>>
>> 7)
>> The route-coverage tooling that I started, should be finished up and
>> include in the next release
>> http://camel.465427.n5.nabble.com/HEADS-UP-Apache-Camel-route-coverage-tooling-on-the-way-tp5814300.html
>>
>>
>> 8)
>> Improve the spring boot auto configuration generated source code. We
>> have some tickets to make the -starter components better support some
>> more complex nested configuration classes and whatnot.
>>
>>
>> 9)
>> Usual stuff with new components, community contributions, bug fixes,
>> and what else people feel like.
>>
>>
>> 10)
>> Deprecate more components and other artifact when they are using EOL
>> or very old libraries. We have a bunch of components that are outdated
>> and in preparation for Camel 3.x we should start to deprecate some
>> more of them, so its easier to remove them in the future.
>>
>>
>>
>>
>> --
>> 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
Re: [DISCUSS] - Plan for rest of 2017 and bigger goals for Apache
Camel 2.21
Posted by Quinn Stevenson <qu...@pronoia-solutions.com>.
Do you have a timeframe in mind for 2.21? I already missed 2.20, and I have a bunch of updates and enhancements for camel-mllp that I’ve developed on a private for while working with a customer. I’d like to get the updates/enhancements included with the next release, but I’m not sure if I’ll be able to do much until after we go-live next month.
> On Oct 12, 2017, at 5:04 AM, Claus Ibsen <cl...@gmail.com> wrote:
>
> Hi
>
> Now that Camel 2.20 is released, then I think it would be good to put
> out some overall goal of what we among others can/should work on for
> the remainder of 2017 in terms of Apache Camel and the next release.
>
> The next release is Apache Camel 2.21 which IMHO should provide these
> bigger goals
>
> 1)
> Official Java 9 support.
>
> We have already done great work in the 2.20 release to have it Java 9
> as technical preview. But we should continue this work. For example we
> should include the Java 9 automatic module names. See PR:
> https://github.com/apache/camel/pull/2007. However we should agree on
> the naming convention to be used.
>
>
> 2)
> Spring Boot 2 support
>
> We prepared for this in 2.20. Spring Boot 2 is expected to go GA later
> this fall, and we should then be able to offer support for running
> Camel on Spring Boot 2, and ideally also on Spring Boot 1 (for a
> period of time). We did some experiment with this in the spring-boot2
> branch. Its based on that work we should migrate over some commits and
> ideally make the starter components work with both spring boot v1 and
> v2.
>
>
> 3)
> Migrate all wiki documentation to ascii docs
>
> We should finish migrating all the remainder documentation. As first
> priority is the migrate the EIPs and then afterwards the rest of the
> documentation. We may skip some documentation that has become
> outdated, or if we find out its better to write some new documentation
> from scratch - for example the error handler documentation could use a
> re-write.
>
>
> 4)
> Build new documentation.
>
> Based on #3 we should be able to build a new documentation in html
> which we can publish on the website. Build documentation in other
> formats such as pdf, ebook is 2nd priority. The top priority is on our
> own website as html.
>
>
> 5)
> Build new website.
>
> In extension of #4 we should build up a new website. We could start
> with maybe what the karaf team did, by creating a few fresh modern
> looking pages for the front page and a few other pages. As ideally 98%
> of the website should be the documentation (#4).
>
> As part of this we should also use the new logo.
>
>
> 6)
> Continue on the new experimental APIs that was introduced in 2.20 for
> health check, clustering and route controller.
>
>
> 7)
> The route-coverage tooling that I started, should be finished up and
> include in the next release
> http://camel.465427.n5.nabble.com/HEADS-UP-Apache-Camel-route-coverage-tooling-on-the-way-tp5814300.html
>
>
> 8)
> Improve the spring boot auto configuration generated source code. We
> have some tickets to make the -starter components better support some
> more complex nested configuration classes and whatnot.
>
>
> 9)
> Usual stuff with new components, community contributions, bug fixes,
> and what else people feel like.
>
>
> 10)
> Deprecate more components and other artifact when they are using EOL
> or very old libraries. We have a bunch of components that are outdated
> and in preparation for Camel 3.x we should start to deprecate some
> more of them, so its easier to remove them in the future.
>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
Re: [DISCUSS] - Plan for rest of 2017 and bigger goals for Apache
Camel 2.21
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
this sounds like a good plan to me, I hope to set aside some time to
work on the website and fix outstanding issues and also work on new
functionality in Salesforce component.
zoran
On Thu, Oct 12, 2017 at 1:04 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> Now that Camel 2.20 is released, then I think it would be good to put
> out some overall goal of what we among others can/should work on for
> the remainder of 2017 in terms of Apache Camel and the next release.
>
> The next release is Apache Camel 2.21 which IMHO should provide these
> bigger goals
>
> 1)
> Official Java 9 support.
>
> We have already done great work in the 2.20 release to have it Java 9
> as technical preview. But we should continue this work. For example we
> should include the Java 9 automatic module names. See PR:
> https://github.com/apache/camel/pull/2007. However we should agree on
> the naming convention to be used.
>
>
> 2)
> Spring Boot 2 support
>
> We prepared for this in 2.20. Spring Boot 2 is expected to go GA later
> this fall, and we should then be able to offer support for running
> Camel on Spring Boot 2, and ideally also on Spring Boot 1 (for a
> period of time). We did some experiment with this in the spring-boot2
> branch. Its based on that work we should migrate over some commits and
> ideally make the starter components work with both spring boot v1 and
> v2.
>
>
> 3)
> Migrate all wiki documentation to ascii docs
>
> We should finish migrating all the remainder documentation. As first
> priority is the migrate the EIPs and then afterwards the rest of the
> documentation. We may skip some documentation that has become
> outdated, or if we find out its better to write some new documentation
> from scratch - for example the error handler documentation could use a
> re-write.
>
>
> 4)
> Build new documentation.
>
> Based on #3 we should be able to build a new documentation in html
> which we can publish on the website. Build documentation in other
> formats such as pdf, ebook is 2nd priority. The top priority is on our
> own website as html.
>
>
> 5)
> Build new website.
>
> In extension of #4 we should build up a new website. We could start
> with maybe what the karaf team did, by creating a few fresh modern
> looking pages for the front page and a few other pages. As ideally 98%
> of the website should be the documentation (#4).
>
> As part of this we should also use the new logo.
>
>
> 6)
> Continue on the new experimental APIs that was introduced in 2.20 for
> health check, clustering and route controller.
>
>
> 7)
> The route-coverage tooling that I started, should be finished up and
> include in the next release
> http://camel.465427.n5.nabble.com/HEADS-UP-Apache-Camel-route-coverage-tooling-on-the-way-tp5814300.html
>
>
> 8)
> Improve the spring boot auto configuration generated source code. We
> have some tickets to make the -starter components better support some
> more complex nested configuration classes and whatnot.
>
>
> 9)
> Usual stuff with new components, community contributions, bug fixes,
> and what else people feel like.
>
>
> 10)
> Deprecate more components and other artifact when they are using EOL
> or very old libraries. We have a bunch of components that are outdated
> and in preparation for Camel 3.x we should start to deprecate some
> more of them, so its easier to remove them in the future.
>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
--
Zoran Regvart