On 06/08/15 23:26, Andreas Cadhalpun wrote: > I'm seeing more dramatic words than good arguments in your mail.
Could we please tune it down a little? The summary so far is that the people in Libav do not want to do again three time the extra miles. This time will be up to the downstreams to take care of it and will be up to the distributor do the distributor job and update the packets or prod downstreams. The deprecated APIs will keep getting used till they do not disappear, I know quite well since my downstream projects will get some updates that I postponed till now because "hey they are easy I can do once I have a moment" for... well more than 2 years... For this release the deprecated APIs will be dropped w/out a third warning, if nobody does not provide an alternate patchset and there isn't consensus in doing otherwise. The even-odd pace had been agreed during the last two meetings. For the next release probably we can make so the odd release does win a trigger --enable-future that makes all the apis slated to drop in the even release disappear for that build. I will make so that the libav-9999 build in Gentoo will have a +future use flag (as in always on until disabled). I know that probably is not great for you, but... Well, I can't blame anybody for not wasting their time on a thankless and partially fruitless effort, there is tons of new and interesting code to be written instead =) lu _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
