We know. The problem is that we do not want to let code rot because we do not have the work load to deal with it. For closure the more we waited the more it becomes a problem and painful. We decided that we will include the event cleaning made by mike. After the large part is the MIT cleaning. Now please join and help fixing the pending points.
Can we do something about the way schedule slippage is handled? There is a lot of feature creep, and we are taking too small slippages.
Based on yesterdays weather, 1.0 is not going to be released in May 2009.
Issues were closed after on average 30 days, 48% within a week, but 10% took 85 days or longer. Of the new,started,accepted, fixed issues for 1.0 40% is 280 days old.
Stephan
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project