- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] Last pending things for Pharo 1.2
by Marcus Denker April 5, 2011

April 5, 2011

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. > > 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. > > 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. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

Re: [Pharo-project] [Pharo-users] Last pending things for Pharo 1.2
by Marcus Denker April 5, 2011

April 5, 2011

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.

1 0

[Pharo-project] Issue 3831 in pharo: 1.2 full image workspace has description on how to load O2
by pharo＠googlecode.com April 5, 2011

April 5, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3831 by marcus.d...(a)gmail.com: 1.2 full image workspace has description on how to load O2 http://code.google.com/p/pharo/issues/detail?id=3831 ... but O2 does not work in 1.2 So we should remove the description.

1 6

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement
by Marcus Denker April 5, 2011

April 5, 2011

On Apr 5, 2011, at 10:21 PM, Casimiro de Almeida Barreto wrote: > I suggest some corrections at: "DEVImageWorkspaces > openExternalProjectWorkspace". > > O2 does not install according to instructions and installing it other > ways result in error. > Aida has pending dependencies (Swazoo, I guess because Seaside installs > Swazoo2) > etc. > I removed the O2 description!!!!! I removed it, waited for Hudson to build the release, downloaded, checked, and it was gone. There is even a tracker entry: http://code.google.com/p/pharo/issues/detail?id=3831 So now why in the world is it there now? I think we should really find someone else for managing the Full image build scripts. I am definitly to dumb to get anything to work. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Actions done in 1.3
by StÃ©phane Ducasse April 5, 2011

April 5, 2011

Hi guys to help us in the future I started http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotThree The list starts to get long... Stef

1 0

[Pharo-project] Let's get rid of Core vs. Full
by Marcus Denker April 5, 2011

April 5, 2011

Hi, So finally I have to admit that I am defeated: The way we do the Core vs. Full release does not work. 1) We don't develop the system using the tools that we tell people to use. -> bugs don't get fixed -> there is no pressure on improving the tools -> we can't use the advanced tools while developing the Core. 2) We integrate *far* too late. -> merging in the tools of Dev a week before the big release *will* fail, as they are not tested. 3) As we use Core for Development of Core, it's not a Core. It contains all needed tools, just simplified versions. -> People even expect to be able to shrink it more, which in turn we do not test. 4) Refactoring are only applied to the Core, not to the whole code base. Look at the Sound or Morph Examples... getting them fixed for the release if they are not touched for a year is nearly impossible. 5) Fixing something in the Core is fast. We move *extremely* fast. Getting something fixed for Full can be very difficult. e.g. repositories need to be changed (for a temporary fork), build scripts edited.. it's so hard that it is done far too late. 6) We can not do a release and be done. Release drag over weeks, making announcments (and publicity) impossible. The build server helps a little bitwith some of the problems, but not much... especially as the full build of unstable is mostly not working. So I vote for abandoning Core vs. Dev for 1.3. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

10 19

[Pharo-project] [COTDC] 40#2 - NonReentrantWeakMessageSend
by laurent laffont April 5, 2011

April 5, 2011

Today: NonReentrantWeakMessageSend (ExclusiveWeakMessageSend aborted - no answer) Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

3 3

[Pharo-project] Status of Weak enhancements in Pharo
by Miguel CobÃ¡ April 5, 2011

April 5, 2011

What is the status of the Weak enhancements that were applied to Squeak 4.2 (by Levente and Igor, mainly) and were targeted for inclusion in Pharo? Is there a list of them somewhere? which ones are integrated and which ones are not yet? Other question, is the plan to take the enhancements as they are and apply them on Pharo, that is, the versions in Squeak are the reference or there are conflicting versions in Pharo that are to be keep instead. I remember that some changes were made to Pharo in this regard. Cheers -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

2 2

[Pharo-project] syntax highlighting for (stateful) traits (non-local methods)
by Toon Verwaest April 5, 2011

April 5, 2011

Hi all, as you know I'm working on stateful traits using my new classbuilder etc... Now I noticed that methods are highlighted always inside of the context of the class that's active in the class browser. How can I change this? There is already a useful method around to figure out which object it belongs to: SomeClass traitOrClassOfSelector: #aMethod This actually will tell me which trait it comes from. So now I could apply syntax coloring in the context of the trait rather than the class. Since in my implementation state is all private to the trait / class, they should be able to access their own state but not see the state of the other class. This obviously also means that coloring should happen in the correct scope, rather than always in the scope of the class. At the moment the coloring doesn't really make sense ... but then it didn't really matter that much until now. Although if you try to access state in a method coming from a trait, while coding in your IDE you'll probably have the impression you can access your local instvars. I don't really know what the semantics are there... but it seems a bit broken :) cheers, Toon

3 33

Re: [Pharo-project] Issue 3105 in pharo: DeepCopier warnIverNotCopiedIn:sel: dependent on ToolSet
by pharo＠googlecode.com April 5, 2011

April 5, 2011

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #1 on issue 3105 by marcus.d...(a)gmail.com: DeepCopier warnIverNotCopiedIn:sel: dependent on ToolSet http://code.google.com/p/pharo/issues/detail?id=3105 fix attached Attachments: KernelCleanDeepCopier.1.cs 713 bytes

1 2