[FFmpeg-devel] Please do proper Release Candidates

James Almer jamrial at gmail.com
Thu Feb 27 23:25:28 EET 2025


On 2/27/2025 6:05 PM, Andrew Randrianasulu wrote:
> Otherwise it just feels like random snapshot everyone downstream must adapt
> to.

Does it make a difference? Every release is going to be a snapshot at 
some point in development. And how much testing is a release candidate 
going to get? Distros rarely if ever implement them.

Release branches are created days or weeks before a release is tagged, 
and in the meantime, fixes are backported. And of course, fixes keep 
being backported to be included in point releases.

> 
> Also, PLEASE add API changelog in future  release announcements on website,
> I want to see what broken in each release. Right now it looks like only
> "positive" end of news openly publicized. Be honest, post other end of news
> too.
News entries on the website for new releases mainly mention features, 
but i guess we could add a link to APIChanges in it.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20250227/25ac9cbb/attachment.sig>


More information about the ffmpeg-devel mailing list