From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC/PATCH] doc/developer: clarify the criterion for removing deprecated APIs
Date: Sun, 28 Jan 2024 23:47:06 +0100
Message-ID: <20240128224706.GU6420@pb2> (raw)
In-Reply-To: <20240128122944.10889-1-anton@khirnov.net>
[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]
On Sun, Jan 28, 2024 at 01:28:36PM +0100, Anton Khirnov wrote:
> Previously, the implicit standard was to wait 2 years before deprecation
> 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 reason
we make several major releases in quick succession it doesnt deprecate
things faster)
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Everything should be made as simple as possible, but not simpler.
-- Albert Einstein
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
next prev parent reply other threads:[~2024-01-28 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 12:28 Anton Khirnov
2024-01-28 22:47 ` Michael Niedermayer [this message]
2024-01-29 9:31 ` Vittorio Giovara
2024-01-29 12:41 ` Michael Niedermayer
2024-01-29 10:55 ` Anton Khirnov
2024-01-29 11:20 ` Andrew Randrianasulu
2024-01-29 12:47 ` Michael Niedermayer
2024-01-29 17:20 ` Anton Khirnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240128224706.GU6420@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git