On Wed, 2022-01-12 at 21:35 +0000, Soft Works wrote: > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-boun...@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 mich...@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.ffmpegag...@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 ? 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.ffmpegag...@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-requ...@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-requ...@ffmpeg.org with subject "unsubscribe".
