In general start with the more recent fix.
What have to be done:
- verify that the issue is still an issue
- check that we know how to reproduce it.
- possibly write a test to cover the case.
- start to see ....
stef
>>
>>
>> I try to solve some issue in the issues tracker from time to time, but
>> it's often difficult
>> when outside your expertise. So doing it with others might definitively help.
>>
>>
>> Fix of the day contest has the advantage of being compatible with every
>> people timezone / agenda.
>>
>> We can also synchronize CODTC and FOTDC in order to comment classes related
>> to the fix.
>>
>> Now we just need someone to lead the FOTDC. I already do COTDC so is there a
>> good soul ?
>>
>>
>> well, I've started by renaming the thread and attaching Pharo-users.
>>
>> Laurent, maybe you should clarify what "lead" exactly means.
>>
>>
>> Everyday:
>> - choose an issue for the contest
>> - write it to the mailing list
>> - push to ask help
>> - contest is done when a slice is put in inbox
>>
>>
>> Indeed, much like COTDC is.
>>
>> Laurent.
>
> That would be awesome! I was looking at the bug tracker
> (http://code.google.com/p/pharo/issues/list#) yesterday to see if there were
> things that I could help with...but even when looking at "open" issues, many
> of them are several years old, and have a state of "Accepted." So as someone
> not actively involved in pharo development, I have absolutely no clue what
> actually needs to be fixed.
>
> I'd like to help, the bug tracker doesn't give me much guidance (or at least
> I'd benefit from an explanation of how it's structured), and so guidance from
> someone who's active would be really helpful.
>
> Pat
