Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] FFmpeg 8.0 Release
Date: Wed, 23 Jul 2025 21:38:16 -0300
Message-ID: <6e732ec5-65d8-4357-92a9-bd9b58563b0c@gmail.com> (raw)
In-Reply-To: <20250723160145.GD1393756@haasn.xyz>


[-- Attachment #1.1.1: Type: text/plain, Size: 2132 bytes --]

On 7/23/2025 11:01 AM, Niklas Haas wrote:
> On Wed, 23 Jul 2025 16:01:14 +0200 Niklas Haas <ffmpeg@haasn.xyz> wrote:
>> On Wed, 23 Jul 2025 13:43:43 +0200 Michael Niedermayer <michael@niedermayer.cc> wrote:
>>> Hi everyone
>>>
>>> I intend to create the release/8.0 branch in the next 1-2 weeks
>>> after that i intend to make teh 8.0 release in the following 1-2 weeks
>>>
>>> If theres something you want in it make sure its pushed before the branch
>>> is made.
>>>
>>> And if theres a bugfix that you want included make sure it either hits
>>> master before the branch point or cherry pick it into release/8.0
>>> before the release
>>>
>>> Also name ideas as always are welcome, will choose teh one with most
>>> votes. If theres a tie, i plan to vote last so i can break ties
>>
>> When can we formally remove YUV pixel formats?

It's an ABI break, so when we bump major soname, which we'd do early 
next year.

> 
> I of course meant to write YUVJ, although formally removing YUV would make our
> lives easier too.

How so?

> 
>>
>> As far as I'm aware, nothing is blocking this, we just need to break the
>> ABI for it. When is the best time to do that?
>>
>>>
>>> thx
>>>
>>> --
>>> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>>>
>>> The real ebay dictionary, page 1
>>> "Used only once"    - "Some unspecified defect prevented a second use"
>>> "In good condition" - "Can be repaird by experienced expert"
>>> "As is" - "You wouldnt want it even if you were payed for it, if you knew ..."
>>> _______________________________________________
>>> 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".
> _______________________________________________
> 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".


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 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".

      reply	other threads:[~2025-07-24  0:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 11:43 Michael Niedermayer
2025-07-23 13:45 ` Timo Rothenpieler
2025-07-23 16:27   ` Michael Niedermayer
2025-07-23 16:43     ` Dimitry Andric
2025-07-23 17:48       ` Michael Niedermayer
2025-07-23 18:19         ` Jacob Lifshay
2025-07-24  0:16           ` Michael Niedermayer
2025-07-23 18:40         ` Nicolas George
2025-07-23 23:58           ` Michael Niedermayer
2025-07-23 14:01 ` Niklas Haas
2025-07-23 14:01   ` Niklas Haas
2025-07-24  0:38     ` James Almer [this message]

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=6e732ec5-65d8-4357-92a9-bd9b58563b0c@gmail.com \
    --to=jamrial@gmail.com \
    --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