Quoting Lynne (2024-01-23 21:18:29) > Jan 23, 2024, 20:22 by mich...@niedermayer.cc: > > > Hi all > > > > As it was a little difficult for me to not loose track of what is > > blocking a release. I suggest that for all release blocking issues > > open a ticket and set Blocking to 7.0 > > that way this: > > https://trac.ffmpeg.org/query?blocking=~7.0 > > > > or for the ones not closed: > > https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&blocking=~7.0 > > > > will list all blocking issues > > > > Ive added one, for testing that, i intend to add more if i see something > > > > What is blocking? (IMHO) > > * regressions (unless its non possible to fix before release) > > * crashes > > * security issues > > * data loss > > * privacy issues > > * anything the commuity agrees should be in the release > > > > On my side, what I want: > Vulkan AV1. It's ready to be posted once the spec goes public very very soon. > This shouldn't even become a blocker unless you want a release tagged > immediately. > > And those that I don't consider as blockers, just something nice to have: > > Vulkan encode (H264). Needs about a week of work. > HE-AAC 960-point. > Preliminary xHE-AAC support. Not sure. > AAC prepad fixes - perhaps partial (off by one sample for SBR).
Sigh. We already had this drama last time, must we do it again? If you haven't even started working on it yet, then it shouldn't be a blocker for the release, it can wait half a year for 7.1. -- Anton Khirnov _______________________________________________ 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".
