Well the *real* issue here is that VM level fixes just aren't properly
tracked and place in the VM or NOT placed in the VM. The process I'm
afraid just relies on too many
folks remembering to check the bugs, acting on email flows to the vm-
dev list or squeak list.
What I would propose is say a monthly or even quarterly meeting/
mailing? to co-ordinate the process to a better degree to ensure yes
or no this fix is going into the VM.
On Jun 18, 2008, at 2:44 PM, Andreas Raab wrote:
> nicolas cellier wrote:
>> Dilbert Dogbert a écrit :
>>> Andreas Raab wrote:
>>>> No - we've fixed this a long time ago in our code base.
>>> Thanks for not sharing
>> Can't speak for Andreas, but would i be asked so kindly that i'm
>> not sure i would be more inclined to share.
> Oh don't worry I'm pretty thick-skinned. The only disappointing part
> is that the above poster (who happens to be a well-renowned member
> of the Squeak community btw) thinks that I wouldn't instantly
> recognize his style. I mean "Dilbert Dogbert"? Come on, you might
> have just as well signed with your real name ;-)
>> Let's be more positive!
>> Thanks for taking time to share in squeak-dev finally.
> You're welcome. Interestingly, the exchange that sparked this fix
> included both Tim and John. Seems like they didn't consider this to
> be uber-critical either.
> - Andreas
John M. McIntosh <[hidden email]>
Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com =
Re: Re: [squeak-dev] Re: Bug in object finalization?
On 18-Jun-08, at 4:22 PM, John M McIntosh wrote:
Well the *real* issue here is that VM level fixes just aren't properly tracked and place in the VM or NOT placed in the VM. The process I'm afraid just relies on too many folks remembering to check the bugs, acting on email flows to the vm-dev list or squeak list.
Well there is Mantis; currently I have 16 reports open, some of which are suspended pending answers or information from other people.
6966 is waiting on repsonse from kbrown and/or jmm
What I would propose is say a monthly or even quarterly meeting/mailing? to co-ordinate the process to a better degree to ensure yes or no this fix is going into the VM.
Yes, something like that would be nice. Of course, a large part of the problem has been that I've been busy for the last while and unable to pay much attention, for which I must apologise. Right now I'm trying to catch up and get things into a good enough state to make it sensible to run a more open repository for VMMaker. Getting answers from the above mentioned people would be a big help.