On 8/5/2019 10:13 AM, Gyan wrote: > > > On 05-08-2019 06:05 PM, Paul B Mahol wrote: >> Hi, >> >> Is there some official way how to become release maintainer? >> Expecially creating new releases once in a while. >> I'm not happy with current release management in FFmpeg. > > Yes, release intervals look to be erratic. What would help is a > suggested schedule, something like > > master nb_commits % 1500 == 0.
Commit amount means nothing. You could get a whole new decoder in one, or a fix for a single issue split across seven. And if you make the cut as strict as you suggest, you'll surely get broken releases. > > This is self-pacing - rapid/slow development -> rapid/slow release. > Since the marker indication is known in advance, developers can guess by > when their patches should be pushed to make it in a release. The exact > cut point can be relaxed a bit to allow for important backports. > > Gyan > _______________________________________________ > 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".