On Mon, May 4, 2015 at 8:27 AM, Sergio Fedi <[email protected]> wrote:
> @Cyril > I tried to do what you suggested, but the amount of cases to resolve is > huge, I'm quite lost on where to begin, and most of them I don't understand > how to solve them > > @Ben > Which ones do you suggest I should begin reviewing? > Any and all that turn up under the "Fixed To review" filter on Fogbugz, from the pull down menu on the <Cases> buttons. > How do I do that reviewing you suggest? > > 1. From the issue description, reproduce the original problem. If there is not sufficient information to do that, ask for clarificationon the issue. Sometimes the person who logs the issue already has a fix and so the desciption to reproduce is limited, but its good to pin down for historical purposes (I've hit some opaque ones tracking down introduced regressions before) 2. Filter on the Pharo5Inbox for the issue number then <Merge> the slice. 3. Report your opinion on the issue being fixed, or other problems introduced. 4. Over time as you feel comfortable, comment on the source code quality/conventions/etc... cheers -ben
