Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Please do proper Release Candidates
Date: Thu, 27 Feb 2025 18:25:28 -0300
Message-ID: <0da23c6a-78a2-40d1-a898-67bcfbd18be9@gmail.com> (raw)
In-Reply-To: <CA+rFky74Qo1oUYM5CH0MHpv0kEWBEmNZJq+JAZAzAKyzgndU8g@mail.gmail.com>


[-- 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".

      reply	other threads:[~2025-02-27 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 21:05 Andrew Randrianasulu
2025-02-27 21:25 ` James Almer [this message]

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=0da23c6a-78a2-40d1-a898-67bcfbd18be9@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