> A 1.0 release based off 0.20 would give us a chance to state more precisely 
> the 1.0 API that we intend to support long-term.  For example, we might 
> un-mark the old mapreduce APIs as deprecated in a 1.0 release, and mark the 
> new mapreduce APIs as experimental and unstable there. Programs that use only 
> public stable features in 1.0 could be then guaranteed to run for a long-time 
> hence.
> 

+1 

ckw

--
Chris K Wensel
ch...@concurrentinc.com
http://www.concurrentinc.com

Reply via email to