the idea is like that: - send an email that you are fixing an issue (optional) - check write emails - fix it - publish it and ask for feedback. I think that also reviewing fixes of other, writing new tests, or adding comments to classes is also important. Stef On Jun 13, 2009, at 3:15 AM, Gabriel Cotelli wrote:

What is the process to fix an issue? There's someone coordinating who is working on what?

Or just I take an issue from the list and If I can write a fix post this to inbox?

As a start point I will run the test cases and see if I can fix the failing... (Issue 409).

Regards, Gabriel _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

As a start point I will run the test cases and see if I can fix the failing... (Issue 409).

I would encourage anyone fixing an issue to first add a test case that exhibits the issue to the appropriate test class, and *then* see if you can fix the issue itself. Even if you can't fix the issue, *publish the test case*(s). This will allow someone else to move forward faster on fixing it. ../Dave