You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Dy...@Sun.COM on 2008/01/16 10:56:08 UTC

Blockers and 10.4

Currently we have two JIRA issues classified as "Blockers":

https://issues.apache.org/jira/browse/DERBY-3260

and

https://issues.apache.org/jira/browse/DERBY-3303


DERBY-3260 has a patch which has been reviewed favorably by Knut, but I
feel that the following quote from his comment deserves some attention:

"It would be interesting, though, if someone could shed some light on
why the synchronization was commented out in the first place. This piece
of code hasn't been changed since the code was donated to Apache, so the
commit log doesn't tell us anything about it."


It seems like both DERBY-3303 and its "Critical" cousin DERBY-3231
are caused by rev 516454 (fix for DERBY-681), (a fix was checked in for
DERBY-3231, but it remains open). Is there any chance of these being
fixed in time for 10.4?

-- 
dt

Re: Blockers and 10.4

Posted by Dy...@Sun.COM.
Rick Hillegas <Ri...@Sun.COM> writes:

> Hi Dyre,
>
> These two issues were marked as blockers by the people who logged
> them. Is that anything more than a statement of how much pain these
> issues cause those people? 

Probably not. But I wanted to get an impression of which open bugs could
be candidates for 10.4, and the high-priority issues seemed like a good
place to start. 

> If I were to categorize issues according to
> the severity of their impact, it would look something like this (in
> declining order of significance):
>
> 1) Engine crashes
> 2) Data corruption
> 3) Wrong results
> 4) Failures (e.g., a query just aborts)
> 5) Misleading messages, typos, ugly formatting, ...

Agreed. Except that I think I would move 1) below corruption and wrong
results, but that's just my opinion...

> These two issues seem to fall into category (4). 

> If I were release
> manager, I would downgrade these to the level of other NPEs and query
> aborts--beneath the significance of issues in category (3).

Agreed, and this is more or less what I was planning to do. In the case
of DERBY-3260 it seemed so close to being fixed that I thought it might
be easier just to get it checked in. But if it, for some reason, cannot
be fixed, I agree that it should be downgraded.

Wrt. DERBY-3303 I think that it is actually in category 3) (as I think
Army has said, as well).  

> You, of course, are the release manager. It's up to you to publish
> your criteria for ranking issues. It may also be helpful to ask the
> user community to vote on which issues are most important to them.

Well, I welcome any input on how to categorize bugs :)

>
> Dyre.Tjeldvoll@Sun.COM wrote:
>> Currently we have two JIRA issues classified as "Blockers":
>>
>> https://issues.apache.org/jira/browse/DERBY-3260
>>
>> and
>>
>> https://issues.apache.org/jira/browse/DERBY-3303
>>
>>
>> DERBY-3260 has a patch which has been reviewed favorably by Knut, but I
>> feel that the following quote from his comment deserves some attention:
>>
>> "It would be interesting, though, if someone could shed some light on
>> why the synchronization was commented out in the first place. This piece
>> of code hasn't been changed since the code was donated to Apache, so the
>> commit log doesn't tell us anything about it."
>>
>>
>> It seems like both DERBY-3303 and its "Critical" cousin DERBY-3231
>> are caused by rev 516454 (fix for DERBY-681), (a fix was checked in for
>> DERBY-3231, but it remains open). Is there any chance of these being
>> fixed in time for 10.4?
>>
>>   
>

-- 
dt

Re: HighValueFixCandidates (was Re: Blockers and 10.4)

Posted by Kathey Marsden <km...@sbcglobal.net>.
Myrna van Lunteren wrote:
>>     
> I wonder what the criteria are to get things on this wiki? Is it just
> up to whomever wants to add or remove something there?
>   
Pretty Much.  This is a description of the page:
This Wiki page is where members of the development community and those 
involved in support and QA can list fixes that they see as giving a 
potentially high return on time investment based on:

    *

      Frequency and likelihood the issue might be hit by users.

    *

      Estimated difficulty of fix.

    *

      Risk to existing users if the fix is implemented.

    *

      Severity of the issue.

    *

      Availability of a workaround.

    *

      The amount of user/developer time is wasted by the issue.

Just a smaller list for bug fixers to look at if they don't want to go 
through the 302 open bugs that we have.
> For instance, DERBY-1482 is marked as minor, and has no
> watchers/voters...I'd remove it...(still needs to get fixed, of
> course, I just wonder about the "high value").
>
>   
I saw it as a likely user hit,  but perhaps you are right, since nobody 
has seemed to have hit it so far, maybe it doesn't qualify.

Kathey



Re: HighValueFixCandidates (was Re: Blockers and 10.4)

Posted by Myrna van Lunteren <m....@gmail.com>.
On 1/17/08, Kathey Marsden <km...@sbcglobal.net> wrote:
> Dyre.Tjeldvoll@Sun.COM wrote:
> > Ok, as you may have noticed I have updated the HighValueFixCandidates
> > page with a status column. (Most are still open unfortunately). For now
> > I have just created a link from the Bug fixing section of the 10.4 wiki
> > page.
> >
> >
> I tend to think it is best to remove the resolved and perhaps even in
> progress issues from the list.  I think it should just be a list of fix
> candidates. Otherwise the list gets too long to be useful.
>
> Kathey
>
>
>
I wonder what the criteria are to get things on this wiki? Is it just
up to whomever wants to add or remove something there?
For instance, DERBY-1482 is marked as minor, and has no
watchers/voters...I'd remove it...(still needs to get fixed, of
course, I just wonder about the "high value").

Myrna

Re: HighValueFixCandidates

Posted by Dy...@Sun.COM.
Kathey Marsden <km...@sbcglobal.net> writes:

> Dyre.Tjeldvoll@Sun.COM wrote:
>> Ok, as you may have noticed I have updated the HighValueFixCandidates
>> page with a status column. (Most are still open unfortunately). For now
>> I have just created a link from the Bug fixing section of the 10.4 wiki
>> page.
>>
>>   
> I tend to think it is best to remove the resolved and perhaps even in
> progress issues from the list.  I think it should just be a list of
> fix candidates. Otherwise the list gets too long to be useful.

Ok, makes sense. Should DERBY-3230 be removed as well? It isn't in
progress but it is assigned to you and has a patch ready for review
AFAICT?

-- 
dt

HighValueFixCandidates (was Re: Blockers and 10.4)

Posted by Kathey Marsden <km...@sbcglobal.net>.
Dyre.Tjeldvoll@Sun.COM wrote:
> Ok, as you may have noticed I have updated the HighValueFixCandidates
> page with a status column. (Most are still open unfortunately). For now
> I have just created a link from the Bug fixing section of the 10.4 wiki
> page.
>
>   
I tend to think it is best to remove the resolved and perhaps even in 
progress issues from the list.  I think it should just be a list of fix 
candidates. Otherwise the list gets too long to be useful.

Kathey



Re: Blockers and 10.4

Posted by Dy...@Sun.COM.
Myrna van Lunteren <m....@gmail.com> writes:

> On 1/17/08, Dyre.Tjeldvoll@sun.com <Dy...@sun.com> wrote:
>> Do you have any thoughts on how to maintain this page? Should we create
>> a new page for each release and just copy those issues still not solved?
>> Or perhaps create a new section (on this page) for each new release?
>>
>> --
>> dt
>>
> Hm, good point...If we find it important to track how many of the high
> fix candidates got fixed for a certain release, we should add areas
> per release.
>
> If I remember correctly what's happened with this page I think until
> now issues just were added and removed as they came up and got fixed.
> If we decide to go on in this way we could simply remove the link from
> the DerbyTenThreeRelease page and remove the 10.3 reference from the
> HighValueFixCandidates page...

Ok, as you may have noticed I have updated the HighValueFixCandidates
page with a status column. (Most are still open unfortunately). For now
I have just created a link from the Bug fixing section of the 10.4 wiki
page.

-- 
dt

Re: Blockers and 10.4

Posted by Myrna van Lunteren <m....@gmail.com>.
On 1/17/08, Dyre.Tjeldvoll@sun.com <Dy...@sun.com> wrote:
> Do you have any thoughts on how to maintain this page? Should we create
> a new page for each release and just copy those issues still not solved?
> Or perhaps create a new section (on this page) for each new release?
>
> --
> dt
>
Hm, good point...If we find it important to track how many of the high
fix candidates got fixed for a certain release, we should add areas
per release.

If I remember correctly what's happened with this page I think until
now issues just were added and removed as they came up and got fixed.
If we decide to go on in this way we could simply remove the link from
the DerbyTenThreeRelease page and remove the 10.3 reference from the
HighValueFixCandidates page...

Myrna

Re: Blockers and 10.4

Posted by Dy...@Sun.COM.
Myrna van Lunteren <m....@gmail.com> writes:

> On 1/16/08, Army <qo...@gmail.com> wrote:
>> Rick Hillegas wrote:
>>
>> > If I were to categorize issues according to the severity of
>> > their impact, it would look something like this (in declining
>> > order of significance):
>> >
>> > 1) Engine crashes
>> > 2) Data corruption
>> > 3) Wrong results
>> > 4) Failures (e.g., a query just aborts)
>> > 5) Misleading messages, typos, ugly formatting, ...
>>
> I would add to that list
>  Unintended regression of behavior/fixes.
> (not sure of the priority of it, but I'm inclined to see it as 0).
>
> Also, maybe there are some items off Kathey's high value fix bugs that
> can be fixed for 10.4.
> http://wiki.apache.org/db-derby/HighValueFixCandidates

Do you have any thoughts on how to maintain this page? Should we create
a new page for each release and just copy those issues still not solved?
Or perhaps create a new section (on this page) for each new release?

-- 
dt

Heads up: pending commit will require recreating trunk databases

Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Just a warning, so you know what's going on when you can no longer
boot your trunk database :) Early next week I plan to commit at patch for
DERBY-3137 that will change the dictionary format for SYSROLES.

Dag
 

Re: Blockers and 10.4

Posted by Myrna van Lunteren <m....@gmail.com>.
On 1/17/08, Dag H. Wanvik <Da...@sun.com> wrote:
> Dyre.Tjeldvoll@Sun.COM writes:
>
> > I guess I see 'regression' as a separate dimension which increases the
> > priority. In general I think all regressions should have higher priority
> > than non-regressions, but I would not prioritize say, an unclear error
> > message regression over a data corruption that is not a regression.
>
> +1
>
> Dag
>
Yes, I'll +1 to this prioritizing also.
Myrna

Re: Blockers and 10.4

Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Dyre.Tjeldvoll@Sun.COM writes:

> I guess I see 'regression' as a separate dimension which increases the
> priority. In general I think all regressions should have higher priority
> than non-regressions, but I would not prioritize say, an unclear error
> message regression over a data corruption that is not a regression.

+1

Dag

Re: Blockers and 10.4

Posted by Dy...@Sun.COM.
Myrna van Lunteren <m....@gmail.com> writes:

> On 1/16/08, Army <qo...@gmail.com> wrote:
>> Rick Hillegas wrote:
>>
>> > If I were to categorize issues according to the severity of
>> > their impact, it would look something like this (in declining
>> > order of significance):
>> >
>> > 1) Engine crashes
>> > 2) Data corruption
>> > 3) Wrong results
>> > 4) Failures (e.g., a query just aborts)
>> > 5) Misleading messages, typos, ugly formatting, ...
>>
> I would add to that list
>  Unintended regression of behavior/fixes.
> (not sure of the priority of it, but I'm inclined to see it as 0).

I guess I see 'regression' as a separate dimension which increases the
priority. In general I think all regressions should have higher priority
than non-regressions, but I would not prioritize say, an unclear error
message regression over a data corruption that is not a regression.

> Also, maybe there are some items off Kathey's high value fix bugs that
> can be fixed for 10.4.
> http://wiki.apache.org/db-derby/HighValueFixCandidates

Thanks for posting the link. I'll bookmark it :)

-- 
dt

Re: Regression Filter

Posted by Dy...@Sun.COM.
Kathey Marsden <km...@sbcglobal.net> writes:

> Dyre.Tjeldvoll@Sun.COM wrote:
>> Is this query saved as a public filter in Jira? I could not find it.
>>
>>   
> It is the Jira filter Derby Open Product Regressions.  

OK, I get it, thanks. I've updated the 10.4 Wiki with links to some jira
filters.

>I was wondering
> if a Jira admin could subscribe derby-dev to this filter to get a
> report once a week.

Could be a good idea.

-- 
dt

Re: Regression Filter (was Re: Blockers and 10.4)

Posted by Rick Hillegas <Ri...@Sun.COM>.
Ok, I think I've found this one. I subscribed derby-dev to Open Product 
Regressions. The report should be mailed every Sunday.

Regards,
-Rick

Kathey Marsden wrote:
> Rick Hillegas wrote:
>> Kathey Marsden wrote:
>>> Dyre.Tjeldvoll@Sun.COM wrote:
>>>> Is this query saved as a public filter in Jira? I could not find it.
>>>>
>>>>   
>>> It is the Jira filter Derby Open Product Regressions.  I was 
>>> wondering if a Jira admin could subscribe derby-dev to this filter 
>>> to get a report once a week.
>>>
>>>
>>>
>> Hi Kathey,
>>
>> I found a filter called Derby Open Regressions. I have subscribed 
>> derby-dev to receive a copy of this report every Sunday. Please let 
>> me know if that's not what you wanted.
>>
> That filter does not pick up the issues that are in progress. There is 
> another one Derby Open Product Regressions which looks ok. Derby Open 
> Regressions then can probably be deleted.
>
> Kathey
>
>
>
>
>
>
>
>
>
>


Re: Regression Filter (was Re: Blockers and 10.4)

Posted by Dy...@Sun.COM.
Kathey Marsden <km...@sbcglobal.net> writes:

>> I must be going blind. I don't see a filter called Derby Open
>> Product Regressions. Can you tell me where it lives in your list of
>> filters?
>>
> In my list it shows up just before Derby Open Regressions. In manage
> filters though it shows up under "Your filters" with sharing:
> Group:derby-developers, so maybe it is only I that can see it for some
> reason.  If you can't see it is it  possible to change the Derby Open
> Regressions to include "In Progress". That would be just as good. I
> couldn't seem to do it myself, but maybe with your karma ...

I can confirm that there are two filters for open regressions, one
created by Kathey and one by Rick, and one does not include those in
progress. 

For the 10.4 Wiki I ended up not using a filter, but rather embed a link
to a query for _unresolved_ regressions...

-- 
dt

Re: Regression Filter (was Re: Blockers and 10.4)

Posted by Kathey Marsden <km...@sbcglobal.net>.
> I must be going blind. I don't see a filter called Derby Open Product 
> Regressions. Can you tell me where it lives in your list of filters?
>
In my list it shows up just before Derby Open Regressions. In manage 
filters though it shows up under "Your filters" with sharing: 
Group:derby-developers, so maybe it is only I that can see it for some 
reason.  If you can't see it is it  possible to change the Derby Open 
Regressions to include "In Progress". That would be just as good. I 
couldn't seem to do it myself, but maybe with your karma ...

Kathey



Re: Regression Filter (was Re: Blockers and 10.4)

Posted by Rick Hillegas <Ri...@Sun.COM>.
Kathey Marsden wrote:
> Rick Hillegas wrote:
>> Kathey Marsden wrote:
>>> Dyre.Tjeldvoll@Sun.COM wrote:
>>>> Is this query saved as a public filter in Jira? I could not find it.
>>>>
>>>>   
>>> It is the Jira filter Derby Open Product Regressions.  I was 
>>> wondering if a Jira admin could subscribe derby-dev to this filter 
>>> to get a report once a week.
>>>
>>>
>>>
>> Hi Kathey,
>>
>> I found a filter called Derby Open Regressions. I have subscribed 
>> derby-dev to receive a copy of this report every Sunday. Please let 
>> me know if that's not what you wanted.
>>
> That filter does not pick up the issues that are in progress. There is 
> another one Derby Open Product Regressions which looks ok. Derby Open 
> Regressions then can probably be deleted.
>
> Kathey
I must be going blind. I don't see a filter called Derby Open Product 
Regressions. Can you tell me where it lives in your list of filters?

Rick
>
>
>
>
>
>
>
>
>
>


Re: Regression Filter (was Re: Blockers and 10.4)

Posted by Kathey Marsden <km...@sbcglobal.net>.
Rick Hillegas wrote:
> Kathey Marsden wrote:
>> Dyre.Tjeldvoll@Sun.COM wrote:
>>> Is this query saved as a public filter in Jira? I could not find it.
>>>
>>>   
>> It is the Jira filter Derby Open Product Regressions.  I was 
>> wondering if a Jira admin could subscribe derby-dev to this filter to 
>> get a report once a week.
>>
>>
>>
> Hi Kathey,
>
> I found a filter called Derby Open Regressions. I have subscribed 
> derby-dev to receive a copy of this report every Sunday. Please let me 
> know if that's not what you wanted.
>
That filter does not pick up the issues that are in progress. There is 
another one Derby Open Product Regressions which looks ok. Derby Open 
Regressions then can probably be deleted.

Kathey











Re: Regression Filter (was Re: Blockers and 10.4)

Posted by Rick Hillegas <Ri...@Sun.COM>.
Kathey Marsden wrote:
> Dyre.Tjeldvoll@Sun.COM wrote:
>> Is this query saved as a public filter in Jira? I could not find it.
>>
>>   
> It is the Jira filter Derby Open Product Regressions.  I was wondering 
> if a Jira admin could subscribe derby-dev to this filter to get a 
> report once a week.
>
>
>
Hi Kathey,

I found a filter called Derby Open Regressions. I have subscribed 
derby-dev to receive a copy of this report every Sunday. Please let me 
know if that's not what you wanted.

Thanks,
-Rick

Regression Filter (was Re: Blockers and 10.4)

Posted by Kathey Marsden <km...@sbcglobal.net>.
Dyre.Tjeldvoll@Sun.COM wrote:
> Is this query saved as a public filter in Jira? I could not find it.
>
>   
It is the Jira filter Derby Open Product Regressions.  I was wondering 
if a Jira admin could subscribe derby-dev to this filter to get a report 
once a week.




Re: Blockers and 10.4

Posted by Kristian Waagan <Kr...@Sun.COM>.
Dyre.Tjeldvoll@Sun.COM wrote:
> Kathey Marsden <km...@sbcglobal.net> writes:
> 
>> Myrna van Lunteren wrote:
>>> On 1/16/08, Army <qo...@gmail.com> wrote:
>>>   
>>>> Rick Hillegas wrote:
>>>>
>>>>     
>>>>> If I were to categorize issues according to the severity of
>>>>> their impact, it would look something like this (in declining
>>>>> order of significance):
>>>>>
>>>>> 1) Engine crashes
>>>>> 2) Data corruption
>>>>> 3) Wrong results
>>>>> 4) Failures (e.g., a query just aborts)
>>>>> 5) Misleading messages, typos, ugly formatting, ...
>>>>>       
>>> I would add to that list
>>>  Unintended regression of behavior/fixes.
>>> (not sure of the priority of it, but I'm inclined to see it as 0).
>>>   
>> +1
>> We are accumulating quite a list:
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&status=1&status=3&status=4&customfield_12310090=Regression&sorter/field=issuekey&sorter/order=ASC&sorter/field=updated&sorter/order=DESC&sorter/field=priority&sorter/order=DESC
>>
> 
> Thanks Kathey. 
> 
> Is this query saved as a public filter in Jira? I could not find it.
> 

Hi Dyre,

I can access the filter.
If the link doesn't work for you, maybe you have to be logged in to be 
able to use it?

I do note however, that Jira says the filter is a new, unsaved search.


-- 
Kristian

Re: Blockers and 10.4

Posted by Dy...@Sun.COM.
Kathey Marsden <km...@sbcglobal.net> writes:

> Myrna van Lunteren wrote:
>> On 1/16/08, Army <qo...@gmail.com> wrote:
>>   
>>> Rick Hillegas wrote:
>>>
>>>     
>>>> If I were to categorize issues according to the severity of
>>>> their impact, it would look something like this (in declining
>>>> order of significance):
>>>>
>>>> 1) Engine crashes
>>>> 2) Data corruption
>>>> 3) Wrong results
>>>> 4) Failures (e.g., a query just aborts)
>>>> 5) Misleading messages, typos, ugly formatting, ...
>>>>       
>> I would add to that list
>>  Unintended regression of behavior/fixes.
>> (not sure of the priority of it, but I'm inclined to see it as 0).
>>   
> +1
> We are accumulating quite a list:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&status=1&status=3&status=4&customfield_12310090=Regression&sorter/field=issuekey&sorter/order=ASC&sorter/field=updated&sorter/order=DESC&sorter/field=priority&sorter/order=DESC
>

Thanks Kathey. 

Is this query saved as a public filter in Jira? I could not find it.

-- 
dt

Re: Blockers and 10.4

Posted by Kathey Marsden <km...@sbcglobal.net>.
Myrna van Lunteren wrote:
> On 1/16/08, Army <qo...@gmail.com> wrote:
>   
>> Rick Hillegas wrote:
>>
>>     
>>> If I were to categorize issues according to the severity of
>>> their impact, it would look something like this (in declining
>>> order of significance):
>>>
>>> 1) Engine crashes
>>> 2) Data corruption
>>> 3) Wrong results
>>> 4) Failures (e.g., a query just aborts)
>>> 5) Misleading messages, typos, ugly formatting, ...
>>>       
> I would add to that list
>  Unintended regression of behavior/fixes.
> (not sure of the priority of it, but I'm inclined to see it as 0).
>   
+1
We are accumulating quite a list:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&status=1&status=3&status=4&customfield_12310090=Regression&sorter/field=issuekey&sorter/order=ASC&sorter/field=updated&sorter/order=DESC&sorter/field=priority&sorter/order=DESC


Re: Blockers and 10.4

Posted by Myrna van Lunteren <m....@gmail.com>.
On 1/16/08, Army <qo...@gmail.com> wrote:
> Rick Hillegas wrote:
>
> > If I were to categorize issues according to the severity of
> > their impact, it would look something like this (in declining
> > order of significance):
> >
> > 1) Engine crashes
> > 2) Data corruption
> > 3) Wrong results
> > 4) Failures (e.g., a query just aborts)
> > 5) Misleading messages, typos, ugly formatting, ...
>
I would add to that list
 Unintended regression of behavior/fixes.
(not sure of the priority of it, but I'm inclined to see it as 0).

Also, maybe there are some items off Kathey's high value fix bugs that
can be fixed for 10.4.
http://wiki.apache.org/db-derby/HighValueFixCandidates

Myrna

Re: Blockers and 10.4

Posted by Army <qo...@gmail.com>.
Rick Hillegas wrote:

> If I were to categorize issues according to the severity of 
> their impact, it would look something like this (in declining
> order of significance):
> 
> 1) Engine crashes
> 2) Data corruption
> 3) Wrong results
> 4) Failures (e.g., a query just aborts)
> 5) Misleading messages, typos, ugly formatting, ...

Just a note that if you're looking for issues that fall into category 
#3, DERBY-2034 is a good place to start, as it has a relatively 
consolidated list.  Whether or not any of those should block 10.4, I 
don't know.

Army


Re: Blockers and 10.4

Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi Dyre,

These two issues were marked as blockers by the people who logged them. 
Is that anything more than a statement of how much pain these issues 
cause those people? If I were to categorize issues according to the 
severity of their impact, it would look something like this (in 
declining order of significance):

1) Engine crashes
2) Data corruption
3) Wrong results
4) Failures (e.g., a query just aborts)
5) Misleading messages, typos, ugly formatting, ...

These two issues seem to fall into category (4). If I were release 
manager, I would downgrade these to the level of other NPEs and query 
aborts--beneath the significance of issues in category (3).

You, of course, are the release manager. It's up to you to publish your 
criteria for ranking issues. It may also be helpful to ask the user 
community to vote on which issues are most important to them.

Thanks,
-Rick


Dyre.Tjeldvoll@Sun.COM wrote:
> Currently we have two JIRA issues classified as "Blockers":
>
> https://issues.apache.org/jira/browse/DERBY-3260
>
> and
>
> https://issues.apache.org/jira/browse/DERBY-3303
>
>
> DERBY-3260 has a patch which has been reviewed favorably by Knut, but I
> feel that the following quote from his comment deserves some attention:
>
> "It would be interesting, though, if someone could shed some light on
> why the synchronization was commented out in the first place. This piece
> of code hasn't been changed since the code was donated to Apache, so the
> commit log doesn't tell us anything about it."
>
>
> It seems like both DERBY-3303 and its "Critical" cousin DERBY-3231
> are caused by rev 516454 (fix for DERBY-681), (a fix was checked in for
> DERBY-3231, but it remains open). Is there any chance of these being
> fixed in time for 10.4?
>
>