Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andrew Sayers <ffmpeg-devel@pileofstuff.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 7.0 blocking issues
Date: Tue, 4 Jun 2024 09:34:52 +0100
Message-ID: <Zl7RrMKft3P_yFg5@andrews-2024-laptop.sayers> (raw)
In-Reply-To: <20240603213237.GC2821752@pb2>

On Mon, Jun 03, 2024 at 11:32:37PM +0200, Michael Niedermayer wrote:
> On Sun, Jun 02, 2024 at 03:49:42PM +0200, Sebastian Ramacher wrote:
[...]
> > Just as a FYI: ffmpeg 7.0 breaks close to 70 reverse dependencies in
> > Debian. The list is available at [1]. So if you want ffmpeg X to be in
> > Debian Y or Ubuntu Z, X needs to be released at least half a year before
> > Y or Z freeze.
> 
> Is there something that ffmpeg can do to reduce this breakage ?
> (i know its a bit of a lame question as its API brekages but i mean
> can the policy we have about deprecating API/ABI be amended in some way
> to make this easier ?

A quick look through Sebastian's list suggests two main groups of issues:

* channel layout migration
* things that didn't have attribute_deprecated before being removed

There are probably ways to reduce migration issues (e.g. Anton's point about
frequent small changes), but the quick win is to use attribute_deprecated more.

To be clear - attribute_deprecated is already used a lot.  If those messages
were being ignored, we would expect to see more bugs reported for those things.
The fact that channel layout is the only deprecated functionality to get this
far suggests that attribute_deprecated is a good way to notify people about
all but the largest changes.

> Also am i correct that it should be easier if a X.1 with same API/ABI that is
> released 6 month after X.0 is targetet for the release ? Thats in fact kind
> of what i would have preferred anyway as the .1 likely has also fewer bugs
> 
> And last but not least, someone needs to write down when .0 and .1 releases should
> be made so I dont forget it :)

Whatever decision is made about this, it would be good to update the
attribute_deprecated macro to point to a URL that lays out the policy.
Something like:

#define attribute_deprecated __attribute__((deprecated("see <url> for details")))
_______________________________________________
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".

  parent reply	other threads:[~2024-06-04  8:35 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 19:22 Michael Niedermayer
2024-01-23 20:18 ` Lynne
2024-01-24  7:40   ` Anton Khirnov
2024-01-24 12:07     ` Lynne
2024-01-24 12:30       ` Anton Khirnov
2024-01-24 13:14         ` Lynne
2024-01-24 13:24           ` Anton Khirnov
2024-01-24 13:36             ` Lynne
2024-01-24 12:28     ` James Almer
2024-01-24  7:45 ` Anton Khirnov
2024-01-24 12:29   ` James Almer
2024-01-24 12:45 ` Niklas Haas
2024-01-28 10:38   ` Anton Khirnov
2024-01-24 13:59 ` Kieran Kunhya
2024-02-07 14:54 ` Derek Buitenhuis
2024-02-09  3:32   ` Michael Niedermayer
2024-02-12 15:36     ` Derek Buitenhuis
2024-02-07 18:49 ` Leo Izen
2024-02-07 18:56   ` Andreas Rheinhardt
2024-02-08  1:27     ` Leo Izen
2024-02-08  2:20       ` James Almer
     [not found] ` <2E182D4F-95D4-43F7-A772-A737003B3C79@cosmin.at>
2024-02-07 18:55   ` Cosmin Stejerean via ffmpeg-devel
2024-02-10 21:03 ` James Almer
2024-02-11  1:35   ` Michael Niedermayer
2024-02-11  5:53     ` Nuo Mi
2024-02-25 23:18 ` Michael Niedermayer
2024-02-25 23:20   ` James Almer
2024-02-26 21:26     ` Michael Niedermayer
2024-03-02 22:55 ` Michael Niedermayer
2024-03-02 23:06   ` Sebastian Ramacher
2024-03-02 23:19     ` Michael Niedermayer
2024-03-03  1:39       ` Sean McGovern
2024-03-03  8:55         ` Sebastian Ramacher
2024-06-02 13:49           ` Sebastian Ramacher
2024-06-03 21:32             ` Michael Niedermayer
2024-06-03 21:36               ` Sean McGovern
2024-06-03 21:41               ` James Almer
2024-06-04  1:16                 ` Michael Niedermayer
2024-06-04  7:23                   ` Vittorio Giovara
2024-06-04  7:46                   ` Anton Khirnov
2024-06-04  6:31                 ` Rémi Denis-Courmont
2024-06-04  9:29                   ` Sebastian Ramacher
2024-06-05 10:55                 ` Kacper Michajlow
2024-06-04  8:34               ` Andrew Sayers [this message]
2024-06-04  9:19               ` Sebastian Ramacher
2024-03-03  7:35   ` Jean-Baptiste Kempf
2024-03-03 12:35     ` James Almer
2024-03-08 14:00     ` James Almer
2024-03-08 14:02       ` Kieran Kunhya
2024-03-08 14:04         ` James Almer
2024-03-08 15:04           ` Frank Plowman
2024-03-08 15:40             ` Kieran Kunhya
2024-03-09 12:33               ` Nuo Mi
2024-03-09 18:31                 ` Marth64
2024-03-10 13:25                   ` Xiang, Haihao
2024-03-10 23:29       ` Michael Niedermayer

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=Zl7RrMKft3P_yFg5@andrews-2024-laptop.sayers \
    --to=ffmpeg-devel@pileofstuff.org \
    --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