March 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] [Bug Tracker] fixed vs. fixedProposed...

by Marcus Denker

Hi, There was always the confusion of the meaning of "fixed", which actually had no clear meaning... I therefore added some weeks ago FixProposed --> this issue has a proposal of a fix, but there is no consensus that it's good FixToInclude ---> Please add to unstable ASAP This makes it clear what the status is. I now re-tagged all "fixed" issues as "FixProposed" and removed the "fixed" status. Next step: There are far too many items tagged "1.3". I think only a very select set of items should have that tag. -> FixToInclude -> Show stoppers ("If we release tomorrow, would this be a show stopper?") -> Failing tests -> Things people are actively working on. I will re-tag items... but I will turn off Email notification so that we don't get 130 mails. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 14, 2011

Re: [Pharo-project] Issue 953 in pharo: PackageInfo could be much faster

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #20 on issue 953 by marcus.d...(a)gmail.com: PackageInfo could be much faster http://code.google.com/p/pharo/issues/detail?id=953 (No comment was entered for this change.)

March 14, 2011

Re: [Pharo-project] Issue 1575 in pharo: optimize WeakKeyDictionary and subclasses for messagesends

by pharo＠googlecode.com

Updates: Status: Invalid Comment #3 on issue 1575 by marcus.d...(a)gmail.com: optimize WeakKeyDictionary and subclasses for messagesends http://code.google.com/p/pharo/issues/detail?id=1575 Weak* will be revisited soon. I close this.

March 14, 2011

Re: [Pharo-project] Issue 3817 in pharo: make Object >> error: deprecated

by pharo＠googlecode.com

Comment #5 on issue 3817 by stephane...(a)gmail.com: make Object >> error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 only :) and I'm sure that I fixed some of them already :). What would be good is to perform an analysis to see their usage.

March 14, 2011

Re: [Pharo-project] Issue 3606 in pharo: [1.1.2] [Failing Test] Undeclared in package shout

by pharo＠googlecode.com

Updates: Status: WontFix Comment #3 on issue 3606 by marcus.d...(a)gmail.com: [1.1.2] [Failing Test] Undeclared in package shout http://code.google.com/p/pharo/issues/detail?id=3606 1.1 is retired to the archives.

March 14, 2011

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.1.2-DevImage Milestone-1.2-DevImage Comment #10 on issue 3581 by marcus.d...(a)gmail.com: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 Problem in 1.2 (1.1 we don't care)

March 14, 2011

Re: [Pharo-project] Issue 3734 in pharo: Build of 1.1 Full is broken...

by pharo＠googlecode.com

Updates: Status: WontFix Comment #1 on issue 3734 by marcus.d...(a)gmail.com: Build of 1.1 Full is broken... http://code.google.com/p/pharo/issues/detail?id=3734 As 1.2 is the new stable, we do stop the builds of 1.1 on Hudson (1.1 is just in the archive, static).

March 14, 2011

Re: [Pharo-project] Issue 3815 in pharo: Filing in Class comments raises an error

by pharo＠googlecode.com

Comment #13 on issue 3815 by stephane...(a)gmail.com: Filing in Class comments raises an error http://code.google.com/p/pharo/issues/detail?id=3815 Henrik I think that this is clearly a showstopper for 1.2 and this will be just a patch on a huge patch. I prefer to keep my energy to rebuild something from scratch using ring

March 14, 2011

[Pharo-project] removing toolbuilder

by StÃ©phane Ducasse

Hi guys since the esug discussion and request to take action, I kept that issue in my mind. Now I think that we should remove toolbuilder since it serves a purpose we do not need right now (developing tools to new ui framworks,...platform). Now if somebody uses it I suggest to maintain it. Stef

March 14, 2011

Re: [Pharo-project] The current status of OSProcess

by Igor Stasenko

i added this to issue tracker :) On 14 March 2011 16:54, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > +1 > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Casimiro de Almeida Barreto [casimiro.barreto(a)gmail.com] > Sent: Monday, March 14, 2011 11:37 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] The current status of OSProcess > > +1 > > OSProcess important > FFI and/or "Alien running Ok in Linux and Windows" important > > CdAB > > Em 13-03-2011 06:46, StÃ©phane Ducasse escreveu: >> +1 >> >> OSProcess is really important for us. >> Like a good FFI >> >> Stef >> >> On Mar 13, 2011, at 1:11 AM, Igor Stasenko wrote: > > > > -- Best regards, Igor Stasenko AKA sig.

March 14, 2011