db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@apache.org>
Subject Re: Existing application impact flag
Date Thu, 22 Feb 2007 23:25:30 GMT
Kathey Marsden wrote:
> Dan and I were discussing the existing application impact flag.  
> Typically this is set for intentional behaviour changes and also for 
> regresssions until they are fixed.  It was intended to provide an easy 
> report for those upgrading to know what changes might affect their 
> applications on upgrade.
> Dan suggested that the "existing application impact"  field would be 
> better split into two fields. One for intentional changes and another 
> for bugs that might affect existing applications.  I kind of like it the 
> way it is.  Does anyone have thoughts on this?

Or I thought it was already split into two flags:

    regression - a regression from a previous release
    existing application impact - an intentional change that might 
require application change


View raw message