http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.4 - All issues "FixReviewNeeded" needs to be looked at and reviewed. Does it fix the bug (or for an improvement: is this good? Do you want it in the release? - All issues "NoSourcesAvailable" do have fixes, but described in wonderful prose. ("change the third character of the second line.." (nearly...). The idea here is that it's far far far far easier to look at things that one can just load in the system as opposed to solve a textual riddle first. yes, it's trivial... but it's amazing how the triviality between "machine readable code" and "textual description for a human to parse" changes how long an issue is not looked at. Marcus -- Marcus Denker -- http://marcusdenker.de