On Mon, Jan 31, 2011 at 8:45 AM, Marcus Denker <marcus.denker@inria.fr>wrote:
On Jan 30, 2011, at 10:47 PM, Stéphane Ducasse wrote:
republished. Now waiting for hudson to see.
I like automatic builds and tests!
I think it brings an improvement equal (or even larger) then using bug-tracking vs. not using it.
And if now somebody says: "Everyone uses a bug tracker": No, Squeak did not for many, many years. And when it did, not many people looked at it... amazing now in retrospect.
We will say the same about continuous integration soon, especially when it encompasses everything: VM build from source, *that* vm used to run tests, the resulting image and vm used to build the artefact people download automatically, every time a commit happens.
And that for all supported plattforms, of course.
CI is a big step forward. I can download last built and work instantaneously on the current failing tests. As a free-time contributor this is a HUGE gain of time. It seems the current bottleneck in the process is patch integration on external packages (like OB). May be we can have a PharoPatchQueue repository so we can integrate patch that have passed QA but still not integrated in external packages. Then I hope we'll see Lint Checks, list of non-commented classes, test coverage, automatic API doc :) Laurent.
Marcus I published the other sounds fixes in the sound packages. Now I do not know how the dev image is specified. May be the script should be changed to load the new packages versions I published. Do you know where is this script?
It uses the ConfigurationOfPharo
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load.
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.