Adrian wrote: > Thanks for the stats. How did you produce them? From the csv output of the issue tracker. I used an old Delphi hack and a calculator, but if you're interested in generating some kind of burn-down chart, I can do a Pharo version. (or a DabbleDB one, I guess)
> One way to alleviate the problem is if more people help. There is > work for everybody. I know, but that's not likely to solve this problem. More people = more scope creep. The issue is that if Pharo is to be a professional development tool, the release schedule should be somewhat reliable. If we miss a milestone, just adding another month to the schedule isn't working very well. Stephan _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
