[Bugzilla] and [AppDB] add ability to mark Wine versions as 'obsolete', 'supported' or 'current'

Jeremy Newman jnewman at codeweavers.com
Mon Oct 31 09:27:02 CST 2005

Curious. The more we diverge our Bugzilla from the mainline Bugzilla,
the harder it will be for us to upgrade. I've had requests to get us up
to the latest release. But I'm fearful of the amount of work it will be
to clean it up once the merge is complete.

That and the last time I upgraded Bugzilla the upgrade process deleted
all the comments from the DB. (Note: not a problem anymore as we keep
good DB backups.)

Maybe someone with more time can look into keeping our Bugzilla current
and maintain our patches.

On Sat, 2005-10-29 at 16:24 -0600, Tony Lambregts wrote:
> This patch is meant to stimulate a discussion about how to deal with the 
> fact we cannot reasonable support obsolete versions of wine ;^)
> For example we  would like to be able to age Test Results and probably 
> do not want submittions of test results or bugs that are from older 
> versions of wine. On the other hand we should accept new  bug reports 
> from CVS and at least our current release. Since we cannot simply delete 
> old versions in bugzilla I came up the following patch.
> To use this patch you need to run the following sql:
> use bugs;
> alter table versions add column status 
> enum('obsolete','supported','current') NOT NULL default 'current';
> change log: Add status ('obsolete','supported' or 'current') to versions 
> table

More information about the wine-devel mailing list