From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] RELEASE_NOTES: Based on the version from 5.0
Date: Wed, 20 Jul 2022 17:28:26 +0200
Message-ID: <20220720152826.GC2088045@pb2> (raw)
In-Reply-To: <CADQbU6_AZDTKgdpp=bjrgKbQK5AWTmK86baR-8fhtnHqyTZo3w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1036 bytes --]
On Sun, Jul 17, 2022 at 10:01:19AM +0200, Martijn van Beurden wrote:
> Op zo 17 jul. 2022 om 00:50 schreef Michael Niedermayer <
> michael@niedermayer.cc>:
>
> > ATM we have to maintain many releases because each is used by some distro
> > the LTS designation might cause distros to coalescence onto fewer releases
> > This may also make life easier to distro maintainers
> >
>
> Then maybe this can be placed in the release notes
>
> + The FFmpeg Project proudly presents FFmpeg 5.1 "Riemann" LTS, about 6
> + months after the release of FFmpeg 5.0, our first Long Term Support
> + release. While several past FFmpeg releases have enjoyed long term
> support,
> + this is the first release where such an intention is made clear at
> release.
will apply with this change
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
"Nothing to hide" only works if the folks in power share the values of
you and everyone you know entirely and always will -- Tom Scott
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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".
next prev parent reply other threads:[~2022-07-20 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 15:09 Michael Niedermayer
2022-07-16 20:05 ` Martijn van Beurden
2022-07-16 20:35 ` Michael Niedermayer
2022-07-16 21:02 ` Martijn van Beurden
2022-07-16 22:50 ` Michael Niedermayer
2022-07-17 8:01 ` Martijn van Beurden
2022-07-20 15:28 ` Michael Niedermayer [this message]
2022-07-17 8:43 ` Jean-Baptiste Kempf
2022-07-17 14:23 ` Michael Niedermayer
2022-07-18 11:39 ` Anton Khirnov
2022-07-18 16:20 ` Michael Niedermayer
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=20220720152826.GC2088045@pb2 \
--to=michael@niedermayer.cc \
--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