On 8/6/2019 9:44 AM, Gyan wrote: > > > On 06-08-2019 03:19 AM, Michael Niedermayer wrote: >> On Sun, Aug 04, 2019 at 07:56:00AM +0200, Michael Niedermayer wrote: >>> On Sun, Jul 21, 2019 at 07:11:40PM +0200, Michael Niedermayer wrote: >>>> On Mon, May 20, 2019 at 08:39:45PM +0200, Michael Niedermayer wrote: >>>>> Hi >>>>> >>>>> Its quite some time since 4.1 so its probably getting time to branch >>>>> 4.2. >>>>> >>>>> If there are any bugs you want fixed in 4.2 its probably a good >>>>> idea to >>>>> fix them soon. >>>>> >>>>> Are there any suggestions for a name ? >>>>> If not ill pick something from unused past suggestions. >>>>> >>>>> If there are no objections i will likely make that release in the >>>>> next weeks >>>> 4.2 branch made >>>> i intend to make the 4.2 release from HEAD of release/4.2 in the >>>> next 1-2 weeks >>>> please backport any relevant bugfixes to it. >>> Status update: There are a few remaining crashes / security issues >>> which i think >>> we should fix and include before the release. Iam working on that >>> currently. >>> >>> When thats done depends on >>> 1. any delays (bikesheds, distractions, headaches, good weather that >>> makes me ignore >>> this and go for a walk or maybe going for a walk occasionally >>> actually helps >>> my efficiency who knows, ...) >>> 2. influx of more security reports (fuzzer and any human reports), >>> there where >>> several new reports in the last 2 weeks which fall in the "I >>> think that should >>> be fixed before the release" category >>> 3. murphies law and anything else unexpected >> 4.2 release made >> > > Someone with access should post the News entry. > > Gyan
I'll send a patch in a bit. _______________________________________________ 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".
