[RFC][POLICY] Immediately use the new API in ffmpeg
Hi guys, I'd like to make a request to the policy: Every time an API is deprecated, I'd like to add the rule that developers must immediately use the new API in ffmpeg/ffplay/ffserver tools. My question is why is the old swscale API still used ? -- Baptiste COUDURIER Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA FFmpeg maintainer http://www.ffmpeg.org
On Sat, Nov 20, 2010 at 3:21 PM, Baptiste Coudurier <baptiste.coudurier at gmail.com> wrote:
Hi guys,
I'd like to make a request to the policy:
Every time an API is deprecated, I'd like to add the rule that developers must immediately use the new API in ffmpeg/ffplay/ffserver tools.
Actually, I would say further that, for the cases of new API functions intended to replace older ones, such new functions should not even be made public until ffmpeg/ffplay/ffserver modifications are ready. ff* apps should be the first testbed for new APIs, not the last. Jason
On Sat, Nov 20, 2010 at 03:26:12PM -0800, Jason Garrett-Glaser wrote:
On Sat, Nov 20, 2010 at 3:21 PM, Baptiste Coudurier <baptiste.coudurier at gmail.com> wrote:
Hi guys,
I'd like to make a request to the policy:
Every time an API is deprecated, I'd like to add the rule that developers must immediately use the new API in ffmpeg/ffplay/ffserver tools.
i agree that people should not add new code using old apis.Requiring a strict "you must update all use of an old API" would add additional burden on the very few that work on improving the APIs Its a goal we should aim toward but the time and motivation each person has available should dictate in the end how far things are converted. Half finished code should not rot in private repos for years if it does no harm if commited and allows others to finish it.
Actually, I would say further that, for the cases of new API functions intended to replace older ones, such new functions should not even be made public until ffmpeg/ffplay/ffserver modifications are ready.
ff* apps should be the first testbed for new APIs, not the last.
i approximately agree but i think there are 2 seperate things that is 1. an API being experimental vs final 2. all uses being converted to the new API in case os swscale the new api is still experimental and it wasntg me pushing it to the public and deprecating the old even if i probably approved it i remember not feeling too well about it [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I have never wished to cater to the crowd; for what I know they do not approve, and what they approve I do not know. -- Epicurus
Hi, On Sat, Nov 20, 2010 at 11:31 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
i agree that people should not add new code using old apis.Requiring a strict "you must update all use of an old API" would add additional burden on the very few that work on improving the APIs Its a goal we should aim toward but the time and motivation each person has available should dictate in the end how far things are converted. Half finished code should not rot in private repos for years if it does no harm if commited and allows others to finish it.
Why not write SoC qualification tasks (depending on difficulty), or add them to the wiki small task list? Right now nobody knows how many uses we have of each old deprecated API. Ronald
On Sun, Nov 21, 2010 at 07:27:56AM -0500, Ronald S. Bultje wrote:
Hi,
On Sat, Nov 20, 2010 at 11:31 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
i agree that people should not add new code using old apis.Requiring a strict "you must update all use of an old API" would add additional burden on the very few that work on improving the APIs Its a goal we should aim toward but the time and motivation each person has available should dictate in the end how far things are converted. Half finished code should not rot in private repos for years if it does no harm if commited and allows others to finish it.
Why not write SoC qualification tasks (depending on difficulty), or add them to the wiki small task list?
Right now nobody knows how many uses we have of each old deprecated API.
make | grep deprecated or something like this should tell all uses of old APIs [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Avoid a single point of failure, be that a person or equipment.
On date Saturday 2010-11-20 15:21:32 -0800, Baptiste Coudurier encoded: [...]
My question is why is the old swscale API still used ?
Because there are some changes that need to be done in libavcodec before the new API can be employed without regressions. Feel free to remove the deprecation on the old API until someone (where hopefully is someone != me) will fix those problems. -- FFmpeg = Faithful & Faithful Meaningful Pacific Energized Gangster
participants (5)
-
baptiste.coudurier@gmail.com -
jason@x264.com -
michaelni@gmx.at -
rsbultje@gmail.com -
stefano.sabatini-lala@poste.it