Is the missing debugger on your list? I have found 1.3 (speaking as a friend here) to be unusable over this. I get some work done with it, and then debuggers stop opening, rendering the image useless (AFAIK).
Bill ________________________________________ From: [email protected] [[email protected]] on behalf of Marcus Denker [[email protected]] Sent: Friday, February 24, 2012 2:57 AM To: An open mailing list to discuss any topics related to an open-source Smalltalk Subject: [Pharo-project] [Bug Tracker] Issues tagged 1.3 Hi, Just as another suggestion of something else to do to uselessly talk about what one would do if one could do... here is something that needs to be done: http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 Someone need to looks at each issue and as questions. - can this problem be repeated in the current last version of 1.3? - is this already fixed in 1.4? if yes -- is it so grave that the fix needs to be backported? - was it already a bug for the last 10 years and it did not hurt? -- Hint, hint: likely not important for fixing in 1.3 after it has been released. (yet, it could be. And if the fix is easy and clearly not breaking anything) - is there already a bug report about this issue on the tracker? (you have no idea how many reports are duplicated entries...) - What could be the reason for the problem? What could be a possible fix? -- Marcus Denker -- http://marcusdenker.de
