On Apr 8, 2009, at 15:31 , stephan@stack.nl wrote:

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)

Sure, that would be interesting to track our progress!

...

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.

There's certainly a tendency for more feature creep, but as we control what makes it into a milestone, its not that just anybody can add new stuff.

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.

I agree, there's room for improvement. One difficulty is that the available resources are hard to plan in advance as everybody is working on a voluntary basis. For example, I couldn't do much the last three weeks due to high priority work at my company, Marcus is moving, etc. Cheers, Adrian