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] 5.0 release
Date: Wed, 22 Dec 2021 11:05:55 -0300
Message-ID: <123bc8cf-2486-26ec-8c80-51815ccef543@gmail.com> (raw)
In-Reply-To: <20211222140322.GC2829255@pb2>



On 12/22/2021 11:03 AM, Michael Niedermayer wrote:
> On Mon, Dec 13, 2021 at 07:05:07PM +0100, Jean-Baptiste Kempf wrote:
>> On Mon, 13 Dec 2021, at 16:25, Michael Niedermayer wrote:
>>> If you know of any major issues which need to be done before the release do them
>>> now. If you know of any issues which are release-blocking list them in a reply
>>> here please.
>>
>> Maybe the audio channel layout would be nice to settle before?
> 
> iam not sure we will achieve a december 2021 release if we want to
> include that
> 
> anyone has an opinion if we should wait with the release until this
> is in ?
> 
> thx

Is the December target to get into the feature freeze schedule from 
distros? If so, then IMO better make the release now. The channel layout 
API is unlikely to be committed before the end of the year.
_______________________________________________
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:[~2021-12-22 14:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211125171932.GC2829255@pb2>
     [not found] ` <20211213152557.GL2829255@pb2>
     [not found]   ` <CABcAi1jFnkGd-dyLy_iOHhKEVUz=OPYXp23X326_6okM+zW8Aw@mail.gmail.com>
     [not found]     ` <20211214161924.GM2829255@pb2>
     [not found]       ` <CABcAi1h45bkw4rmYJYEJrEaqOybbFvqXZFAAJ6F5=Mo4+BPHVg@mail.gmail.com>
2021-12-15 14:52         ` Michael Niedermayer
2021-12-15 15:08           ` Diederick C. Niehorster
2021-12-15 15:15             ` Michael Niedermayer
     [not found]   ` <3238136b-1f43-49ae-b2d6-ce98b98e24f0@www.fastmail.com>
2021-12-22 14:03     ` Michael Niedermayer
2021-12-22 14:05       ` James Almer [this message]
2021-12-22 16:44         ` Jean-Baptiste Kempf
2021-12-27 23:55           ` Michael Niedermayer
2021-12-31 16:52             ` Michael Niedermayer
2021-12-31 17:15               ` Gyan Doshi
2021-12-31 19:40                 ` Michael Niedermayer
2022-01-02 14:12                   ` Anton Khirnov
2022-01-02 14:29                     ` James Almer
2022-01-02 14:50                       ` Zane van Iperen
2022-01-02 15:09                         ` James Almer
2022-01-02 15:52                           ` Zane van Iperen
2022-01-02 16:28                             ` Lynne
2022-01-02 17:11                               ` Michael Niedermayer
2022-01-02 18:12                                 ` Lynne
2022-01-02 22:29                                   ` Michael Niedermayer
2022-01-02 22:32                                     ` Michael Niedermayer
2022-01-03  5:31                   ` Jean-Baptiste Kempf
2022-01-03 16:14                     ` Michael Niedermayer
2022-01-03 17:17                       ` Hendrik Leppkes
2022-01-03 17:19                         ` Hendrik Leppkes
2022-01-03 18:04                         ` Paul B Mahol
2022-01-03 18:58                           ` Michael Niedermayer
2022-01-03 19:25                             ` Paul B Mahol
2022-01-03 20:14                               ` Michael Niedermayer
2022-01-03 20:29                                 ` Paul B Mahol
2022-01-03 20:36                                   ` Michael Niedermayer
2022-01-03 19:23                       ` Michael Niedermayer
2022-01-04  2:11                     ` Soft Works
2021-12-31 19:08               ` Lynne

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=123bc8cf-2486-26ec-8c80-51815ccef543@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