Hi,
We should stat to get serious to evaluate the remaining issues that are tagged 2.0. http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D2.0 Which of the are true show stoppers? This means, is the issue of a severity that, just for this single issue, we can not release 2.0? By definition, all problems that are already in 1.4 do not qualify for this, as we did already release 1.4 and the world did not stop spinning. The same is for "nice to have" issues. "It would be nice if.." is not a show stopper. Marcus |
Hello.
Just want to notice issue http://code.google.com/p/pharo/issues/detail?id=6885 It about hanging image when it can not load fonts. If it will not fixed in 2.0 release I think many non latin users will have many bad words about pharo when they can't move their images on different computers. Images with loaded specific fonts can't start on computers which not have it (or placed in different directories). I was wait somebody with fonts knowledge look at this issue. I'm sure it is not difficult problem. Now when nobody solve it I will try fix it by myself. 2013/1/29 Marcus Denker <[hidden email]> Hi, |
On Jan 29, 2013, at 10:25 AM, Denis Kudriashov <[hidden email]> wrote: Hello. There are two solutions: 1) decide which issues are needed to be fixed and fixable, fix them and release 2) Do not decide, claim that "only a perfect release is a good release", and *never* release. Marcus
|
I uploaded fix to PharoInbox With it image not hangs and starts correctly. But existed loaded fonts are not valid in moved images because of saved absolute file path 2013/1/29 Marcus Denker <[hidden email]>
|
On Jan 29, 2013, at 7:16 PM, Denis Kudriashov <[hidden email]> wrote: I uploaded fix to PharoInbox With it image not hangs and starts correctly. But existed loaded fonts are not valid in moved images because of saved absolute file path Very good! Thanks.
|
In reply to this post by Denis Kudriashov
thanks
This is the best way to get the system better. Stef On Jan 29, 2013, at 3:16 PM, Denis Kudriashov wrote: > I uploaded fix to PharoInbox > With it image not hangs and starts correctly. > But existed loaded fonts are not valid in moved images because of saved absolute file path > > > 2013/1/29 Marcus Denker <[hidden email]> > > On Jan 29, 2013, at 10:25 AM, Denis Kudriashov <[hidden email]> wrote: > >> Hello. >> >> Just want to notice issue http://code.google.com/p/pharo/issues/detail?id=6885 >> It about hanging image when it can not load fonts. >> >> If it will not fixed in 2.0 release I think many non latin users will have many bad words about pharo when they can't move their images on different computers. Images with loaded specific fonts can't start on computers which not have it (or placed in different directories). >> >> I was wait somebody with fonts knowledge look at this issue. I'm sure it is not difficult problem. Now when nobody solve it I will try fix it by myself. > > There are two solutions: > > 1) decide which issues are needed to be fixed and fixable, fix them and release > 2) Do not decide, claim that "only a perfect release is a good release", and *never* release. > > Marcus > |
Free forum by Nabble | Edit this page |