From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Release 6.1 Date: Fri, 22 Sep 2023 11:32:27 +0200 Message-ID: <CAPYw7P5aSeMV9UHfdnxoc38je84_i7jHFRtOnjnQzUXwndtk1A@mail.gmail.com> (raw) In-Reply-To: <20230922092754.GV8640@pb2> On Fri, Sep 22, 2023 at 11:28 AM Michael Niedermayer <michael@niedermayer.cc> wrote: > On Sun, Jul 09, 2023 at 12:14:09PM +0200, Anton Khirnov wrote: > > Quoting Michael Niedermayer (2023-07-07 17:06:54) > > > Hi > > > > > > On Thu, Jul 06, 2023 at 06:04:41PM +0200, Lynne wrote: > > > > It's been a while since we've had a release, and we've had > > > > a lot of new features in. > > > > We did say we would make releases more often, and I think > > > > it's about time we have a new release. > > > > > > yes > > > > > > > > > > > > > > Anything anyone wants to have merged or should we branch > > > > off 6.1 in a few days? > > > > > > libavradio needs testing, at least build testing. > > > all parts of git master are tested automatically by our user base > > > but anything in seperate repositories might receive less testing > > > so we should encourage people to test these seperate repositories > > > for the release > > > > > > also note iam quite busy ATM, its not the best time for me to > > > do 6.1, so "in a few days" is a bit too optimistic i think > > > > How is libavradio related to the release? > > Right, thats a valid question > when i wrote the SDR code it seemed to me that including it in 6.1 was > very simple. But as then some people tried to block SDR by any means > (blocking patches randomly, asking for moving it into a seperate libraray > while not replying to any questions about that libraray and so on) > that made libavradio now have much more strings attached > then the original simple self contained input device > secondary, i lost the will to really work on FFmpeg around the time > of these attacks, so even without SDR i had limited motivation > and then more things that should be in 6.1 accumulated and summer and > good waether ... > And noone else took up the accumulating work either ... > What accumulating work? The SDR work for certainly nobody else wants to pick, except maybe Peter. If you mean real FFmpeg work, than by all means give access to services only you have to other interesting parties, like security related reports and others. > > Now the SDR + blockings is solved by not including any SDR that the > community doesnt like in 6.1 but instead me simply making a seperate > release with SDR, or so i thought. It seems given the replies I seem > to have touched some nerve here too > > The idea was really just, that i said ill include SDR and i want to > keep this word so i want our users to have that 6.1 with SDR that i > promised and also have everyone happy about 6.1 and the long term > design of the SDR code. > I have some more comments about the seperate libraray and SDR but > thats better in a seperate mail in the future. > Thank you for all hard FFmpeg related work, hope your continuing work on your SDR hobby related projects. > > Thanks > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > "You are 36 times more likely to die in a bathtub than at the hands of a > terrorist. Also, you are 2.5 times more likely to become a president and > 2 times more likely to become an astronaut, than to die in a terrorist > attack." -- Thoughty2 > > _______________________________________________ > 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". > _______________________________________________ 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-09-22 9:32 UTC|newest] Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-06 16:04 Lynne 2023-07-06 16:19 ` Jean-Baptiste Kempf [not found] ` <4e164164-f730-4b5e-9edc-1a37b10684e2@betaapp.fastmail.com-NZg-97N----9> 2023-07-07 6:40 ` Lynne 2023-07-07 6:53 ` Ingo Oppermann 2023-07-07 7:36 ` Steven Liu 2023-09-26 13:37 ` Leo Izen 2023-07-07 15:06 ` Michael Niedermayer 2023-07-07 15:33 ` Lynne 2023-07-07 22:51 ` Michael Niedermayer 2023-07-09 10:14 ` Anton Khirnov 2023-09-22 9:27 ` Michael Niedermayer 2023-09-22 9:32 ` Paul B Mahol [this message] 2023-09-22 14:49 ` Michael Niedermayer 2023-09-22 15:27 ` Paul B Mahol 2023-09-26 8:47 ` Jean-Baptiste Kempf 2023-09-22 10:04 ` Nicolas George 2023-09-22 11:42 ` Paul B Mahol 2023-09-26 9:13 ` Anton Khirnov 2023-09-26 15:09 ` Michael Niedermayer 2023-09-26 15:14 ` Kieran Kunhya via ffmpeg-devel 2023-09-26 15:30 ` Anton Khirnov 2023-09-26 16:27 ` Derek Buitenhuis 2023-09-26 17:24 ` Michael Niedermayer 2023-09-26 17:16 ` Michael Niedermayer 2023-09-26 17:25 ` James Almer 2023-09-26 18:03 ` Nicolas George 2023-09-26 18:14 ` Anton Khirnov 2023-09-26 18:24 ` Nicolas George 2023-09-26 18:27 ` Vittorio Giovara 2023-09-26 18:28 ` Nicolas George [not found] ` <F3D5B4BB-AE60-401F-800E-6246B9F359A4@cosmin.at> 2023-09-26 22:50 ` [FFmpeg-devel] SDR choices Cosmin Stejerean via ffmpeg-devel 2023-10-03 19:22 ` [FFmpeg-devel] [RFC] Release 6.1 Michael Niedermayer 2023-10-04 15:19 ` Anton Khirnov 2023-10-04 16:54 ` Lynne 2023-10-04 17:53 ` Michael Niedermayer 2023-09-26 21:20 ` Ronald S. Bultje 2023-09-27 13:53 ` Tomas Härdin 2023-09-27 20:18 ` Michael Niedermayer 2023-09-27 20:27 ` Nicolas George 2023-09-28 8:48 ` Ronald S. Bultje 2023-09-28 14:45 ` Rémi Denis-Courmont 2023-09-28 15:33 ` Nicolas George 2023-09-28 15:58 ` Rémi Denis-Courmont 2023-09-28 16:13 ` Nicolas George 2023-09-28 16:34 ` Rémi Denis-Courmont 2023-09-28 16:42 ` Nicolas George 2023-09-28 14:32 ` Rémi Denis-Courmont 2023-09-28 15:28 ` Nicolas George 2023-09-28 16:22 ` Rémi Denis-Courmont 2023-09-28 16:32 ` Nicolas George 2023-09-28 16:35 ` Paul B Mahol 2023-09-28 16:38 ` Rémi Denis-Courmont 2023-09-28 16:41 ` Nicolas George 2023-09-28 16:42 ` Rémi Denis-Courmont 2023-09-28 16:43 ` Nicolas George 2023-09-28 17:27 ` Rémi Denis-Courmont 2023-07-08 1:46 ` Neal Gompa 2023-07-09 10:13 ` Anton Khirnov 2023-10-09 3:37 ` Lynne 2023-10-09 17:41 ` Michael Niedermayer 2023-10-10 15:19 ` Neal Gompa 2023-10-28 16:49 ` Michael Niedermayer 2023-10-28 16:56 ` James Almer 2023-10-28 19:23 ` Lynne 2023-10-29 4:51 ` Michael Niedermayer 2023-10-29 5:57 ` Lynne 2023-11-07 7:36 ` Lynne 2023-11-07 16:47 ` Tristan Matthews 2023-11-08 1:26 ` Steven Liu 2023-11-08 1:29 ` Steven Liu [not found] ` <NichQkq--3-9@lynne.ee-NichTw8----9> 2023-11-09 8:20 ` Lynne 2023-11-09 9:46 ` epirat07 2023-11-09 9:48 ` Gyan Doshi 2023-11-10 1:47 ` Michael Niedermayer 2023-10-29 9:30 ` Nicolas George 2023-10-29 13:51 ` Jean-Baptiste Kempf 2023-10-29 14:17 ` Nicolas George 2023-10-29 16:27 ` Jean-Baptiste Kempf 2023-10-29 16:40 ` Nicolas George 2023-10-29 16:43 ` Jean-Baptiste Kempf 2023-10-29 16:45 ` Nicolas George 2023-10-29 15:10 ` Thilo Borgmann via ffmpeg-devel 2023-10-29 16:25 ` Jean-Baptiste Kempf 2023-10-29 17:20 ` Thilo Borgmann via ffmpeg-devel 2023-10-29 17:56 ` Jean-Baptiste Kempf 2023-10-29 18:12 ` Nicolas George 2023-10-29 18:22 ` Jean-Baptiste Kempf 2023-10-29 18:31 ` Nicolas George 2023-10-29 19:11 ` Jean-Baptiste Kempf 2023-10-29 19:19 ` Nicolas George 2023-10-29 18:47 ` Thilo Borgmann via ffmpeg-devel 2023-10-29 18:46 ` Thilo Borgmann via ffmpeg-devel 2023-10-29 19:27 ` Jean-Baptiste Kempf 2023-11-01 17:53 ` Thilo Borgmann via ffmpeg-devel 2023-10-29 16:42 ` Jean-Baptiste Kempf 2023-10-29 16:49 ` James Almer 2023-10-29 17:01 ` Jean-Baptiste Kempf
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=CAPYw7P5aSeMV9UHfdnxoc38je84_i7jHFRtOnjnQzUXwndtk1A@mail.gmail.com \ --to=onemda@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