Sounds good!

2008/11/6 Claus Ibsen <[EMAIL PROTECTED]>:
> Hi
>
> I propose a work plan such as:
>
> You and Hadrian should work on the remaining issues with refactoring the API 
> to remove the generics and get it as correct. You are the best people for 
> this work. Also very important that you guys look at the "remove unneeded 
> copies of exchanges".
>
> Then Jonathan can work on the renaming of the DSL's. And he could also help 
> removing the stuff that has been marked as @deprecated. He has already done 
> some of this stuff before. And as a 2nd priority to find the gaps in the 
> spring DSL vs. Java DSL.
>
> I would like to use this break to focus on the wiki documentation and my 
> tutorial that I need to continue on part 5.
>
>
> Med venlig hilsen
>
> Claus Ibsen
> ......................................
> Silverbullet
> Skovsgårdsvænget 21
> 8362 Hørning
> Tlf. +45 2962 7576
> Web: www.silverbullet.dk
>
> -----Original Message-----
> From: James Strachan [mailto:[EMAIL PROTECTED]
> Sent: 6. november 2008 10:20
> To: [email protected]
> Subject: Re: [Discussion] - Camel 1.5.1 - What should we add and what not
>
> 2008/11/6 Claus Ibsen <[EMAIL PROTECTED]>:
>> Hi
>>
>> Yeah could be a good idea to let 2.0.0 solely be focused on changing the API.
>> - generics
>> - verbs for DSL
>> - remove @deprecated stuff
>>
>> And then we can be back on track with hammering 200+ issues every 3rd month.
>
> Yeah!  I kinda think we should focus almost exclusively on the stuff
> that might result in API changes ASAP. e.g. how fast can we get Camel
> when its being used as a JMS <-> JMS router or a JBI <-> JBI router.
>
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>



-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://fusesource.com/

Reply via email to