Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Website release notes for 6.0
Date: Tue, 28 Feb 2023 22:13:42 +0100 (CET)
Message-ID: <NPOrvuW--3-9@lynne.ee> (raw)
In-Reply-To: <20230228194733.GG1949656@pb2>

Feb 28, 2023, 20:47 by michael@niedermayer.cc:

> Hi
>
> On Tue, Feb 28, 2023 at 08:44:01PM +0100, Marton Balint wrote:
>
>>
>>
>> On Tue, 28 Feb 2023, Lynne wrote:
>>
>> > Feb 28, 2023, 10:59 by dev@lynne.ee:
>> > 
>> > > Feb 28, 2023, 10:41 by dev@lynne.ee:
>> > > 
>> > > > Wrote the release notes for 6.0, containing an
>> > > > explanation of the new releases/ABI bump details,
>> > > > and an overview of what has changed.
>> > > > 
>> > > > Patch attached.
>> > > > 
>> > 
>> > Ping, release has been tagged for quite a while now.
>> > Final version:
>> > 
>> >     A new major release, <a href="download.html#release_6.0">FFmpeg 6.0 "Von Neumann"</a>,
>> >     is now available for download. This release has many new encoders and decoders, filters,
>> >     ffmpeg CLI tool improvements, and also, changes the way releases are done. All major
>> >     releases will now bump the version of the ABI. We plan to have a new major release each
>> >     year. Another release-specific change is that deprecated APIs will be removed after 3
>> >     releases, upon the next major bump. The last minor release of a major version will be an
>> >     LTS release.
>>
>> For some reason LTS releases were only planned for every second year:
>>
>> https://ftp.belnet.be/mirror/FOSDEM/video/2023/K.3.401/om_vlc.webm#t=724
>>
>> So I'd remove the last sentence until this is clarified.
>>
>
> patch LGTM with the change
>

Applied the change and pushed, thanks
_______________________________________________
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:[~2023-02-28 21:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28  9:41 Lynne
     [not found] ` <NPMOV34--3-9@lynne.ee-NPMOZAh--7-9>
2023-02-28  9:59   ` Lynne
     [not found]   ` <NPMSbWa--3-9@lynne.ee-NPMSeu1--3-9>
2023-02-28 14:52     ` Lynne
2023-02-28 19:44       ` Marton Balint
2023-02-28 19:47         ` Michael Niedermayer
2023-02-28 21:13           ` Lynne [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=NPOrvuW--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --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