From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 5.0 LTS vs 5.1 LTS
Date: Mon, 25 Apr 2022 10:01:01 +0200
Message-ID: <CAPYw7P4xqBVVGqgtr3+ERDg_LOwR-LJcPjUpSk7_T8id7tyZzg@mail.gmail.com> (raw)
In-Reply-To: <DM8P223MB0365D5A4D8B979426C40B623BAF99@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
On Mon, Apr 25, 2022 at 12:48 AM Soft Works <softworkz@hotmail.com> wrote:
>
>
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > Michael Niedermayer
> > Sent: Saturday, April 23, 2022 6:36 PM
> > To: FFmpeg development discussions and patches <ffmpeg-
> > devel@ffmpeg.org>
> > Subject: [FFmpeg-devel] FFmpeg 5.0 LTS vs 5.1 LTS
> >
> > Hi all
> >
> > Do people prefer that 5.0 becomes LTS or the next (5.1) ?
> > Or something else ?
>
> @Anton - I'm wondering how your multi-threading transformations
> to ffmpeg.c would align with the release schedule?
>
> I think an LTS release should be either before or after the
> series of changes you are planning. It would be unfortunate
> when 5.1 would be somewhere in the middle of those changes
> and become LTS.
> (as you said it could take a year in the worst case)
>
>
I'm still expecting info that you said to provide.
> Thanks,
> softworkz
> _______________________________________________
> 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-04-25 7:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 16:36 Michael Niedermayer
2022-04-23 16:40 ` James Almer
2022-04-23 18:08 ` Neal Gompa
2022-04-23 18:14 ` James Almer
2022-04-23 18:17 ` Neal Gompa
2022-04-24 9:18 ` Gyan Doshi
2022-04-24 9:55 ` Steven Liu
2022-04-24 22:48 ` Soft Works
2022-04-25 8:01 ` Paul B Mahol [this message]
2022-04-25 9:04 ` Soft Works
2022-04-25 11:51 ` Jean-Baptiste Kempf
2022-04-25 17:19 ` Michael Niedermayer
2022-04-25 18:04 ` Jean-Baptiste Kempf
2022-04-25 18:40 ` Michael Niedermayer
2022-04-25 19:40 ` Soft Works
2022-04-25 19:44 ` Jean-Baptiste Kempf
2022-04-26 13:32 ` Michael Niedermayer
2022-04-25 18:38 ` James Almer
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=CAPYw7P4xqBVVGqgtr3+ERDg_LOwR-LJcPjUpSk7_T8id7tyZzg@mail.gmail.com \
--to=onemda@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