On 1/17/08, Kathey Marsden [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] 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
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:
[EMAIL PROTECTED] wrote:
Is this query saved as a public filter in Jira? I could
Kathey Marsden [EMAIL PROTECTED] 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
Kathey Marsden wrote:
[EMAIL PROTECTED] 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,
Rick Hillegas wrote:
Kathey Marsden wrote:
[EMAIL PROTECTED] 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
Kathey Marsden wrote:
Rick Hillegas wrote:
Kathey Marsden wrote:
[EMAIL PROTECTED] 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
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,
Rick Hillegas [EMAIL PROTECTED] 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
Myrna van Lunteren [EMAIL PROTECTED] writes:
On 1/16/08, Army [EMAIL PROTECTED] 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
Kathey Marsden [EMAIL PROTECTED] writes:
Myrna van Lunteren wrote:
On 1/16/08, Army [EMAIL PROTECTED] 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)
Myrna van Lunteren [EMAIL PROTECTED] writes:
On 1/16/08, Army [EMAIL PROTECTED] 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
[EMAIL PROTECTED] wrote:
Kathey Marsden [EMAIL PROTECTED] writes:
Myrna van Lunteren wrote:
On 1/16/08, Army [EMAIL PROTECTED] 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
On 1/17/08, [EMAIL PROTECTED] [EMAIL PROTECTED] 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
[EMAIL PROTECTED] 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
Myrna van Lunteren [EMAIL PROTECTED] writes:
On 1/17/08, [EMAIL PROTECTED] [EMAIL PROTECTED] 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)
[EMAIL PROTECTED] 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.
[EMAIL PROTECTED] 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
On 1/17/08, Dag H. Wanvik [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] 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
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
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
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,
On 1/16/08, Army [EMAIL PROTECTED] 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
Myrna van Lunteren wrote:
On 1/16/08, Army [EMAIL PROTECTED] 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
23 matches
Mail list logo
