From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 083CE48E60 for ; Mon, 29 Jan 2024 12:41:48 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id F182468D1F8; Mon, 29 Jan 2024 14:41:45 +0200 (EET) Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1B8AC68D060 for ; Mon, 29 Jan 2024 14:41:40 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 1F7B040005 for ; Mon, 29 Jan 2024 12:41:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1706532099; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Mv9G+0+N7fY5cijxaPkQEJr2CAuUsOdD7Ch6sJ0wR5Y=; b=mwn8Rrkm5qBoKRSWW/JRb720PT1YjM63oFx7c3YgZyOE6D65YbwMJVmo3d0n7hvvxycS2f ju6+VPPq25aG741wvRpxW4FsIJNQ/mTIcrboBYtPF3CFPZseq7+5ByRAQl8djyUdoKSP4U s+ao9XkaXXhbjNOfm8Ss825vjw2JFOpqEcixEQkQVODNGJzv2Gw/pNPn/2jUhfhTVPcuq1 9koVIInc0l3wWyGhopX141GPthFxveE2BsHp6VqFja5ec4Ti3YNp4iGAoUDujHMB68Yix1 YW/jC9uzYfljSCALRlAO4R6e8zCgjsIw/YtFspHe1SIZF7QU4ksBApGPvCYhGA== Date: Mon, 29 Jan 2024 13:41:38 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240129124138.GW6420@pb2> References: <20240128122944.10889-1-anton@khirnov.net> <20240128224706.GU6420@pb2> MIME-Version: 1.0 In-Reply-To: X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [RFC/PATCH] doc/developer: clarify the criterion for removing deprecated APIs X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============6571404124902449461==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============6571404124902449461== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3e1ACokgasLb/0VD" Content-Disposition: inline --3e1ACokgasLb/0VD Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 29, 2024 at 10:31:02AM +0100, Vittorio Giovara wrote: > On Sun, Jan 28, 2024 at 11:47=E2=80=AFPM Michael Niedermayer > wrote: >=20 > > On Sun, Jan 28, 2024 at 01:28:36PM +0100, Anton Khirnov wrote: > > > Previously, the implicit standard was to wait 2 years before deprecat= ion > > > and removal, but it has been widely agreed at developer meetings that > > > time-based measures do not make sense and we should switch to a > > > release-based one instead. > > > --- > > > Feel welcome to argue for other numbers than 2, or suggest alternative > > > criteria, but please try to limit bikeshedding. > > > --- > > > doc/developer.texi | 3 ++- > > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > > > diff --git a/doc/developer.texi b/doc/developer.texi > > > index dd96e3b36a..3f3218f66a 100644 > > > --- a/doc/developer.texi > > > +++ b/doc/developer.texi > > > @@ -552,7 +552,8 @@ the negative effects on our callers, who are > > required to adapt their code, > > > backward-incompatible changes during a major bump should be limited = to: > > > @itemize @bullet > > > @item > > > -Removing previously deprecated APIs. > > > +Removing APIs that were marked as deprecated in at least two previous > > > +major releases. > > > > Removing APIs that were marked as deprecated in at least two previous > > major releases for at least 1 year. > > > > (goal of this proposed difference is to ensure that if for whatever rea= son > > we make several major releases in quick succession it doesnt deprecate > > things faster) > > >=20 > IMO that's a bit verbose and given language is not precise it could lead = to > confusion (at least 1 year from deprecation? from a release with a > deprecation warning? a mix of the two?) You can suggest clearer language. The advanagte of including a time period is that its easier for people to plan things, as they know how long they can depend on an API. thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I know you won't believe me, but the highest form of Human Excellence is to question oneself and others. -- Socrates --3e1ACokgasLb/0VD Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZbec/gAKCRBhHseHBAsP q66tAJ0bEHqvsaEg1YBYgirL0oH2n1NC4gCfU+VHwq8m0ObVnLdaeFcJxHOTW8U= =DYuB -----END PGP SIGNATURE----- --3e1ACokgasLb/0VD-- --===============6571404124902449461== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". --===============6571404124902449461==--