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 41FE145326 for ; Sat, 21 Jan 2023 21:36:40 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 6B2E468BAEB; Sat, 21 Jan 2023 23:36:37 +0200 (EET) Received: from relay10.mail.gandi.net (relay10.mail.gandi.net [217.70.178.230]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 4D519689B11 for ; Sat, 21 Jan 2023 23:36:31 +0200 (EET) Received: (Authenticated sender: michael@niedermayer.cc) by mail.gandi.net (Postfix) with ESMTPSA id 411A8240002 for ; Sat, 21 Jan 2023 21:36:29 +0000 (UTC) Date: Sat, 21 Jan 2023 22:36:29 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20230121213629.GZ1949656@pb2> References: <20230116133840.512-1-jamrial@gmail.com> <167407008302.4503.12911207010634660934@lain.khirnov.net> <20230120020509.GX1949656@pb2> <167431989409.26119.3043585718968218@lain.khirnov.net> MIME-Version: 1.0 In-Reply-To: <167431989409.26119.3043585718968218@lain.khirnov.net> Subject: Re: [FFmpeg-devel] [PATCH 00/26] Major library version bump 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="===============0626606298410159073==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============0626606298410159073== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ZuvoxmZMh0nHqhEq" Content-Disposition: inline --ZuvoxmZMh0nHqhEq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 21, 2023 at 05:51:34PM +0100, Anton Khirnov wrote: > Quoting Michael Niedermayer (2023-01-20 03:05:09) > > PS: iam not sure i fully understood the reason behind why versions shou= ld be > > set to "wrong" values during some period, so as always i might be missi= ng > > something >=20 > The reason is that after the major bump, the API and ABI are declared to > be unstable for some period, so people can freely > - break ABI, e.g. by reordering struct members > - modify API added during the instability period in an arbitrary way > without a new major bump for every such change, that would be normally > required. >=20 > My concern is that the instability period is quite long and there is > very little indication for our users that they cannot depend on the > ABI/API being stable. So I'm proposing to introduce some mechanism to > make this more visible for our callers. >=20 > Alternatively, we could just not have an instability period at all. Does anyone plan to use the next bumps instability period for anything ? If so, i assume theres a good reason why it cannot be done without such period easily? If theres noone -> easy solution, we need no instability period ATM. If theres someone, i would ask that someone how long it needs to be and write that down in APIchanges. Maybe as in "API is unstable becuase of X until 2033-11-11 a new #define LIBAVCODEC_UNSTABLE could be added but izt feels a bit overengeneered. This whole thing is more a exception, isnt it? thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB While the State exists there can be no freedom; when there is freedom there will be no State. -- Vladimir Lenin --ZuvoxmZMh0nHqhEq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCY8xa1gAKCRBhHseHBAsP q78BAJ4jovmzfsLhZQwE1s2jvEVF81WeawCfZp/pX2P7YS3M22kUO7CsEGenv+k= =rWSZ -----END PGP SIGNATURE----- --ZuvoxmZMh0nHqhEq-- --===============0626606298410159073== 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". --===============0626606298410159073==--