[FFmpeg-devel] maintainer duties (was: Re: [PATCH] fix speex sample)
Fri Apr 10 19:38:48 CEST 2009
On Fri, Apr 10, 2009 at 07:26:56PM +0200, Diego Biurrun wrote:
> On Thu, Apr 09, 2009 at 04:15:01PM +0200, Diego Biurrun wrote:
> > I think maintainers should (in descending order of priorities)
> > 1) review patches,
> > 2) fix bugs and
> > 3) implement missing features
> One thing I forgot:
> 0) Keep their code working and current.
> I mean things like exchanging deprecated functions for their
> replacements etc.
yes, let me just add that all the
0..3 have their easy, hard and insanely hard to implement cases
and in the case of replacing old by new, if a single developer doesnt have
the resources to replace all instances by the new there are only 2 choices
A. do nothing, new code still will then use the old system
B. add the new and replace what can be replaced with the available resources
I think B is pretty much universally better
now one could add the new API, but not mark the old as
deprecated, but doing this means people will use the old in newly added
code, which is not good.
What both you and I seem to want is to hide the warnings about deprecated
stuff in existing code without hiding them for new code.
Maybe that could be done with some Makefile magic i dont know ...
Either way lets not fight about which of 2 bad solutions is better, rather
lets find a solution that isnt bad. (that is if i guessed correctly what
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Concerning the gods, I have no means of knowing whether they exist or not
or of what sort they may be, because of the obscurity of the subject, and
the brevity of human life -- Protagoras
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
More information about the ffmpeg-devel