Github user sabre1041 closed the pull request at:
https://github.com/apache/camel/pull/512
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
The Apache Jenkins build system has built Camel.2.15.x.notest (build #58)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.2.15.x.notest/58/
to view the results.
The Apache Jenkins build system has built Camel.2.14.x.notest (build #159)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.2.14.x.notest/159/
to view the results.
Hi
I think we should if possible later this month release a new patch
release of this branch.
Any thoughts?
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http:
+1
Best,
Christian
Am 11.05.2015 04:13 schrieb "Willem Jiang" :
> We can update the code in Camel 2.15.x branch to warn the user the API
> could be removed in Camel 2.16.0 first, then we can clean up the quite old
> API.
>
> There are some APIs just marked with @deprecated but we don’t have any
>
Strictly speaking we should only remove deprecated code in the next
major release.
For functionality that is not used a lot I think we can make an
exemption though.
It is still important then that we list all removed functions in the
release notes so people are aware of it.
Christian
On 10.
BTW We might also think about cleaning old "Available since Camel 2.x"
notes from the documentation. IMHO We should keep information only about
the updates for the version of Camel we still support. That is 2.13 or
higher. Who cares that Camel 2.8 provides some "new" feature? ;)
pon., 11.05.2015 o
Hi,
I think that if we mark something as deprecated in 2.x, then we can safely
remove it in 2.(x + 1). Just need to be sure that the deprecation
information was available in the documentation between 2.x and 2.(x + 1)
period. And that we have provided some valid usage alternative for the
users.
C
