In Camel 3.2.0 we’ll release the complete set of Camel AWS2 components. In Camel 3.1.0 we already have a bunch of AWS2 components living together with the original AWS components. The aim of this post is giving a full perspective of what will change for the end users and the roadmap for new features. New components Except camel-aws-xray, which is a particular component needing much more work to be migrated, all the original AWS components have been migrated to AWS SDK v2.
This year in addition to the Google Summer of Code we’re participating in the Outreachy internship program as well. For those that might not be aware of the Outreachy, Outreachy is a paid, remote internship program. Outreachy’s goal is to support people from groups underrepresented in tech. They help newcomers to free software and open source make their first contributions. Apache Camel is looking for contributions to the website you’re reading this blog post on.
The Camel community announces the immediate availability of Camel 3.1.0, a new minor release with over 291 new features, improvements and fixes. All users of Camel 3.0 are encouraged to upgrade to Camel 3.1 soon because there are some major memory usage optimizations in this release. We also plan to retire Camel 3.0 very soon due to this. Please read our Camel 3.x upgrade guide that describes how to upgrade Camel 3.