Am 20.02.2013 um 16:22 schrieb Henryk Konsek <hekon...@gmail.com>:

>> But aren't there situations today where people might not be able to update 
>> camel?
> 
> These situations are minor ones comparing to the size of
> incompatibility that will be caused by introducing components not
> supported by the committers team.

Incompatibility to what? If e.g. the API I develop components against changes 
frequently that's a risk and then the project might not be mature enough that 
others are able to develop components. And then it's best that committers are 
playing close attention to all components. But I do think that people other 
than committers are able (or should be able) to develop components which do not 
break between releases.

> 
>> No need to stop working on select components and either release them 
>> together with core or put them in the marketplace.
> 
> If we encourage users to take advantage of marketplace, then we
> encourage them to use unstable components as well. That's the problem.

Does that mean that all components currently released are stable and never 
break? And all components in a marketplace are unstable per se? Of course there 
might be components developed by others which do not adhere to the same 
standards as components people with deep knowledge about camel are able to 
develop. But that can only mean that component development needs a deep 
understanding about the internals of core. Maybe an are which could be 
addressed.

> 
>> You are right - components are what people are interested in.
>> But the number of components will not shrink if there is no decision to 
>> abandon some of them.
> 
> The question is do we really need to abandon them? The majority of the
> components don't need extra care between releases.

Didn't mean to abandon them. What I wanted to say is that the decision to have 
something like a marketplace or component repository doesn't mean that 
committers have to stop working on the components available. Only if they make 
a decision to do so they might be abandoned. 
> 
> -- 
> Henryk Konsek
> http://henryk-konsek.blogspot.com

Reply via email to