And actually the core should not even change that often. And the api
should change even less often. Ideally we would only have major api
releases (ideally, that is).
Hopefully we'll find a better solution for our release process.
Cheers,
Hadrian
On 02/19/2013 05:21 PM, Henryk Konsek wrote:
Hi Christian,
How about a simpler model?
A component could specify the minimum camel core or better api in the future
it needs.
For example:
camel-jms 3.0 -> camel-core 3.0
camel-jms 3.1 -> camel-core 3.0
Unfortunately this approach doesn't address the problem that component
users still need to wait for core to be released if they want the
latest version of the component. The main issue I try to address is to
give the users faster access the to the released components without
waiting for the core release.
Best regards.
