* [FFmpeg-devel] Please do proper Release Candidates
@ 2025-02-27 21:05 Andrew Randrianasulu
2025-02-27 21:25 ` James Almer
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Randrianasulu @ 2025-02-27 21:05 UTC (permalink / raw)
To: FFmpeg development discussions and patches
Otherwise it just feels like random snapshot everyone downstream must adapt
to.
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.
_______________________________________________
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".
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [FFmpeg-devel] Please do proper Release Candidates
2025-02-27 21:05 [FFmpeg-devel] Please do proper Release Candidates Andrew Randrianasulu
@ 2025-02-27 21:25 ` James Almer
0 siblings, 0 replies; 2+ messages in thread
From: James Almer @ 2025-02-27 21:25 UTC (permalink / raw)
To: ffmpeg-devel
[-- Attachment #1.1.1: Type: text/plain, Size: 911 bytes --]
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.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-02-27 21:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-02-27 21:05 [FFmpeg-devel] Please do proper Release Candidates Andrew Randrianasulu
2025-02-27 21:25 ` James Almer
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