I have a minor gripe about placeholder issues logged when a developer already has a fix ready - which lack any useful information regarding the problem that was solved. As an example, for Case 13112 [1] I found the problem was introduced in build 30205 by Case 10961, which is shown in the attached snapshot. First I'll say there was value that the issue was logged even as bare as that. I did manage to isolate a problem introduced by that slice, which was only observed 500 builds later. However providing limited information creates costs later on. The consequence in this case is relatively minor - the work-around is easy and probably all that is wanted during Pharo 3 beta anyhow. The background information will probably turn up. However having to stop and ask slows down the investigation. If I knew more upfront about the original problem of Case 10961, I could consider alternative solutions for that rather than just work-around the current issue. As I said, its only a minor thing, and hopefully this is useful feedback. Keep up the good work. cheers -ben [1] https://pharo.fogbugz.com/f/cases/13112/Broken-Vistary-theme
