On Sat, Feb 10, 2024 at 06:03:57PM -0300, James Almer wrote: > On 1/23/2024 4:22 PM, Michael Niedermayer wrote: > > 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 > > > > thx > > There are currently issues with the hevc decoder after some of the commits > that shared code with the vvc decoder were pushed. You can see it by running > the hevc conformance suite in FATE under GCC ubsan. > > Nuo Mi said he's looking at them, but if it takes him too much time we can > revert the faulty commits before the release, in either master or even the > actual release branch.
Please create a ticket for this and add blocking: 7.0 So it cannot be forgotten thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB "Nothing to hide" only works if the folks in power share the values of you and everyone you know entirely and always will -- Tom Scott
signature.asc
Description: PGP signature
_______________________________________________ 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".
