[Opensource] isn't it a priority to correct bugs ?

Thu Oct 24 06:40:18 PDT 2002

hi mike,
i ask this list about CVS two times, without answer,
in this mail, you talk about CVS HEAD, whats that?
how can i obtain fixes in that branch?
as you know i am very interested in solve problem
with dbpool, cause of high use of the system
that we are developing.

thanks in advance,
and good answer this one.

regards.
david gil.

>At 09:01 AM 10/23/02 +0200, you wrote:
>
>>Hi,
>>I am surprised having read several mails concerning bugs and being 
>>unanswered. Specifically, I sent on oct 16. a mail titled "minor pbs 
>>encountered switching from Expresso 4.02 to 5.0", and saw 2 days later 
>>same bug as one I detected reported by David Gil under title "bug in 
>>update method in 5.0 class JDBCExecutor".
>
>Thierry,
>
>Most of this that I have seen have been bugs that I have already fixed in 
>CVS for the 5.0.1 release, and I  THOUGHT that I acknowledged them on the 
>listserv.  If the acknowledgement didn't get sent, then I'm sorry for that.
>
>As far as some bugs that came in last minute, like DBConnectionPool 
>opening too many connections goes,  I had posted to the listserv  well 
>before the 5.0 final release, that my goal was to get a release out there 
>to the people because at that point, Expresso 5 was much more robust in 
>several areas than Expresso 4.02 and it was unfair to make those people 
>wait longer to get their hands on bugs that had been fixed 6 months ago.
>
>As almost anybody will agree on this list, fixing bugs can sometimes 
>introduce other bugs.  As it was, I made the evaluation of which bugs were 
>'non-critical' and would appear in the next release. [In this case 5.0.1].
>
>Now, before I get any feathers ruffled, I DO understand that if you're 
>experiencing a particular bug, having others tell you it is 'non critical' 
>is the fastest way to get you to tell your tool vendor to go jump in a 
>lake.  So let me tell you how I rated things so you can understand that it 
>was not so arbitrary as it seems on the outside.  I'm going to take three 
>bugs, two that were marked as 'critical' in my book, and one that was 
>marked 'non critical'.
>
>Null Date Fields:  Expresso RC's were crashing on null date fields.  This 
>I classed as a critical bug since it was causing exceptions to occur for 
>people that had been happily using null date fields in their database for 
>some time.  I believe I fixed all known the issues related to that before 
>the Expreso 5 final release.
>
>Oracle Compatability:  Several users were using Oracle in Expreso 
>4.02.  Having issues that would prevent Oracle DB compatability would be a 
>serious issue indeed.
>
>DBConnectionPool:  This is an example of a 'serious' bug that got put off 
>until 5.0.1.  For those that missed it, here's what happened with 
>it:  Expresso's DBConnectionPool has the ability to make up to X number of 
>connections to the database.  However, if there is a large burst of 
>people, DBConnectionPool was making more connections than that defined in 
>the setup table.  This was being caused by a race condition in the code 
>for creating new connections.
>
>So why did I put it off onto the next release for something that could 
>potentially consume huge amounts of database resources?    There were 
>several contributing factors.  Although no single factor is a good enough 
>reason to postpone the inclusion, all together they add up.  So please 
>bear with me for a second:
>
>(1) Time.  Including the fix at the time the bug was found would most 
>likely require yet another release candidate in the release cycle.  That 
>means, that the people that are waiting on the other 100+ bugs fixed since 
>4.02 would have to wait another 2 weeks or so.
>
>(2) Functionality.  The crucialness of the bug was brought down one notch 
>because even under load DBConnectionPool itself wouldn't "crash"... 
>although the underlying database might crash due to the resource load, it 
>was my evaluation that most sites using Expresso at the current time would 
>not be experiencing database crashes due to this bug.  Why would I say 
>that?  Read on to #3 :)
>
>(3) Repeatability.  Since Expresso 4.02 [when I took over the project], 
>I've fixed SEVERAL concurrency errors that would cause different kinds of 
>crashes under loads.   However, nobody was reporting the race conditions I 
>came across... in fact David G. was the first.
>
>So I was left with the decision... is this bug effecting enough current 
>Expresso users to warrant making everybody wait even longer then they 
>have. [And a thanks goes out there to all you people like Mike Traum that 
>patiently waited!]  As the person ultimately responsible for the project, 
>I decided that it was in the best interest of the community to release it 
>as it, and put the bugfix into CVS for the 5.0.1 release.
>
>Now for those out there, wondering why some of their bugs seem to be 
>fixed, but they can't find it in CVS, it simply boils down to the fact 
>that some bugs were fixed in CVS HEAD and some were in the expresso-4-1 
>branch.  I'm in the process of merging those bug fixes into a unified code 
>base, so we can finish out a 5.0.1 release.  This is part of the source 
>for confusion.
>
>Now is it possible that you're referring to a bug posted on the list that 
>I missed?  Sure.... sometimes emails get buried with the intention of 
>replying to it.... it's certainly not my intention to ignore people.
>
>I'm sorry that you've hit a frustration point with Expresso on this, but 
>if you check the changelog, you'll already see that 10 bugs have been 
>fixed since the last release in CVS, with more on the way. So I would 
>hardly say that bug fixing isn't a priority!
>
>As far as performance problems, I'm curious as to where you're 
>encountering them since by and large, Expresso 5 is using much less memory 
>than 4 and should be more scaleable as well.  If you could be more 
>specific in this, I'd like to track it down.
>
>HTH!
>
>                                         -Mike
>
>
>
>_______________________________________________
>Opensource mailing list
>Opensource at jcorporate.com
>http://mail.jcorporate.com/mailman/listinfo/opensource
>Archives: http://mail.jcorporate.com/pipermail/opensource/

David Gil Sánchez
------------------------------------------------
INDABA Consultores <Internet y Bases de Datos>
Centro de empresas Oarsoaldea (Edificio Mamut)
Carretera Astigarraga, 2 - 2º
Oiartzun (Guipúzcoa)
943 261121
http://www.indaba.es
------------------------------------------------

_______________________________________________________________
Yahoo! Messenger
Nueva versión: Webcam, voz, y mucho más ¡Gratis! 
Descárgalo ya desde http://messenger.yahoo.es