From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] 5.0 blocking issues Date: Thu, 13 Jan 2022 08:34:12 -0300 Message-ID: <a46e21f2-221a-06fc-1b1c-0d2bc0d0aeee@gmail.com> (raw) In-Reply-To: <9ea7cfe56c33584a7e7dff19936be3191f21be00.camel@intel.com> On 1/13/2022 1:02 AM, Xiang, Haihao wrote: > On Wed, 2022-01-12 at 21:35 +0000, Soft Works wrote: >>> -----Original Message----- >>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Michael >>> Niedermayer >>> Sent: Wednesday, January 12, 2022 5:31 PM >>> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> >>> Subject: Re: [FFmpeg-devel] 5.0 blocking issues >>> >>> On Wed, Jan 12, 2022 at 07:37:03AM +0100, Lynne wrote: >>>> 8 Jan 2022, 17:30 by michael@niedermayer.cc: >>>> >>>>> Hi all >>>>> >>>>> This is a simple go/no go call >>>>> if you know of something that still should go into 5.0 please reply here >>>>> with a list of what you are working on and a timelimit until when you >>>>> will be done with it >>>>> >>>>> if you think everything is ready for the release, then too feel free to >>>>> reply (assuming few others said ok yet) this is not supposed to become a >>>>> 100 reply thread with oks, just maybe 2-3 people confirming that noone >>>>> is aware of things missing. >>>>> >>>>> I intend to do the release within 2-3 days of all "no go" things being >>>>> resolved or timeouting >>>>> >>>>> thx >>>>> >>>> >>>> Both of elenril and mkver's patches got merged, isn't it >>>> time to tag and make archives already? >>> >>> something is not working efficiently here >>> There have been more replies here than from elenril and mkver >>> also there have been over the ML multiple requests for backports >>> to 5.0 today. (which may or may not be all unimportant) >>> We do need a better way to detect when a branch is ready for release >>> or master is ready to be branched. >>> Iam really bad at keeping track of everything everyone asks to be >>> included and then notice when it was included fully with nothing >>> missing and no amendmends. >>> Maybe we could put a RELEASE_BLOCKER file in release branches in the future >>> and everyone can list in it what needs to be done before the release >>> and when something is done the person pushing would also remove that >>> line from the file. >>> >>> for 5.0 now, i guess this is a 2nd go/no go call here >>> anything else that I should wait for ? >>> if not i will make the release _probably_ in the next 2-3 days or so >>> (if nothing interferes) >> >> >> [PATCH v4] avfilter/vpp_qsv: fix regression on older api versions (e.g. 1.11) >> >> Published-As: >> https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-15%2Fsoftworkz%2Fqsv_vpp_regression-v4 >> >> Pull-Request: https://github.com/ffstaging/FFmpeg/pull/15 >> Patchwork: >> https://patchwork.ffmpeg.org/project/ffmpeg/patch/pull.15.v4.ffstaging.FFmpeg.1641538891098.ffmpegagent@gmail.com/ >> >> => Has been merged in to master >> > > It would be better to include this fix in 5.0 release. May I cherry-pick this > patch to the release branch ? It's a bug fix, not a feature addition or behavior change, so it matches the criteria for backporting. Feel free to do it. > > Thanks > Haihao > > >> >> [PATCH] avcodec/dvdsubdec: fix incorrect yellow appearance of dvd subtitles >> >> Published-As: >> https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-16%2Fsoftworkz%2Fpatch_dvdsubdec_fix-v1 >> >> Pull-Request: https://github.com/ffstaging/FFmpeg/pull/16 >> Patchwork: >> https://patchwork.ffmpeg.org/project/ffmpeg/patch/pull.16.ffstaging.FFmpeg.1641262759164.ffmpegagent@gmail.com/ >> >> => not merged yet >> >> >> Thanks, >> softworkz >> >> >> >> >> _______________________________________________ >> 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". _______________________________________________ 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".
prev parent reply other threads:[~2022-01-13 11:34 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-08 16:30 Michael Niedermayer 2022-01-08 16:36 ` Romain Beauxis 2022-01-08 18:55 ` Soft Works 2022-01-08 21:31 ` Lynne 2022-01-10 3:09 ` "zhilizhao(赵志立)" 2022-01-10 9:04 ` lance.lmwang 2022-01-10 10:32 ` "zhilizhao(赵志立)" 2022-01-10 16:55 ` Anton Khirnov 2022-01-10 18:12 ` Andreas Rheinhardt 2022-01-12 6:37 ` Lynne 2022-01-12 16:30 ` Michael Niedermayer 2022-01-12 16:36 ` Nicolas George 2022-01-12 16:41 ` James Almer 2022-01-12 16:47 ` Nicolas George 2022-01-12 17:30 ` Jean-Baptiste Kempf 2022-01-12 17:58 ` Nicolas George 2022-01-12 23:17 ` Michael Niedermayer 2022-01-12 21:35 ` Soft Works 2022-01-13 4:02 ` Xiang, Haihao 2022-01-13 11:34 ` 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=a46e21f2-221a-06fc-1b1c-0d2bc0d0aeee@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