A pause... for tests and orthogonal concerns

hi guys

I was discussing with pavel and I like his point. I would like to do a kind of pause and fix the tests. Improve a bit the fact that we get more tests incrementally to avoid regression.
Tell what you think and think how you could help.

Stef
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Also pushing a bit the integration of the regression process with hudson or others.
I will have a look at the SUnit changes now for real (once the smalltalk-> SmalltalkImage is finished)

Stef

On Mar 15, 2010, at 12:05 AM, Stéphane Ducasse wrote:


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

I think this is a good idea! We have a lot of tests but we don't make use of them because we don't know which additional tests fail after an update, which would allow us to spot problems much faster.

Adrian

On Mar 15, 2010, at 07:29 , Stéphane Ducasse wrote:


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Stef,

There is a part of me that wants 1.1 tomorrow<g> to get Alien and full freedom to use underscores, among other things.  Briefly on $_, it came back up on squeak-dev, with the usual polarity and screams of doom due to poor aesthetics.  It is and IMHO always will be a consideration of external interfacing and avoiding name collisions.

Back on topic, tests are good thing.  As far as how I can help, a good starting point will be to clean up my image build process.  It appears to do a good job of identifying work that I have failed to package and saving the packages I have flagged as mine.  I wonder about possible problems with dependencies among packages, but can't say that I have had problems with that; for whatever reason, "cyclic dependencies" magage to terrorize every new Dolphin user at some point :)  I am unclear on whether Dolphin is too pedantic, Pharo is too relaxed (and somehow manages to "clean up the messes later"), or whether I am not pushing Pharo hard enough to have problems.

Regardless of the details above, I need to revise the load step of my build, and I have been hoping that Loader will appear so I can rewrite it once rather than twice.  I noticed mention today that SqueakSource was down (appears ok now).  Not meaning to complain about a free service, it hit me once before and I had to add complexity to my builds to work around it; I had thought about taking that out, but a local-only option appears important.  I am unclear on how to do that with Metacello - any ideas?

I was going to ask about Citezen and Metacello, but the SqueakSource wiki page shows instructions for it.  I will try to test it soon.

Bill





-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Stéphane Ducasse
Sent: Sunday, March 14, 2010 6:06 PM
To: Pharo Development
Subject: [Pharo-project] A pause... for tests and orthogonal concerns

hi guys

I was discussing with pavel and I like his point. I would like to do a kind of pause and fix the tests. Improve a bit the fact that we get more tests incrementally to avoid regression.
Tell what you think and think how you could help.

Stef
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Mar 15, 2010, at 2:09 PM, Schwab,Wilhelm K wrote:

> Stef,
>
> There is a part of me that wants 1.1 tomorrow<g> to get Alien and full freedom to use underscores, among other things.  Briefly on $_, it came back up on squeak-dev, with the usual polarity and screams of doom due to poor aesthetics.  It is and IMHO always will be a consideration of external interfacing and avoiding name collisions.

I scanned but did not read.
I think that Squeak should decide what is good for them.
For us
        _ is banned as :=
        _ can be in selector (not for readibility purposes :)) but for connection to stuff in C outside there :).


> Back on topic, tests are good thing.  As far as how I can help, a good starting point will be to clean up my image build process.  It appears to do a good job of identifying work that I have failed to package and saving the packages I have flagged as mine.  I wonder about possible problems with dependencies among packages, but can't say that I have had problems with that; for whatever reason, "cyclic dependencies" magage to terrorize every new Dolphin user at some point :)  I am unclear on whether Dolphin is too pedantic, Pharo is too relaxed (and somehow manages to "clean up the messes later"), or whether I am not pushing Pharo hard enough to have problems.

Yes we should improve also on the process (not integration) but development process.

> Regardless of the details above, I need to revise the load step of my build, and I have been hoping that Loader will appear so I can rewrite it once rather than twice.  I noticed mention today that SqueakSource was down (appears ok now).  Not meaning to complain about a free service, it hit me once before and I had to add complexity to my builds to work around it; I had thought about taking that out, but a local-only option appears important.  I am unclear on how to do that with Metacello - any ideas?

Since Gofer supports local and distant loading. It should not be a problem.
Ask in metacello ml. Dale is cool and responsive.

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project