On Sun, 2011-12-18 at 19:42 +0100, Janne Grunau wrote: > On 2011-12-18 21:37:37 +0200, Uoti Urpala wrote: > > On Sun, 2011-12-18 at 19:22 +0000, Måns Rullgård wrote: > > > > > The next release will have the field marked deprecated, and the one > > > after that will remove it. That's how we roll. > > > > I have no objection to that. But it doesn't require you to start > > immediately spamming warnings even _before_ that next release (if > > there's still a full release cycle left after that before it's really > > necessary to change). You could use deprecated_avcodec54 or something > > like that to only start enabled-by-default deprecation warnings under > > that major version. > > That would require two major bumps to remove something. Please note > that we haven't done and don't plan to do one major bump per release.
You could of course use something other than major version as the trigger (such as release count), so that should not be an issue. I think that at the current deprecation rate, following the policy mentioned above would result in symbol/field removals requiring major bumps for the next releases anyway though. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
