Hi Marcus, Thanks for replying to my suggestion. I am a relative newbie to Pharo, i.e. I did not use it much so far. Therefore, I am sure missing some obvious things.
See further comments below. Cheers, Bernhard Am 26.10.2011 um 08:54 schrieb Marcus Denker: > On Oct 25, 2011, at 8:24 PM, Bernhard Pieber wrote: >> May I humbly suggest to at least add a link to known open issues for 1.3 >> right next to the release download? Then at least a newbie knows what to >> expect. > There is nothing different with 1.3 than with any other release we did. I am not sure I understand what you are trying to tell me. I hope you don't get the impression that I am criticizing you. That is the last thing I want, because you are one of those putting the most effort into Pharo! Thanks for that! > And the discussion was more about unknown bugs, not known ones. "You can not > release because maybe I found a bug > yesterday that I have not yet reported". > > To make is clear: there are 7 (seven) open issues tagged for 1.3: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 > Most of which are not even show stoppers (are already a bug in 1.2, just > cosmetic...) > None is important enough to have seen any work done since the last sprint. What I always wanted to ask and did not dare until now: What is the meaning of a 1.3 tag? It *could* mean the following: a) Those are the issues that are show stoppers before a release can be done. b) Those are known issues in 1.3. c) ... At first I thought it meant a). When you removed the "release candidate" status from the 1.3 download page I started to doubt this. ;-) My next assumption was it meant b). Hence my humble suggestion. Now it seems it must mean something completely different. > In a way of course many reports on the issue tracker are describing an > improvement or problem that could > be related to 1.3: > > http://code.google.com/p/pharo/issues/list > > These are 421 issues.
