23 Jan
2013
23 Jan
'13
7:37 a.m.
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."
23 Jan
23 Jan
9:39 a.m.
On 01/23/2013 07:37 AM, Tudor Girba wrote:
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.
yes!
this will be a good thing as there are good things in pharo 2.0
nicolas
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
--
Nicolas Anquetil -- RMod research team (Inria)
4:37 p.m.
Nicolas Anquetil wrote:
On 01/23/2013 07:37 AM, Tudor Girba wrote:
I think that separating releases for new features and under-the-hood
changes is a good thing.
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.
yes!
this will be a good thing as there are good things in pharo 2.0
nicolas
> Cheers 
8:50 p.m.
+1
Alexandre
On Jan 23, 2013, at 3:39 AM, Nicolas Anquetil <Nicolas.Anquetil(a)inria.fr> wrote:
On 01/23/2013 07:37 AM, Tudor Girba wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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.
yes!
this will be a good thing as there are good things in pharo 2.0
nicolas
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
--
Nicolas Anquetil -- RMod research team (Inria)
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 
24 Jan
24 Jan
2:04 a.m.
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
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
7:44 a.m.
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 :).
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."
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
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
3:45 p.m.
Apparently I should enhance
readableFileNames
readableFileNames
| all cached new |
all := self allFileNames. "from repository"
cached := self cachedFileNames. "in memory"
new := all difference: cached.
^ (cached asArray, new)
select: [:ea | self canReadFileNamed: ea]
so remove shitty and broken file I will hack something for now.
On Jan 24, 2013, at 11:25 AM, Stéphane Ducasse wrote:
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:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 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
6:57 p.m.
doru I submitted a new slice for the problem.
It should fix the problem can you check?
On Jan 24, 2013, at 11:45 AM, Stéphane Ducasse wrote:
Apparently I should enhance
readableFileNames
readableFileNames
| all cached new |
all := self allFileNames. "from repository"
cached := self cachedFileNames. "in memory"
new := all difference: cached.
^ (cached asArray, new)
select: [:ea | self canReadFileNamed: ea]
so remove shitty and broken file I will hack something for now.
On Jan 24, 2013, at 11:25 AM, Stéphane Ducasse wrote:
On Jan 24, 2013, at 3:44 AM, Tudor Girba wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 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:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 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
> 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
--
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
4350
days inactive
4351
days old
8 comments
5 participants
participants (5)
-
Alexandre Bergel -
Ben Coman -
Nicolas Anquetil -
Stéphane Ducasse -
Tudor Girba