I suggest the guideline that database items be obsolete for at least two releases before they get removed. For example, anything that was last used in 0.15, can't be removed until 0.17 is released.
How do you handle data whose meaning changes, though?
In a perfect world, there would be a new table, column, or value to represent the new meaning(s). In the MythTV dev world, I guess we have to hope that developers minimise this?
-- Nigel Pearson, [EMAIL PROTECTED] | "Reality is that which, Telstra BI&D, Sydney, Australia | when you stop believing Office: 8255 4222 Fax: 8255 3153 | in it, doesn't go away." Mobile: 0408 664435 Home: 9792 6998 | Philip K. Dick - 'Valis'
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
