I realize that counting all the time we all took to write all those emails filling up this thread, we surely would have had time to:
1) report the problem in the bug tracker 2) write a temporary fix 3) write unit tests to check for this bug 4) run the test suite 5) move on to something else (and wait for a "proper" fix) :) ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein) ________________________________ From: Philippe Marschall <[email protected]> To: [email protected] Sent: Wed, July 20, 2011 10:00:23 AM Subject: Re: [Pharo-project] UUIDs not so unique On 07/20/2011 03:09 PM, Benoit St-Jean wrote: > Hi guys, > > If I might add, considering the fact that Pharo is putting **lots** of > efforts > into unit testing and automated builds using Hudson/Jenkins, we are getting > closer to "as good as it gets" when you talk about stability of the image and > serious testing and coverage. However, we can't trap every bug all the time, > for every combination of image/VM/OS !!! > > If every time I caught a bug I would have used the argument "this is exactly >the > > kind of shit that makes me want to never again use <whatever> in production", > I > > would still work out of paper and pencil. No Oracle, no VisualAge, no > VisualWorks, no Dolphin, no DB/2, no Windows, no Linux, no MS-Office, no > OpenOffice, no MySQL, no Apache, no whateveryoucouldthinkabout... > > number of images * number of VMs * number of OSes = A LOT TO COVER AND TEST. > > Let's all keep that in mind... > > Besides, I still haven't found a single piece of software without a bug! > Pharo > > ain't different. > > Gentlemen, back to your class browsers and let's make this thing even better! You realize the irony of asking people to write more code when they report that the SCM just broke on them? Cheers Philippe
