24 Jan
2013
24 Jan
'13
3:25 p.m.
On Jan 24, 2013, at 3:44 AM, Tudor Girba wrote:
Hi Stef,
Thanks a lot for looking into this.
I do not need to look at the file by hand. It's just that Monticello crashes when I
try to build the image because of the problem :).
Can you show me how it crashes. Because I only fixed the refresh code in the Monticello
inspector but it means that we will have the same
problem somewhere else and I can fix it.
Stef
Cheers,
Doru
On Jan 24, 2013, at 2:04 AM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote:
Doru
why the bug in PharoTaskForces is a problem (which I solved by the way - look at 7311)
and try it on 1.4. I did it for 2.0.
I do not see why you need to look at file by hand in the pharo taskforces to release
moose.
Stef
--
www.tudorgirba.com
"When people care, great things can happen."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi,
There is not much point in postponing the release of 4.7. As soon as we solve the
squeaksource problem of PharoTaskForces, I will release it.
The next step is to move to Pharo 2.0, move all code to SmalltlakHub, and reorganize the
configurations in the process. And, as soon as Pharo 2.0 gets released, I would like to
release another Moose version even if it only contains minor changes.
Cheers,
Doru
--
www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev