For Work Needed cases, there should be a description of the problem sufficient for you the reproduce it. If not, ask for one. Try to locate which build version introduced the bug. I use PharoLauncher to help download and manage a large number of Image versions while manually bisecting versions like git bisect. Once determined, check the build announcements on pharo-dev for which slices were loaded to go from good image version to bad image version. For Resolved cases, there should be a description of the problem sufficient for you the reproduce it, then apply the fix and repeat the actions to confirm its fixed. If not, ask for one. I find I learn a lot by reviewing the fixes of others. I tend to do <Changes> first, then leave that open while I do a <Merge>. This makes it easier to go the the changed methods and scatter a few 'self halt's so that I can trace the running code. Sometimes in a separate Image I put the same 'self halt's in the original methods and step through both new and old simultaneously. cheers -ben On Thu, Jan 22, 2015 at 11:13 PM, Paul DeBruicker <pdebruic@gmail.com> wrote:

Go here

https://pharo.fogbugz.com/

and follow the instructions to make an account.

Then start with the issues that are tagged 'Work Needed' or 'Resolved (Fix Review Needed)'

nacho wrote

...

I would like to contribute. How can I help. How one contributes to fogbuzz? thanks Nacho

-- View this message in context: http://forum.world.st/More-people-needed-to-review-issues-tp4800916p4801006.... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.