From: Artem Galin <artem.galin@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 5.2 ?
Date: Fri, 4 Nov 2022 14:33:30 +0000
Message-ID: <CANGqAjJOwiHh9OEBXmWYChTqK9HZKPR-y0pAhjgbw2V7dSOPUQ@mail.gmail.com> (raw)
In-Reply-To: <20221104140951.GO1814017@pb2>
DTS to PTS reorder bsf, threading changes, ddagrab, oneVPL support with AV1 HW
encode for new ARC Gfx as well as DX11 for QSV are valuable items for next
5.2 release
On Fri, 4 Nov 2022 at 14:10, Michael Niedermayer <michael@niedermayer.cc>
wrote:
> On Fri, Nov 04, 2022 at 11:30:38AM +0100, Jean-Baptiste Kempf wrote:
> > On Thu, 3 Nov 2022, at 22:59, Michael Niedermayer wrote:
> > > do we want a release/5.2 branch made in december ?
> >
> > Based on what? Master or 5.1?
>
> new release branches are cut from master
> it seems not a great idea ATM though so iam asking what people want
> as the previous plans where for one in december. These plans just
> dont seem that great with the LTS prior
>
> So question for december is:
> 5.2 in December / 5.2 in June / 5.2 in January
>
> and then next we could do: (if we go with 2 releases per year)
> [5.3 would be 5.2 in the 5.2 june case]
> A B C
> 2023 june 5.3 / 5.3 LTS / 6.0
> 2023 december 5.4 LTS / 5.4 / 6.1 LTS
>
> anyone has any other suggestions / comments?
>
> thx
>
>
> [...]
>
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Awnsering whenever a program halts or runs forever is
> On a turing machine, in general impossible (turings halting problem).
> On any real computer, always possible as a real computer has a finite
> number
> of states N, and will either halt in less than N cycles or never halt.
> _______________________________________________
> 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".
next prev parent reply other threads:[~2022-11-04 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 21:59 Michael Niedermayer
2022-11-03 22:26 ` James Almer
2022-11-04 10:30 ` Jean-Baptiste Kempf
2022-11-04 14:09 ` Michael Niedermayer
2022-11-04 14:33 ` Artem Galin [this message]
2022-11-04 14:36 ` Paul B Mahol
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=CANGqAjJOwiHh9OEBXmWYChTqK9HZKPR-y0pAhjgbw2V7dSOPUQ@mail.gmail.com \
--to=artem.galin@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