13 Jun
2008
13 Jun
'08
2:47 p.m.
Hi guys
I checked and found that
AbstractImporter>>errorLog: is deprecated.... ok fair
Now there are at least 4 methods that invoke this method and are not
deprecated.
So what do we do?
How do we log error in moose?
We don't?
Stef
13 Jun
13 Jun
3:01 p.m.
I do remember this was discussed once along time ago. Dont we have
some bugzilla type solution?
If not we should introduce something here...
Cheers
Orla
On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
Hi guys
I checked and found that
AbstractImporter>>errorLog: is deprecated.... ok fair
Now there are at least 4 methods that invoke this method and are not
deprecated.
So what do we do?
How do we log error in moose?
We don't?
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3:02 p.m.
Yes but deprecating a method but not fixing its callers does not help
Now I'm stuck. I do not know how to report errors in moose, there is
broken code in Moose on VW
and on squeak this is not working either.
I think that nobody cares about moose expect doru and we feel it.
Sad end for Moose. So I will certainly take over but what a pity.
Stef
On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
I do remember this was discussed once along time ago.
Dont we have
some bugzilla type solution?
If not we should introduce something here...
Cheers
Orla
On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
Hi guys
I checked and found that
AbstractImporter>>errorLog: is deprecated.... ok fair
Now there are at least 4 methods that invoke this method and are not
deprecated.
So what do we do?
How do we log error in moose?
We don't?
Stef
_______________________________________________
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:08 p.m.
Stef,
if you send 30+ e-Mails in less than a day and nobody replies please
do not wonder, and no it's not a sign that moose is dying or only
Doru cares. At least in Lugano we're fully behind it, but we have a
double deadline in the next couple of days for a total of 5 papers,
you can imagine that we currently have other priorities. To not even
mention the usual stuff like exams, sunny weather after 6 weeks of
rain, the European championship, and another couple of things like
breathing, eating and the European championship. BTW, the European
championship: Doru, you what time it is.. ;-)
Best,
Michele
On Jun 13, 2008, at 15:02 , Stéphane Ducasse wrote:
Yes but deprecating a method but not fixing its
callers does not help
Now I'm stuck. I do not know how to report errors in moose, there is
broken code in Moose on VW
and on squeak this is not working either.
I think that nobody cares about moose expect doru and we feel it.
Sad end for Moose. So I will certainly take over but what a pity.
Stef
On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
I do remember this was discussed once along time
ago. Dont we have
some bugzilla type solution?
If not we should introduce something here...
Cheers
Orla
On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi guys
I checked and found that
AbstractImporter>>errorLog: is deprecated.... ok fair
Now there are at least 4 methods that invoke this method and are not
deprecated.
So what do we do?
How do we log error in moose?
We don't?
Stef
_______________________________________________
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:18 p.m.
Michele I can understand and sure this is certainly me that is wrong,
of course.
Stef,
if you send 30+ e-Mails in less than a day and nobody replies please
do not wonder, and no it's not a sign that moose is dying or only
Doru cares. At least in Lugano we're fully behind it,
good to know.
but we have a
double deadline in the next couple of days for a total of 5 papers,
you can imagine that we currently have other priorities. To not even
mention the usual stuff like exams, sunny weather after 6 weeks of
rain, the European championship, and another couple of things like
breathing, eating and the European championship. BTW, the European
championship: Doru, you what time it is.. ;-)
I heard on the radio rums in italy saying that they hope italy will
win else
they will be in bad situation. Strange feeling.
Stef
Best,
Michele
On Jun 13, 2008, at 15:02 , Stéphane Ducasse wrote:
Yes but deprecating a method but not fixing its
callers does not help
Now I'm stuck. I do not know how to report errors in moose, there is
broken code in Moose on VW
and on squeak this is not working either.
I think that nobody cares about moose expect doru and we feel it.
Sad end for Moose. So I will certainly take over but what a pity.
Stef
On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I do remember this was discussed once along time
ago. Dont we have
some bugzilla type solution?
If not we should introduce something here...
Cheers
Orla
On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi guys
I checked and found that
AbstractImporter>>errorLog: is deprecated.... ok fair
Now there are at least 4 methods that invoke this method and are
not
deprecated.
So what do we do?
How do we log error in moose?
We don't?
Stef
_______________________________________________
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:21 p.m.
We need a tool to report errors centrally for each version of Moose -
one place for Squeak Moose and one place for VW Moose.
I agree that the deprecation of a method without fixing the callers is
a problem.
Doru is at the football match today so that explains why you are not
getting immediate response. But the whole of moose should not rely on
Doru otherwise it will die sooner or later.
We could set up a bugzilla. What do you think?
Cheers
Orla
On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote:
Yes but deprecating a method but not fixing its
callers does not help
Now I'm stuck. I do not know how to report errors in moose, there is
broken code in Moose on VW
and on squeak this is not working either.
I think that nobody cares about moose expect doru and we feel it.
Sad end for Moose. So I will certainly take over but what a pity.
Stef
On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
I do remember this was discussed once along time
ago. Dont we have
some bugzilla type solution?
If not we should introduce something here...
Cheers
Orla
On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi guys
I checked and found that
AbstractImporter>>errorLog: is deprecated.... ok fair
Now there are at least 4 methods that invoke this method and are not
deprecated.
So what do we do?
How do we log error in moose?
We don't?
Stef
_______________________________________________
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:22 p.m.
Orla
this is not the problem. I will fix the error reporting and remove the
deprecation.
Apparently I could not get the message that error reporting is a nice
feature of an environment (you know a little
console) but apparently this is not useful.
Now my point is different. From what I see: everybody is perfectly
happy with moose
as it is, and migrating to Squeak + changing Famix + changing from
Meta to Fame does not seem to be a problem
to anybody so perfect.
We need a tool to report errors centrally for each
version of Moose -
one place for Squeak Moose and one place for VW Moose.
I agree that the deprecation of a method without fixing the callers is
a problem.
Doru is at the football match today so that explains why you are not
getting immediate response.
Sure there is no problem I was aware of that :)
Now still this is a good test because in couple of month they may be
roumanian football matches
everyday.
But the whole of moose should not rely on
Doru otherwise it will die sooner or later.
We could set up a bugzilla. What do you think?
Cheers
Orla
On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote:
Yes but deprecating a method but not fixing its
callers does not help
Now I'm stuck. I do not know how to report errors in moose, there is
broken code in Moose on VW
and on squeak this is not working either.
I think that nobody cares about moose expect doru and we feel it.
Sad end for Moose. So I will certainly take over but what a pity.
Stef
On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I do remember this was discussed once along time
ago. Dont we have
some bugzilla type solution?
If not we should introduce something here...
Cheers
Orla
On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi guys
I checked and found that
AbstractImporter>>errorLog: is deprecated.... ok fair
Now there are at least 4 methods that invoke this method and are
not
deprecated.
So what do we do?
How do we log error in moose?
We don't?
Stef
_______________________________________________
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:41 p.m.
Yes, but wouldn't it be good to have a bug tracking system and anytime
someone has time they could take a bug off the stack and fix it,
Some people are more involved with some packages than others so it
would be good to know this as well.
Of course I don't have the overview anymore of what is happening in
moose as I havent done much general moose coding just dynamoose and a
few other small bits and pieces. So I guess this doesn't give me too
much of a say in moose.
Orla
On Jun 13, 2008, at 3:22 PM, Stéphane Ducasse wrote:
Orla
this is not the problem. I will fix the error reporting and remove the
deprecation.
Apparently I could not get the message that error reporting is a nice
feature of an environment (you know a little
console) but apparently this is not useful.
Now my point is different. From what I see: everybody is perfectly
happy with moose
as it is, and migrating to Squeak + changing Famix + changing from
Meta to Fame does not seem to be a problem
to anybody so perfect.
We need a tool to report errors centrally for
each version of Moose -
one place for Squeak Moose and one place for VW Moose.
I agree that the deprecation of a method without fixing the callers
is
a problem.
Doru is at the football match today so that explains why you are not
getting immediate response.
Sure there is no problem I was aware of that :)
Now still this is a good test because in couple of month they may be
roumanian football matches
everyday.
But the whole of moose should not rely on
Doru otherwise it will die sooner or later.
We could set up a bugzilla. What do you think?
Cheers
Orla
On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes but deprecating a method but not fixing its
callers does not
help
Now I'm stuck. I do not know how to report errors in moose, there is
broken code in Moose on VW
and on squeak this is not working either.
I think that nobody cares about moose expect doru and we feel it.
Sad end for Moose. So I will certainly take over but what a pity.
Stef
On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I do remember this was discussed once along time
ago. Dont we have
some bugzilla type solution?
If not we should introduce something here...
Cheers
Orla
On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
> Hi guys
>
> I checked and found that
>
> AbstractImporter>>errorLog: is deprecated.... ok fair
>
> Now there are at least 4 methods that invoke this method and are
> not
> deprecated.
> So what do we do?
>
> How do we log error in moose?
> We don't?
>
> Stef
> _______________________________________________
> 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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
4:51 p.m.
Yes may be we should open a google code account for moose.
Stef
On Jun 13, 2008, at 3:41 PM, Orla Greevy wrote:
Yes, but wouldn't it be good to have a bug tracking system and anytime
someone has time they could take a bug off the stack and fix it,
Some people are more involved with some packages than others so it
would be good to know this as well.
Of course I don't have the overview anymore of what is happening in
moose as I havent done much general moose coding just dynamoose and a
few other small bits and pieces. So I guess this doesn't give me too
much of a say in moose.
Orla
On Jun 13, 2008, at 3:22 PM, Stéphane Ducasse wrote:
Orla
this is not the problem. I will fix the error reporting and remove
the
deprecation.
Apparently I could not get the message that error reporting is a nice
feature of an environment (you know a little
console) but apparently this is not useful.
Now my point is different. From what I see: everybody is perfectly
happy with moose
as it is, and migrating to Squeak + changing Famix + changing from
Meta to Fame does not seem to be a problem
to anybody so perfect.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
We need a tool to report errors centrally for
each version of
Moose -
one place for Squeak Moose and one place for VW Moose.
I agree that the deprecation of a method without fixing the callers
is
a problem.
Doru is at the football match today so that explains why you are not
getting immediate response.
Sure there is no problem I was aware of that :)
Now still this is a good test because in couple of month they may be
roumanian football matches
everyday.
But the whole of moose should not rely on
Doru otherwise it will die sooner or later.
We could set up a bugzilla. What do you think?
Cheers
Orla
On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes but deprecating a method but not fixing its
callers does not
help
Now I'm stuck. I do not know how to report errors in moose, there
is
broken code in Moose on VW
and on squeak this is not working either.
I think that nobody cares about moose expect doru and we feel it.
Sad end for Moose. So I will certainly take over but what a pity.
Stef
On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
> I do remember this was discussed once along time ago. Dont we have
> some bugzilla type solution?
>
> If not we should introduce something here...
>
> Cheers
> Orla
>
>
>
>
> On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
>
>> Hi guys
>>
>> I checked and found that
>>
>> AbstractImporter>>errorLog: is deprecated.... ok fair
>>
>> Now there are at least 4 methods that invoke this method and are
>> not
>> deprecated.
>> So what do we do?
>>
>> How do we log error in moose?
>> We don't?
>>
>> Stef
>> _______________________________________________
>> 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
>
_______________________________________________
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
5:08 p.m.
Ok I will do this :-)
Just spoke with Lukas and Google code sounds like a good solution :-)
CU
Orla
On Jun 13, 2008, at 4:51 PM, Stéphane Ducasse wrote:
Yes may be we should open a google code account for
moose.
Stef
On Jun 13, 2008, at 3:41 PM, Orla Greevy wrote:
Yes, but wouldn't it be good to have a bug tracking system and
anytime
someone has time they could take a bug off the stack and fix it,
Some people are more involved with some packages than others so it
would be good to know this as well.
Of course I don't have the overview anymore of what is happening in
moose as I havent done much general moose coding just dynamoose and a
few other small bits and pieces. So I guess this doesn't give me too
much of a say in moose.
Orla
On Jun 13, 2008, at 3:22 PM, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Orla
this is not the problem. I will fix the error reporting and remove
the
deprecation.
Apparently I could not get the message that error reporting is a
nice
feature of an environment (you know a little
console) but apparently this is not useful.
Now my point is different. From what I see: everybody is perfectly
happy with moose
as it is, and migrating to Squeak + changing Famix + changing from
Meta to Fame does not seem to be a problem
to anybody so perfect.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
We need a tool to report errors centrally for
each version of
Moose -
one place for Squeak Moose and one place for VW Moose.
I agree that the deprecation of a method without fixing the callers
is
a problem.
Doru is at the football match today so that explains why you are
not
getting immediate response.
Sure there is no problem I was aware of that :)
Now still this is a good test because in couple of month they may be
roumanian football matches
everyday.
But the whole of moose should not rely on
Doru otherwise it will die sooner or later.
We could set up a bugzilla. What do you think?
Cheers
Orla
On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote:
> Yes but deprecating a method but not fixing its callers does not
> help
> Now I'm stuck. I do not know how to report errors in moose, there
> is
> broken code in Moose on VW
> and on squeak this is not working either.
>
> I think that nobody cares about moose expect doru and we feel it.
> Sad end for Moose. So I will certainly take over but what a pity.
>
> Stef
>
> On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
>
>> I do remember this was discussed once along time ago. Dont we
>> have
>> some bugzilla type solution?
>>
>> If not we should introduce something here...
>>
>> Cheers
>> Orla
>>
>>
>>
>>
>> On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
>>
>>> Hi guys
>>>
>>> I checked and found that
>>>
>>> AbstractImporter>>errorLog: is deprecated.... ok fair
>>>
>>> Now there are at least 4 methods that invoke this method and are
>>> not
>>> deprecated.
>>> So what do we do?
>>>
>>> How do we log error in moose?
>>> We don't?
>>>
>>> Stef
>>> _______________________________________________
>>> 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
>>
>
>
> _______________________________________________
> 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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5:01 p.m.
I did it.
pending for an answer
Stef
On Jun 13, 2008, at 5:08 PM, Orla Greevy wrote:
Ok I will do this :-)
Just spoke with Lukas and Google code sounds like a good solution :-)
CU
Orla
On Jun 13, 2008, at 4:51 PM, Stéphane Ducasse wrote:
Yes may be we should open a google code account
for moose.
Stef
On Jun 13, 2008, at 3:41 PM, Orla Greevy wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes, but wouldn't it be good to have a bug tracking system and
anytime
someone has time they could take a bug off the stack and fix it,
Some people are more involved with some packages than others so it
would be good to know this as well.
Of course I don't have the overview anymore of what is happening in
moose as I havent done much general moose coding just dynamoose
and a
few other small bits and pieces. So I guess this doesn't give me too
much of a say in moose.
Orla
On Jun 13, 2008, at 3:22 PM, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Orla
this is not the problem. I will fix the error reporting and remove
the
deprecation.
Apparently I could not get the message that error reporting is a
nice
feature of an environment (you know a little
console) but apparently this is not useful.
Now my point is different. From what I see: everybody is perfectly
happy with moose
as it is, and migrating to Squeak + changing Famix + changing from
Meta to Fame does not seem to be a problem
to anybody so perfect.
> We need a tool to report errors centrally for each version of
> Moose -
> one place for Squeak Moose and one place for VW Moose.
> I agree that the deprecation of a method without fixing the
> callers
> is
> a problem.
>
> Doru is at the football match today so that explains why you are
> not
> getting immediate response.
Sure there is no problem I was aware of that :)
Now still this is a good test because in couple of month they may
be
roumanian football matches
everyday.
> But the whole of moose should not rely on
> Doru otherwise it will die sooner or later.
>
> We could set up a bugzilla. What do you think?
>
> Cheers
> Orla
>
>
> On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote:
>
>> Yes but deprecating a method but not fixing its callers does not
>> help
>> Now I'm stuck. I do not know how to report errors in moose, there
>> is
>> broken code in Moose on VW
>> and on squeak this is not working either.
>>
>> I think that nobody cares about moose expect doru and we feel it.
>> Sad end for Moose. So I will certainly take over but what a pity.
>>
>> Stef
>>
>> On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
>>
>>> I do remember this was discussed once along time ago. Dont we
>>> have
>>> some bugzilla type solution?
>>>
>>> If not we should introduce something here...
>>>
>>> Cheers
>>> Orla
>>>
>>>
>>>
>>>
>>> On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
>>>
>>>> Hi guys
>>>>
>>>> I checked and found that
>>>>
>>>> AbstractImporter>>errorLog: is deprecated.... ok fair
>>>>
>>>> Now there are at least 4 methods that invoke this method and
>>>> are
>>>> not
>>>> deprecated.
>>>> So what do we do?
>>>>
>>>> How do we log error in moose?
>>>> We don't?
>>>>
>>>> Stef
>>>> _______________________________________________
>>>> 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
>>>
>>
>>
>> _______________________________________________
>> 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
>
_______________________________________________
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
5:18 p.m.
Ok cool. Can you also update the Moose page when you get the answer?
On Jun 13, 2008, at 5:01 PM, Stéphane Ducasse wrote:
I did it.
pending for an answer
Stef
On Jun 13, 2008, at 5:08 PM, Orla Greevy wrote:
Ok I will do this :-)
Just spoke with Lukas and Google code sounds like a good solution :-)
CU
Orla
On Jun 13, 2008, at 4:51 PM, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes may be we should open a google code account
for moose.
Stef
On Jun 13, 2008, at 3:41 PM, Orla Greevy wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes, but wouldn't it be good to have a bug tracking system and
anytime
someone has time they could take a bug off the stack and fix it,
Some people are more involved with some packages than others so it
would be good to know this as well.
Of course I don't have the overview anymore of what is happening in
moose as I havent done much general moose coding just dynamoose
and a
few other small bits and pieces. So I guess this doesn't give me
too
much of a say in moose.
Orla
On Jun 13, 2008, at 3:22 PM, Stéphane Ducasse wrote:
> Orla
>
> this is not the problem. I will fix the error reporting and remove
> the
> deprecation.
> Apparently I could not get the message that error reporting is a
> nice
> feature of an environment (you know a little
> console) but apparently this is not useful.
>
> Now my point is different. From what I see: everybody is perfectly
> happy with moose
> as it is, and migrating to Squeak + changing Famix + changing from
> Meta to Fame does not seem to be a problem
> to anybody so perfect.
>
>> We need a tool to report errors centrally for each version of
>> Moose -
>> one place for Squeak Moose and one place for VW Moose.
>> I agree that the deprecation of a method without fixing the
>> callers
>> is
>> a problem.
>>
>> Doru is at the football match today so that explains why you are
>> not
>> getting immediate response.
>
> Sure there is no problem I was aware of that :)
>
> Now still this is a good test because in couple of month they may
> be
> roumanian football matches
> everyday.
>
>> But the whole of moose should not rely on
>> Doru otherwise it will die sooner or later.
>>
>> We could set up a bugzilla. What do you think?
>>
>> Cheers
>> Orla
>>
>>
>> On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote:
>>
>>> Yes but deprecating a method but not fixing its callers does not
>>> help
>>> Now I'm stuck. I do not know how to report errors in moose,
>>> there
>>> is
>>> broken code in Moose on VW
>>> and on squeak this is not working either.
>>>
>>> I think that nobody cares about moose expect doru and we feel
>>> it.
>>> Sad end for Moose. So I will certainly take over but what a
>>> pity.
>>>
>>> Stef
>>>
>>> On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
>>>
>>>> I do remember this was discussed once along time ago. Dont we
>>>> have
>>>> some bugzilla type solution?
>>>>
>>>> If not we should introduce something here...
>>>>
>>>> Cheers
>>>> Orla
>>>>
>>>>
>>>>
>>>>
>>>> On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
>>>>
>>>>> Hi guys
>>>>>
>>>>> I checked and found that
>>>>>
>>>>> AbstractImporter>>errorLog: is deprecated.... ok fair
>>>>>
>>>>> Now there are at least 4 methods that invoke this method and
>>>>> are
>>>>> not
>>>>> deprecated.
>>>>> So what do we do?
>>>>>
>>>>> How do we log error in moose?
>>>>> We don't?
>>>>>
>>>>> Stef
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>
>
> _______________________________________________
> 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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
14 Jun
14 Jun
2:20 a.m.
Cool indeed. We had a bug database that Adrian set up, but in the end
he decided to kill it :). But, indeed it would be very nice to have
one again.
Doru
On Jun 13, 2008, at 5:18 PM, Orla Greevy wrote:
Ok cool. Can you also update the Moose page when you
get the answer?
On Jun 13, 2008, at 5:01 PM, Stéphane Ducasse wrote:
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Problem solving efficiency grows with the abstractness level of
problem understanding."
I did it.
pending for an answer
Stef
On Jun 13, 2008, at 5:08 PM, Orla Greevy wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Ok I will do this :-)
Just spoke with Lukas and Google code sounds like a good
solution :-)
CU
Orla
On Jun 13, 2008, at 4:51 PM, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes may be we should open a google code account
for moose.
Stef
On Jun 13, 2008, at 3:41 PM, Orla Greevy wrote:
>
> Yes, but wouldn't it be good to have a bug tracking system and
> anytime
> someone has time they could take a bug off the stack and fix it,
> Some people are more involved with some packages than others so it
> would be good to know this as well.
>
> Of course I don't have the overview anymore of what is happening
> in
> moose as I havent done much general moose coding just dynamoose
> and a
> few other small bits and pieces. So I guess this doesn't give me
> too
> much of a say in moose.
>
> Orla
>
>
>
>
>
> On Jun 13, 2008, at 3:22 PM, Stéphane Ducasse wrote:
>
>> Orla
>>
>> this is not the problem. I will fix the error reporting and
>> remove
>> the
>> deprecation.
>> Apparently I could not get the message that error reporting is a
>> nice
>> feature of an environment (you know a little
>> console) but apparently this is not useful.
>>
>> Now my point is different. From what I see: everybody is
>> perfectly
>> happy with moose
>> as it is, and migrating to Squeak + changing Famix + changing
>> from
>> Meta to Fame does not seem to be a problem
>> to anybody so perfect.
>>
>>> We need a tool to report errors centrally for each version of
>>> Moose -
>>> one place for Squeak Moose and one place for VW Moose.
>>> I agree that the deprecation of a method without fixing the
>>> callers
>>> is
>>> a problem.
>>>
>>> Doru is at the football match today so that explains why you are
>>> not
>>> getting immediate response.
>>
>> Sure there is no problem I was aware of that :)
>>
>> Now still this is a good test because in couple of month they may
>> be
>> roumanian football matches
>> everyday.
>>
>>> But the whole of moose should not rely on
>>> Doru otherwise it will die sooner or later.
>>>
>>> We could set up a bugzilla. What do you think?
>>>
>>> Cheers
>>> Orla
>>>
>>>
>>> On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote:
>>>
>>>> Yes but deprecating a method but not fixing its callers does
>>>> not
>>>> help
>>>> Now I'm stuck. I do not know how to report errors in moose,
>>>> there
>>>> is
>>>> broken code in Moose on VW
>>>> and on squeak this is not working either.
>>>>
>>>> I think that nobody cares about moose expect doru and we feel
>>>> it.
>>>> Sad end for Moose. So I will certainly take over but what a
>>>> pity.
>>>>
>>>> Stef
>>>>
>>>> On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
>>>>
>>>>> I do remember this was discussed once along time ago. Dont we
>>>>> have
>>>>> some bugzilla type solution?
>>>>>
>>>>> If not we should introduce something here...
>>>>>
>>>>> Cheers
>>>>> Orla
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
>>>>>
>>>>>> Hi guys
>>>>>>
>>>>>> I checked and found that
>>>>>>
>>>>>> AbstractImporter>>errorLog: is deprecated.... ok fair
>>>>>>
>>>>>> Now there are at least 4 methods that invoke this method and
>>>>>> are
>>>>>> not
>>>>>> deprecated.
>>>>>> So what do we do?
>>>>>>
>>>>>> How do we log error in moose?
>>>>>> We don't?
>>>>>>
>>>>>> Stef
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>
>>
>> _______________________________________________
>> 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
>
_______________________________________________
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
2:26 a.m.
Indeed, I truly do not want Moose to depend on just one person (not
even me :)), and I do not think that I am the only one that cares
about Moose either :).
Cheers,
Doru
On Jun 13, 2008, at 3:21 PM, Orla Greevy wrote:
We need a tool to report errors centrally for each
version of Moose -
one place for Squeak Moose and one place for VW Moose.
I agree that the deprecation of a method without fixing the callers is
a problem.
Doru is at the football match today so that explains why you are not
getting immediate response. But the whole of moose should not rely on
Doru otherwise it will die sooner or later.
We could set up a bugzilla. What do you think?
Cheers
Orla
On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote:
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Every thing has its own flow."
Yes but deprecating a method but not fixing its
callers does not help
Now I'm stuck. I do not know how to report errors in moose, there is
broken code in Moose on VW
and on squeak this is not working either.
I think that nobody cares about moose expect doru and we feel it.
Sad end for Moose. So I will certainly take over but what a pity.
Stef
On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I do remember this was discussed once along time
ago. Dont we have
some bugzilla type solution?
If not we should introduce something here...
Cheers
Orla
On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi guys
I checked and found that
AbstractImporter>>errorLog: is deprecated.... ok fair
Now there are at least 4 methods that invoke this method and are
not
deprecated.
So what do we do?
How do we log error in moose?
We don't?
Stef
_______________________________________________
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
9:41 a.m.
we need a measure for care and maintenance or improvement actions is
one that I understand
On Jun 14, 2008, at 2:26 AM, Tudor Girba wrote:
Indeed, I truly do not want Moose to depend on just
one person (not
even me :)), and I do not think that I am the only one that cares
about Moose either :).
Cheers,
Doru
On Jun 13, 2008, at 3:21 PM, Orla Greevy wrote:
We need a tool to report errors centrally for
each version of Moose -
one place for Squeak Moose and one place for VW Moose.
I agree that the deprecation of a method without fixing the callers
is
a problem.
Doru is at the football match today so that explains why you are not
getting immediate response. But the whole of moose should not rely on
Doru otherwise it will die sooner or later.
We could set up a bugzilla. What do you think?
Cheers
Orla
On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote:
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Every thing has its own flow."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes but deprecating a method but not fixing its
callers does not
help
Now I'm stuck. I do not know how to report errors in moose, there is
broken code in Moose on VW
and on squeak this is not working either.
I think that nobody cares about moose expect doru and we feel it.
Sad end for Moose. So I will certainly take over but what a pity.
Stef
On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I do remember this was discussed once along time
ago. Dont we have
some bugzilla type solution?
If not we should introduce something here...
Cheers
Orla
On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote:
> Hi guys
>
> I checked and found that
>
> AbstractImporter>>errorLog: is deprecated.... ok fair
>
> Now there are at least 4 methods that invoke this method and are
> not
> deprecated.
> So what do we do?
>
> How do we log error in moose?
> We don't?
>
> Stef
> _______________________________________________
> 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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5805
days inactive
5806
days old
14 comments
5 participants
participants (5)
-
Michele Lanza -
Orla Greevy -
stéphane ducasse -
Stéphane Ducasse -
Tudor Girba