db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-1554) IDENTITY_VAL_LOCAL() returned value is modified incorrectly by a multi-row INSERT statement.
Date Thu, 27 Jul 2006 15:37:26 GMT
Rick Hillegas (JIRA) wrote:

>Assigning this bug to 10.2 and bumping its priority to Critical. This will make it visible
to bug-fixers. Once the Urgency field appears, we can adjust the severity of this bug.
I think it is really important not to muck with the priority (mental 
translation SEVERITY) settings even with the intention of setting  them 
back later on.   A good way to cope until we have  Urgency   is  to look 
first at the open product regression list first:

and then at the   Blocker/Critical issues.
But I really feel stronger each day that Priority needs to stay as 
outlined in Jira and below:

    Blocks development and/or testing work, production could not run
    Crashes, loss of data, severe memory leak.
    Major loss of function.
    Minor loss of function, or other problem where easy workaround is 
    Cosmetic problem like misspelt words or misaligned text.

Andrew said that he would have this by the end of the week so we are 
talking about a day's wait.    We should not corrupt our bug database 
with wrong data or our thinking with wrong mappings by setting it 
incorrectly.  I have made this mistake myself in not marking DERBY-700 
Critical because it is hard to fix.  That was very wrong thinking on my 
part.  I fear has caused users to lose their data.  DERBY-700 is 
Priority *Critical*.  It's Urgency might be something else based on how 
hard it is to fix.


View raw message