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.
>
> Cheers,
> - Andreas
>
--
=
=
=
========================================================================
John M. McIntosh <
[hidden email]>
Corporate Smalltalk Consulting Ltd.
http://www.smalltalkconsulting.com=
=
=
========================================================================
Locked
