From: Neal Gompa <ngompa13@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 00/72] Implement support for Vulkan multiplane images and video decoding
Date: Sun, 19 Feb 2023 18:50:05 -0500
Message-ID: <CAEg-Je-yPrmWg6HpAgPCLb6bKNn3S7DPabNk04wOLQwNTU+mJQ@mail.gmail.com> (raw)
In-Reply-To: <CAK+ULv79KwP5zNFbOyM1YrmXz48yU=_K+hofvHs9MZrDxHqzfQ@mail.gmail.com>
On Sun, Feb 19, 2023 at 5:00 PM Kieran Kunhya <kierank@obe.tv> wrote:
>
> On Sun, 19 Feb 2023 at 18:46, Lynne <dev@lynne.ee> wrote:
>
> > Feb 19, 2023, 18:43 by kierank@obe.tv:
> >
> > > On Sun, 19 Feb 2023 at 17:36, Kieran Kunhya <kierank@obe.tv> wrote:
> > >
> > >> Obviously, if we merge it now, and big enough issues are found
> > >>
> > >>> which we couldn't fix immediately, I'd have no problem reverting
> > >>> the Vulkan patches from the 6.0 branch.
> > >>>
> > >>
> > >>
> > >> A major LTS release is not your development sandbox.
> > >>
> > >> Kieran
> > >>
> > >
> > > Correction, 6.0 is not an LTS. Nonetheless, it's not your sandbox.
> > >
> >
> > If new features don't go in, the project dies.
> > Everyone but seems to dislike new features.
> >
>
> Sure, then put your features in early in the dev cycle, not days before a
> major release.
>
This is not a reasonable response, especially to someone who is
volunteering their time to develop features for a project. If it
misses 6.0, it sucks.
My concern though is that major version bumps are supposed to be
ABI/API breaks, if this patchset doesn't land in 6.0, does that mean
it'd have to be pushed off to 7.0 if it makes public API changes? If
that's the case, I'd rather request 6.0 to be delayed to get this to land.
--
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
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:[~2023-02-19 23:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 3:43 Lynne
2023-02-17 9:08 ` Jean-Baptiste Kempf
2023-02-17 9:45 ` Hendrik Leppkes
2023-02-17 10:45 ` Lynne
2023-02-17 11:04 ` Kieran Kunhya
[not found] ` <CAK+ULv780c=z_dig_FAhPJ2poZ8u2_QOnnPUmV3SSiYoaQZ+tw@mail.gmail.com-NOU29aV----9>
2023-02-17 11:52 ` Lynne
2023-02-17 15:45 ` Michael Niedermayer
2023-02-17 16:35 ` Lynne
2023-02-18 19:02 ` Michael Niedermayer
2023-02-19 0:08 ` Lynne
2023-02-19 15:40 ` Michael Niedermayer
2023-02-19 15:44 ` Kieran Kunhya
2023-02-19 16:53 ` Lynne
2023-02-19 16:56 ` Jean-Baptiste Kempf
2023-02-19 16:58 ` Lynne
2023-02-19 17:02 ` Jean-Baptiste Kempf
2023-02-19 19:32 ` Niklas Haas
2023-02-19 18:50 ` Michael Niedermayer
2023-02-19 19:02 ` Lynne
2023-02-19 19:44 ` Michael Niedermayer
2023-02-19 20:00 ` Lynne
2023-02-19 20:14 ` Michael Niedermayer
[not found] ` <NOea74V--3-9@lynne.ee-NOeaB9K--R-9>
2023-02-19 16:57 ` Lynne
2023-02-19 17:36 ` Kieran Kunhya
2023-02-19 17:42 ` Kieran Kunhya
2023-02-19 18:46 ` Lynne
2023-02-19 21:59 ` Kieran Kunhya
2023-02-19 23:50 ` Neal Gompa [this message]
2023-02-20 5:13 ` Jean-Baptiste Kempf
2023-02-20 9:18 ` Hendrik Leppkes
2023-02-20 16:51 ` Anton Khirnov
2023-02-20 16:56 ` Anton Khirnov
2023-02-20 17:21 ` Anton Khirnov
2023-02-20 17:40 ` Anton Khirnov
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=CAEg-Je-yPrmWg6HpAgPCLb6bKNn3S7DPabNk04wOLQwNTU+mJQ@mail.gmail.com \
--to=ngompa13@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