- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Schwab,Wilhelm K

I've been grabbing and trying one-click images from Hudson for a while. They have worked on Ubuntu 9.10 and 10.04. My sampling is not exhaustive, but the Linux one-clicks seem to work. My current "project" (hopefully complete) is to eliminate my dependence on some hacks that I added to the vm. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Marcus Denker [marcus.denker(a)inria.fr] Sent: Tuesday, April 05, 2011 5:28 PM To: Pharo Development Subject: Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement On Apr 5, 2011, at 10:38 PM, Marcus Denker wrote: > > On Apr 5, 2011, at 10:28 PM, Adrian Lienhard wrote: > >> Thanks, Sven! >> >> I've put the page online >> - as a blog entry on the news page: http://www.pharo-project.org/news >> - the release page: http://www.pharo-project.org/pharo-download/release-1-2-1 >> >> (I've slightly edited some of the bullet point items to fit on one line) >> >> Thanks Laurent for the translation. I've linked to the wiki page you created. >> >> As far as I see there's one thing missing on the website: the download sticker for the one click image (top right on the page) still points to 1.1.1. I'll try to change the sticker and link tomorrow morning. >> >> Regarding the one click image, on the download page we linked to 1.1.1 with and without COG. Do we still have this distinction? >> > Yes. 1.2 is the last release with Cog / nonCog. > (we need to use and test using cog... e.g. hudson needs to use cog. This is planed for 1.3) > > Therefore, this is not correct: > > Pharo 1.2.1 One-Click is the easiest to get started: it includes all needed components (image, change and source file as well as a fast, compatible Cog VM) in one package that requires no installation > > the linked image does not use Cog. Dumb question: did we actually test the one-click on linux and win? On the mac it works, but the rest I did not test myself. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 5, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Stefan Marr

On 06 Apr 2011, at 00:01, Sven Van Caekenberghe wrote: > > On 05 Apr 2011, at 14:53, Camillo Bruni wrote: > >> Please read: http://portal.acm.org/citation.cfm?id=1297033 > > I would love to read this, but why should I have to pay for this ? > Research, especially when it is paid for with public money, should be free for all. http://lmgtfy.com/?q=Statistically+rigorous+java+performance+evaluation ... > Sven In case google is only my friend: http://itkovian.net/base/files/papers/oopsla2007-georges-preprint.pdf -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

April 5, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Sven Van Caekenberghe

On 05 Apr 2011, at 14:53, Camillo Bruni wrote: > Please read: http://portal.acm.org/citation.cfm?id=1297033 I would love to read this, but why should I have to pay for this ? Research, especially when it is paid for with public money, should be free for all. Sven

April 5, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Michael Haupt

Hi, On 5 April 2011 23:26, Stefan Marr <pharo(a)stefan-marr.de> wrote: > However, once you got your optimization into the VM your favorite build server should do its thing and that should include performance regression testing which is using a "slightly" more sophisticated approach than the described one. :-) this one is "ever so slightly" more sophisticated: "Wake up and smell the coffee: evaluation methodology for the 21st century" by Blackburn et al. - PDF available from http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.140.1635&rep=rep1&… Best, Michael

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Marcus Denker

On Apr 5, 2011, at 10:38 PM, Marcus Denker wrote: > > On Apr 5, 2011, at 10:28 PM, Adrian Lienhard wrote: > >> Thanks, Sven! >> >> I've put the page online >> - as a blog entry on the news page: http://www.pharo-project.org/news >> - the release page: http://www.pharo-project.org/pharo-download/release-1-2-1 >> >> (I've slightly edited some of the bullet point items to fit on one line) >> >> Thanks Laurent for the translation. I've linked to the wiki page you created. >> >> As far as I see there's one thing missing on the website: the download sticker for the one click image (top right on the page) still points to 1.1.1. I'll try to change the sticker and link tomorrow morning. >> >> Regarding the one click image, on the download page we linked to 1.1.1 with and without COG. Do we still have this distinction? >> > Yes. 1.2 is the last release with Cog / nonCog. > (we need to use and test using cog... e.g. hudson needs to use cog. This is planed for 1.3) > > Therefore, this is not correct: > > Pharo 1.2.1 One-Click is the easiest to get started: it includes all needed components (image, change and source file as well as a fast, compatible Cog VM) in one package that requires no installation > > the linked image does not use Cog. Dumb question: did we actually test the one-click on linux and win? On the mac it works, but the rest I did not test myself. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 5, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Stefan Marr

Hi: On 05 Apr 2011, at 21:27, Nicolas Cellier wrote: > But you probably have more ellaborated and well thought method :) I think we are talking here mostly about quick and dirty benchmarks to confirm intuitions. The provable best and most cost effective way to do it is: flip a coin (and that is serious, has the same or even better reliability and quality of result) If you think that is not good enough, well then the absolute minimum is something like this: - run your benchmark 5 times - 5 times with your optimization - 5 times without - look at the collected raw values i.e. measure runtime - and use your gut feeling to decide whether you have meaningful values and whether your time to do the optimization was well spent (don't eliminate outliers) If that is still to much to do, well, again, just flip a coin, and you have a high chance that the result of that are actually more reliable. (the approach above does not account for systematic errors...) However, once you got your optimization into the VM your favorite build server should do its thing and that should include performance regression testing which is using a "slightly" more sophisticated approach than the described one. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

April 5, 2011

Re: [Pharo-project] [Pharo-users] Last pending things for Pharo 1.2

by Casimiro de Almeida Barreto

Em 05-04-2011 18:05, Mariano Martinez Peck escreveu: > > > On Mon, Apr 4, 2011 at 5:19 PM, Marcus Denker <marcus.denker(a)inria.fr > <mailto:marcus.denker@inria.fr>> wrote: > > > On Apr 4, 2011, at 5:05 PM, Mariano Martinez Peck wrote: > >> >> >> On Sat, Mar 12, 2011 at 8:19 PM, Mariano Martinez Peck >> <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: >> >> So....here is the list of things I guess are pending: >> > > > In general, for all pending things adding entries in the bug > tracker is the only way ti make sure they are not forgotten. > >> 1) "Release" all configurations included in Pharo (this is, >> ConfigurationOfPharo and all it dependencies). I mean, we >> should NOT use or depend on #development versions. >> >> >> so...can someone check this is done? GUillermo and me did it >> once...but it seems a lot of stuff was updated once again > > I just gave up and took the image yesterday. Like you did for 1.1: > Just build it once, don't care that it is repeatable. > > > Sorry, I didn't understand. The Pharo 1.1 was repeatable (in the same > core) since all the Metacello versions were frozen. > > > >> >> >> 2) Update the one click image to use latest cog images and >> "pharo prepared vms". There are some issues regarding this... >> >> >> Marcus, which is the status of this one ? > > I updated the one-click image with the last cog VM. > > For the one-click, it is identical to 1.1 with the only change > that I put the windows VM I got from Torsten. > > > > But 1.1 was not-Cog (Cog 1.1.1 was cog). So...we are shipping the > Pharo One Click 1.2 with the Interpreter VM instead of Cog ? > or did you mean 1.1.1 ? if so, it would be good to update to latest > Cog. The cog version used for 1.1.1 had several problems (I think the > run:with:in: crashes the image -> TestCoverage) In linux (Fedora 14) when using diacritics '`~^", cog messes inputs (at least pt_BR) and fail to interpret properly keyboard entries (like Ã¡Ã©ÃÃ³ÃºÃ Ã£ÃµÃ¢Ãª, etc). Thus typing ' + a won't give Ã¡ but a? It's not a pharo problem but it's cog one. I suggest traditional vm is hold in use while cog don't address these input methods problem. > > >> >> >> 3) Write down all the things/summary done in Pharo 1.2 >> >> >> consider as done in nobody else comes with something better, >> >> >> 5) Update SystemVersion current -->> Pharo1.2rc2 of 27 >> January 2011 update 12340 >> >> >> >> SystemVersion current ->> Pharo1.2.1 of 2 April 2011 update 12345 >> >> so..it is ok, isn't it ? can we forget this item ? >> >> >> 6) Condense sources? condense changes? #cleanUpForRelease >> > >> Marcus, is that necessary ? >> >> DEVImageCreator >> cleanUps >> >> ScriptLoader new cleanUpForRelease. >> "In Pharo 1.1 condenseChanges is VERY slow because of the new >> method trailers. So condensingChanges each time even when it is >> not needed is not a good idea anymore. So in case a >> condenseChanges is needed it should be done explicitly. >> Smalltalk condenseChanges." >> Smalltalk garbageCollect. >> >> I did that and I put that comment. Now that they are faster and >> that we have Hudson, should I put back the Smalltalk >> condenseChanges ? is there anything else needed? do we need a >> condenseSources ? >> > > > CondenseChange and CondenseSource is broken right now. > > > Ok, we can live withoput that :) > > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > <http://www.marcusdenker.de/> > INRIA Lille -- Nord Europe. Team RMoD. > > > > > -- > Mariano > http://marianopeck.wordpress.com >

April 5, 2011

Re: [Pharo-project] [Pharo-users] Last pending things for Pharo 1.2

by Marcus Denker

On Apr 5, 2011, at 11:06 PM, Mariano Martinez Peck wrote: > > I just gave up and took the image yesterday. Like you did for 1.1: Just build it once, don't care that it is repeatable. > > Sorry, I didn't understand. The Pharo 1.1 was repeatable (in the same core) since all the Metacello versions were frozen. > In 1.2 seemingly not, it changes by the phase of the moon what is loaded. Yes... someone needs to look at that. Somone needed to look at that for months. At the same time, 1.3 does not even had a build *ever*. > >> >> 2) Update the one click image to use latest cog images and "pharo prepared vms". There are some issues regarding this... >> > >> Marcus, which is the status of this one ? > > I updated the one-click image with the last cog VM. > > For the one-click, it is identical to 1.1 with the only change that I put the windows VM I got from Torsten. > > > But 1.1 was not-Cog (Cog 1.1.1 was cog). So...we are shipping the Pharo One Click 1.2 with the Interpreter VM instead of Cog ? > or did you mean 1.1.1 ? if so, it would be good to update to latest Cog. The cog version used for 1.1.1 had several problems (I think the run:with:in: crashes the image -> TestCoverage) > I updated the cog One-Click to the latest Cog vm released last week. Yes, we need to have everthing build by Hudson automatically... but on the other hand, we need to release and not postpone forever. We had 3 Months to fix everything, we did not, we would not fix in another 3 months. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 5, 2011

Re: [Pharo-project] [Pharo-users] Last pending things for Pharo 1.2

by Mariano Martinez Peck

On Mon, Apr 4, 2011 at 5:19 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Apr 4, 2011, at 5:05 PM, Mariano Martinez Peck wrote: > > > > On Sat, Mar 12, 2011 at 8:19 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> So....here is the list of things I guess are pending: >> >> > > In general, for all pending things adding entries in the bug tracker is the > only way ti make sure they are not forgotten. > > 1) "Release" all configurations included in Pharo (this is, >> ConfigurationOfPharo and all it dependencies). I mean, we should NOT use or >> depend on #development versions. >> > > so...can someone check this is done? GUillermo and me did it once...but it > seems a lot of stuff was updated once again > > > I just gave up and took the image yesterday. Like you did for 1.1: Just > build it once, don't care that it is repeatable. > Sorry, I didn't understand. The Pharo 1.1 was repeatable (in the same core) since all the Metacello versions were frozen. > > > >> 2) Update the one click image to use latest cog images and "pharo prepared >> vms". There are some issues regarding this... >> > > Marcus, which is the status of this one ? > > > I updated the one-click image with the last cog VM. > > For the one-click, it is identical to 1.1 with the only change that I put > the windows VM I got from Torsten. > But 1.1 was not-Cog (Cog 1.1.1 was cog). So...we are shipping the Pharo One Click 1.2 with the Interpreter VM instead of Cog ? or did you mean 1.1.1 ? if so, it would be good to update to latest Cog. The cog version used for 1.1.1 had several problems (I think the run:with:in: crashes the image -> TestCoverage) > > >> 3) Write down all the things/summary done in Pharo 1.2 >> > > consider as done in nobody else comes with something better, > > >> 5) Update SystemVersion current -->> Pharo1.2rc2 of 27 January 2011 >> update 12340 >> > > > SystemVersion current ->> Pharo1.2.1 of 2 April 2011 update 12345 > > so..it is ok, isn't it ? can we forget this item ? > > >> 6) Condense sources? condense changes? #cleanUpForRelease >> >> > Marcus, is that necessary ? > > DEVImageCreator >> cleanUps > > ScriptLoader new cleanUpForRelease. > "In Pharo 1.1 condenseChanges is VERY slow because of the new method > trailers. So condensingChanges each time even when it is not needed is not a > good idea anymore. So in case a condenseChanges is needed it should be done > explicitly. > Smalltalk condenseChanges." > Smalltalk garbageCollect. > > I did that and I put that comment. Now that they are faster and that we > have Hudson, should I put back the Smalltalk condenseChanges ? is there > anything else needed? do we need a condenseSources ? > > > > CondenseChange and CondenseSource is broken right now. > > Ok, we can live withoput that :) > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- Mariano http://marianopeck.wordpress.com

April 5, 2011

Re: [Pharo-project] Issue 3831 in pharo: 1.2 full image workspace has description on how to load O2

by pharo＠googlecode.com

Comment #6 on issue 3831 by marianopeck: 1.2 full image workspace has description on how to load O2 http://code.google.com/p/pharo/issues/detail?id=3831 sorry I meant in version12beta2:

April 5, 2011