db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: Blocker/Critical issues update
Date Mon, 27 Feb 2006 16:09:11 GMT
I have tried to ping Scott privately on the email address linked to his 
name: 044276m@acadiau.ca <mailto:044276m@acadiau.ca>. The mail was 
undeliverable. At the risk of incurring my peers' censure, I will page 
him in the subject line of an email message. I do think this is an 
important enhancement request, gauged by the number of times people 
request it. However, I'm downgrading this JIRA to "major".


Daniel John Debrunner wrote:

>Rajesh Kartha wrote:
>>Critical:  DERBY-396 -Support for ALTER STATEMENT to DROP , MODIFY,
>>(No information about the status, hence should be un-assigned and maybe
>>marked Medium - if we are not targeting it to be
>>fixed for the upcoming 10.2 release)
>Not sure why it would be un-assigned, has anyone requested a status
>update on it, I don't remember seeing anything? Maybe Scott is still
>working on it.
>As for Medium, I'm also not sure. This is a new feature, not a bug, I
>can see an argument for not releasing while there is a critical bug, but
> I can't see a case for holding a release because of a lack of a
>"critcal" new feature. Goes to "critical" in whose opinion? If it's not
>critical in the eyes of the release manager then it's not a release stopper.

View raw message