From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] FFmpeg 5.2 ?
Date: Thu, 3 Nov 2022 19:26:29 -0300
Message-ID: <c31ab08e-4a51-1587-116a-ef368328e788@gmail.com> (raw)
In-Reply-To: <20221103215911.GL1814017@pb2>
On 11/3/2022 6:59 PM, Michael Niedermayer wrote:
> Hi all
>
> do we want a release/5.2 branch made in december ?
>
> I think that would be what previous release shedule suggestions would
> point to
>
> thx
Changelog looks a tad short post 5.1, but i guess there has been more
work in refactoring and improving existing code than adding new features
that get mentioned there.
Also, afaik Debian freeze is in January, and i think it'd be best for us
if they go with 5.1, the release we declared LTS, than if they end up
going with 5.2 and thus force our hand to treat it as one too. So we
might want to postpone a new release until late January or February. It
would also give us time to decide if we do a major soname bump for it
too, to get rid of deprecated API that could be constraining new work (I
think Anton wanted some gone soon for that reason).
_______________________________________________
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-03 22:26 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 [this message]
2022-11-04 10:30 ` Jean-Baptiste Kempf
2022-11-04 14:09 ` Michael Niedermayer
2022-11-04 14:33 ` Artem Galin
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=c31ab08e-4a51-1587-116a-ef368328e788@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