[NEW FAQ] about how to choose project when report bug

[Russ Tyndall]

On 5/10/06 12:41 PM, "Ruslan Zasukhin" <sunshine at public.kherson.ua> wrote:

> On 5/10/06 6:33 PM, "Russ Tyndall" <fitzbew at nc.rr.com> wrote:
> 
>>> http://www.valentina-db.com/dokuwiki/doku.php?id=paradigma:public:en:documen
>>> tation:vgeneral:faqs:faqs
>> 
>> Ruslan,
>> 
>> Great information.  I believe all mine are classified correctly except for:
>> 
>> 0001487 2.x DB Open for 200mb DB File Takes Unusually Long
>> 
>> I put this in V4RB but since it happens with Vstudio also, it should be
>> kernel.  Can you change it? (I don't believe I can.)
> 
> Yes we will move it KERNEL
> 
>> By the way, it is a good time to remind users that they should *always* make
>> an entry in Mantis for bugs, etc.. EVEN if Paradigma staff were instrumental
>> in verifying the problem.  I have had to learn this lesson more than once --
>> but that's my problem.
> 
> right
> 
>> I would love to have a better understanding of how Paradigma prioritizes
>> items. I have sometimes found myself reluctant to file a report because I'm
>> afraid it might delay fixing other reports I have made, which are more
>> important to me.
> 
>> I imagine that with so many products, prioritization of such items must be
>> extremely difficult.
> 
> There is no exact rule how we set priority.
> Many factors:
> 
> * how good bug is explained
> 
> * how good and easy to reproduce bug is and project is.
> 
> * how hard  to fix bug.
> 
> * how important we consider a client.
>   VDN users and VServer users we try pay more attention.
> 
> * if this bug is crash or simple glitch
> 
> * if this bug is ADK or kernel
> 
> * estimate how many people it can affect
> 
> * how good bugs fit into the current stream of work
> 

I believe most developers would agree these are sensible and prudent.

>   for example, I DO NOT try now profile your bug Russ on speed,
>   although this is fastest way to find where is problem.
> 

I am not too worried about it; I have only had a few complaints.  My real
fear is that folks have been seeing this problem in my software all along
and have *not* been complaining --- just deciding that it is lousily
designed software and they never use it again.

But even you and I had not noticed this problem, so perhaps it is not
causing that much pain.

Besides, my deployed app is still using 1.x, and the problem is not as
noticeable (it only takes about 20 secs to open my DB in 1.x, instead of the
40 seconds to open the converted DB in 2.x).

>   But I have decide implement EXPLAIN feature, to give powerful
>   tool into hands of all us.
> 

Yes, we will all benefit from this.

>   But if you will start complain and say - "tomorrow my deadline",
>   then I will go by faster way..
> 

Complain?  If I was facing such a deadline, we would work out some business
arrangement.  In this case, it makes more sense financially to simply delay
migrating to 2.x.  I believe (now that you are aware of it) that you will
not tolerate this slow-opening problem very long; that is where I am placing
my bets.  :-)

-- 
Russ Tyndall
Wake Forest, NC